ModX takes forever to save? The please wait saving loop.

Have you checked in the Developer Console/Firebug/Web Inspector depending on what browser you're using to see if you are getting any errors on the ajax save. Sometimes, the processor will error out (e.g. you have a bad plugin or mod_security is kicking in) and that can cause the save dialog behaviour described here.

That's normally where I start debugging these issues anyway

Thank you for responding so quick! I have an error that shows up in my firebug console that says "uncaught exception: [object Object]" as well as the error (ERROR @ /index.php) [FormIt] Could not find hook "loadCustomValues" in my modx error log. I just tried uninstalling the formit plugin and reinstalling it, but that didn't help. I am not sure where to start looking for solutions with these errors... any ideas where I can start?

Look at the FormIt tag (on any page that has a FormIt tag) for a &hooks or preHooks property with 'loadCustomValues' in its value.

In that case, FormIt will look for a snippet called 'loadCustomValues' and the message is saying that you don't have one with that exact name.

Thank you for the response Bob! I was able to find the forms that were calling the preHook 'loadCustomValues' and I have deleted the preHook because I am no longer using it any more. I haven't seen any of those errors in the error log since, but it is still taking a long time to save the page and I am still getting the firebug error 'uncaught exception: [object Object]' and Failed to load resource: the server responded with a status of 500 (Internal Server Error) - DOMAIN/connectors/resource/index.php,
Uncaught #<Object> - ext-all.js:7 in Chrome Developer... any ideas?

I was experiencing the same issue. It just started today. I looked at the Firebug console and it said there was an issue with the parent document's pagetitle when being parsed by ext-all.js (line 21, col 60):



I find this interesting, because The actual pagetitle of the document is:
Product User Guide (&quot;Hot Chocolate&quot; Edition)


Notice that my pagetitle uses "amp;. It does not use plain quotation marks. Somewhere along the line, MODx is converting my HTML entity into plain quotation marks, and this is breaking the code. So I removed both instances of &quot; from my pagetitle, and now when I save one of the child documents, the save works properly. This is reproduceable. I put &quot; in, and I get the error when saving a child document. I take &quot; out, and the error goes away.

Just out of curiosity, I tried saving it with plain quotation marks, and there is no error.

This seems like a bug that can probably be remedied pretty easily in the MODx source code by anyone who wants to take that on.

(By the way, I had a hard time forcing this discussion forum to write &quot;. I had to cheat and write &amp;quot;. Otherwise this forum converts it automatically to a regular quotation mark.)
[ed. note: paulbohman last edited this post 12 years, 9 months ago.]