Endless loop saving in Revolution 2.3.1

Hi,

suddenly, when trying to save a document, I get the loop saving box stuck forever and the actual content never gets saved. I have tried all different browsers and I don't have tinymce or any other plugins installed.

Any idea?

Thanks.

Dunno if this can help, but logging in and out solves this problem for me. You probably should give some info on your version (Evo and Revo and version number) and anything that is installed.

Also pls check the log file.

What do you see in the Net panel of the debugger in Firefox or Chrome? When I last experienced these symptoms the POST request to save the changes returned 404.

In this case it turned out that normal MODX usage was triggering a mod_security rule at the data centre and they blocked the request.

Does the Net panel show anything useful in your case?

Usually, as mentioned above, a mod_security issue with the host. I always just call the host and ask to be white listed so that mod_security doesn't interfere with web applications (MODX or otherwise).

I get this call

POST http://bountifulbotanicals.com/connectors/index.php 406 (Not Acceptable)

right after the SAVE button is hit...

the entire call looks as the following

POST http://bountifulbotanicals.com/connectors/index.php 406 (Not Acceptable) ext-all.js:21
Ext.extend.doFormUpload ext-all.js:21
Ext.extend.request ext-all.js:21
Ext.extend.run ext-all.js:21
(anonymous function) ext-base.js:21
Uncaught SyntaxError: Unexpected token < ext-all.js:21
Ext.util.JSON.doDecode ext-all.js:21
(anonymous function) ext-all.js:21
Ext.override.handleResponse utilities.js:282
Ext.form.Action.processResponse ext-all.js:21
Ext.extend.success ext-all.js:21
o ext-all.js:21
s ext-all.js:21
I ext-all.js:21

Time to contact your host, evidence suggests they are blocking the request.

it actually is GODADDY who provides MODX intallation package by default....

I'll try to contact them anyway....

Oh the irony, I just got hit with the exact same issue on a server belonging to a client. At least their tech support is responsive:

Yes you are hitting a mod_sec rule

[Mon Sep 22 17:03:04 2014] [error] [client xxx.xxx.xxx.xxx] ModSecurity: Access denied with code 406 (phase 2). Pattern match "(?:include ?\\\\( ?(?:\\"|\\\\')? ?http|(?:define|fgets|move_uploaded_file|readfile|ftp_put|ftp_fget|gze?en?code|gzinflate|ftp_nb_put|bzopen|readdir|gzread|fopen|ftp_nb_f(put|get)|ftp_get|scandir|fscanf|readgzfile|fread|proc_open|fgetc|fgetss|ftp_fput|ftp_n ..." at ARGS:events. [file "/usr/local/apache/conf/modsec_rules/10_asl_rules.conf"] [line "801"] [id "380018"] [rev "25"] [msg "Atomicorp.com WAF Rules: Potentially malicious PHP code injection attempt"] [data "system\\x22"] [severity "CRITICAL"] [hostname "xxxxxxx.co.uk"] [uri "/connectors/index.php"] [unique_id "VCBIN1vS6QIAABE9g@0AAAAB"]

I've no real experience with GoDaddy but expect they should be able to whitelist your IP or remove that rule for your site.

I was told that they can only whitelist one IP and that is all they can do. Pretty much a useless solution...