Out of the blue i can no longer edit chunks

Other than chunks, everything else is editable. When I try to edit a chunk I get a message "You don’t have enough privileges for this action!" !!!! I can add a new chunk and then I cannot go back and edit it. Where did this come from? One moment I can edit the next not. I have admin permissions in the manager.
Any thoughts on what would have caused this?
Thanks,
Hal

Sounds like something in the chunk that your server’s mod_security doesn’t like.
http://wiki.modxcms.com/index.php/What_is_mod_security_and_how_does_it_affect_me

Susan; None of the referenced info helped. Using DBManager Pro, I looked at the tables in my site DB and looking at the table ..._site_htmlsnippets I can see the contents of each chunk - except that the chunk that seems to be causing the problem - does not show up in the table. Hmmmm! I does however show up in the MODx manager - resources -manage resources- chunks. Something needs to be cleared out but I do not know what. Right clicking and selecting inspect element gives; <a href="index.php?id=39&a=78">opinionpng</a>
However I can see there is no entry 39 in the table. I do not know what the &a=78 means unless it is an access code.
More research needed.
I have a memory module that tested bad with memtest86 - it has a memory hole in it, and I awaiting the replacement, so it is possible that when i saved the chunk it got as far as putting the name into the modx manager and then hit the memory hole as it is NOT in the table. Now how to fix things?
Hal

The name can’t be "in the MODx Manager" if it’s not in the database. The Manager gets its list of chunk names from the database. Maybe it’s coming from the assets/cache/siteCache.idx.php file; there is an array in that file named chunkCache, you can find it if you do a search on that file. But that file doesn’t store the chunk’s database ID, and I don’t think the Manager uses that. Maybe your browser cache?

Definitely doesn’t get the list of chunks from the cache file:


You can find out what those numbers in the URL mean if you look at the manager/index.php file and do a search for the number. That index.php file has a long switch structure to determine what action to take based on the GET value. The a means "action".

It sounds like it’s acting as if the site has been moved from one domain to another, but the config file still points back to the origianal DB on a shared server environment. Sure that’s not it, but that’s what it sounds like to me.

Thanks all; No it is not in assets/cache/siteCache.idx.php. but I can see the chunk name in the manager but not the DB??
I think all my problem here is due to the bad memory module. There are several bad memory addresses in that module and without warning an application will simply vanish - blink gone - if it hppens to write to that memory block. Firefox may have done that while i was saving that chunk and corrupted something.
The UPS man just brought my replacement memory modules and after I get them installed, I think I will just wipe the DB clean and reinstall MODx from scratch. I’ve saved all my templates and snippets, and gone into the DB and copied any chunks I needed to save. That will take less time than continuing to troubleshoot.
Thanks for the help.

I upgraded to the latest XAMMP and the re-installed MODx and everything is now working as normal. My new memory modules are installed and checked with a 4 hour run of memtest86 with no errors.
Thanks all,
Hal