Modx Revolution 2.2.6, cannot save site home page changes

Server: Shared hosting
Apache version 2.2.24
PHP version 5.3.22
MySQL version 5.1.68-cll
Architecture x86_64
Operating system linux


All other resources/documents can have their attributes altered, content changed etc and successfully saved.
I was running this site with an older revo version and the problem just started a short while ago. Upgraded the site today to 2.2.6 and there is still the same issue.

When I click on save in the manager after editing the home page resource, the saving popup bar appears and continues to cycle indefinitely. For other pages everything works fine (saves).
Tried altering the template choice for the home page, still the same, will not save any attribute changes.

Anyone else experienced this?

With the risk of playing Captain Obvious here: Tried emptying your cache? (manually)

Quote from: thapriest86 at Mar 21, 2013, 12:09 PM

With the risk of playing Captain Obvious here: Tried emptying your cache? (manually)

Yes tried to empty the cache and remove locks.

Another admin in to the site is also having the same problem

Sorry for being Captain Vague , but I remember I encountered the same problem a while back. Troubleshooted by removing snippets that appeared in my homepage template.

Another thing to try is disabling plugins one-by-one until it stops.

It could also be mod_security if there's something on that page that mod_security doesn't like. Sometimes is can be something really simple, like the word 'casino'. One way to check is to paste the content somewhere safe and try saving it with no content. If the page has its own template, try setting it to another template and saving (though you'll lose your TV values when you do that). If one of those things works, it's probably mod_security. Your host may be able to tell you what the problem is, or you can restore the parts one at a time until it breaks.

Quote from: BobRay at Mar 21, 2013, 09:32 PM

Another thing to try is disabling plugins one-by-one until it stops.

It could also be mod_security if there's something on that page that mod_security doesn't like. Sometimes is can be something really simple, like the word 'casino'. One way to check is to paste the content somewhere safe and try saving it with no content. If the page has its own template, try setting it to another template and saving (though you'll lose your TV values when you do that). If one of those things works, it's probably mod_security. Your host may be able to tell you what the problem is, or you can restore the parts one at a time until it breaks.

No kidding, went through the template section by section. The last component (template variable) which essentially inserted a facebook like iframe was causing the error.
Naturally there is plugin script by facebook called likebox.php which operates inside the iframe.
Please help me out and enlighten me as to why this would cause the saving of the resource to fail (loop endlessly). You mentioned the apache module 'mod_security'; have you ever encountered this specific error and if you have which setting can I ask the host to amend?

Thanks Bob and anyone else with the solution

I can easily imagine mod_security freaking out over a PHP script operating in an iFrame, though I haven't seen that specific problem before. mod_security is infinitely configurable and lots of hosts have strange ideas about what it should protect them from.

BTW, if that extra was installed about the time things went south, it may just be that MODX doesn't like PHP code in page content. It wants it to be in snippets.