Answered All my Chunks have disappeared & Obvious Suggestion for Revo

Hi there,
I am having an issue in Revo 2.2.8, as you can see in the screenshot below all my chunks have suddenly dissapeared. I am on localhost wamp server windows 7 (64 bit). I have been building on localhost without any problems, then yesterday I noticed all my chunks were gone. (I did try clearing cache, flushing, etc, and it did not help..)

I am pretty sure there is a relation here, but if it helps I also tried creating a new chunk to see if all my missing chunks would reappear and am unable to create a chunk (I hit save and the saving pop-up bar loops but does not save.)

Everything above leads to the obvious, or what should have been an obvious module that I have already complained about which was carelessly not included in REVO , THE BACKUP BUTTON... One click would have saved me all this trouble... Luckily this happened to one of my sites and not to one my clients sites...

From Evo to Revo, this is the one and only gigantic step down.

Quote from: sottwell at Sep 11, 2013, 07:42 PM

Are they still in the site_htmlsnippets table in the database? Could that table possibly have become corrupted and need repair? Have you been doing anything with the ACL permission system?

Thank you for your quick response, I would have to guess that no to changing the ACL permission system given I am not 100% sure what that means. I will check my database for site_htmlsnippets and report back.

Thank you again for the quick reply

Quote from: sottwell at Sep 11, 2013, 07:42 PM

Are they still in the site_htmlsnippets table in the database? Could that table possibly have become corrupted and need repair?

Susan,
You are right on first try, upon trying to check "site_htmlsnippets" in database and got this pop-up below(screenshot below).

Any suggestions on how to proceed?

Not sure why its putting my replies at the top..

http://dev.mysql.com/doc/refman/5.0/en/repair-table.html

If you're using phpMyAdmin, you can use that to repair the table.
http://php.about.com/od/mysqladministration/qt/repair_mysql.htm

I'd suggest repairing all the tables just in case. At the bottom of the grid in PhpMyAdmin (after you select the MODX database from the list on the left) there's an option to check all tables and next to it a drop-down menu that lets you pick Repair for all of them. It's surprisingly fast.

Thank Susan & Bob.

One more quick question, If only my chunks are missing any chance that repairing all tables will do any harm to anything else that is currently working..

Thanks again.

If a table is already OK, the repair operation won't affect it. I've never had repair cause a problem.

If you're nervous, you can always create a backup first using the "Export" tab at the top. It's not a bad idea to do that anyway whenever you're messing around in the database.

Quote from: BobRay at Sep 11, 2013, 10:46 PM

If a table is already OK, the repair operation won't affect it. I've never had repair cause a problem.

If you're nervous, you can always create a backup first using the "Export" tab at the top. It's not a bad idea to do that anyway whenever you're messing around in the database.

Thank you