MODx Parse Error Question (Noob)

Cheers everyone and a happy new year.
I’ve got a client site running on MODx and when I went to login/make some updates today, keep running into errors like this:

« MODx Parse Error »

MODx encountered the following error while attempting to parse the requested resource:
« Execution of a query to the database failed - Table ’./gatewayy_modx/modx_site_content’ is marked as crashed and should be repaired »
SQL: SELECT sc.* FROM `gatewayy_modx`.modx_site_content sc LEFT JOIN `gatewayy_modx`.modx_document_groups dg ON dg.document = sc.id WHERE sc.id = ’13’ AND (sc.privateweb=0) LIMIT 1;


Is this something that is triggered by their host making server changes that have affected this MODx install? I apologize in advance for my noobness, I’m the front-end (CSS/XHTML) guy and have been trying to get my head around all the back-end goods over time. You can view the client site here:

http://gatewayyoga.com/home

And the errors occur if you attempt to visit any other page on their site. Thanks in advance for any help everyone!

Cheers,
Benjamin

Go here http://dev.mysql.com/doc/refman/5.0/en/repair.html for the mysql(5) manual page concerning this error.

This article refers to fixing this with cPanelhttps://my.alwayswebhosting.com/support/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=13, you can also do this using phpMyAdmin, select the table in question and then select to repair it.

Note that the error could also indicate more serious corruption than just one table, you may need to repair/rebuild the whole database.

Odd that some pages and the eForm contact form are working. Since all pages use the same site_content table it would be strange that it would be crashed on some pages an not on others. Sorry I don’t have any suggestions

Perhaps some pages don’t invoke this query for some reason, cached maybe, or some other setting? I’d definitely try a repair here, backup before hand of course, if you can that is, the error may preclude this now.

Thanks for responding so quickly people, and for the linkage shamblett. I greatly appreciate your time and consideration.

I admit, being the designer, all this sql stuff intimidates me, so hopefully I can figure it out enough to salvage their site. Fingers crossed, time to jump into the deep end...

Peace,
Benjamin

**UPDATE**

Thanks again shamblett, logging into phpMyAdmin on their servers and doing the ’repair table’ action worked a charm! Have a great new year and until next time...

Peace,
Benjamin