MODX Stuck In Saving Loop - 403 & Uncaught Synax Errors

64 Posts

yankindeez Reply #1, 8 years, 8 months ago

My MODX Revo v2.6.0 was working fine until yesterday, and then suddnely I couldn't save. I've made no significant changes to the settings or modx environment.

When using the Inspect Element Console, the following error appears:

ext-all.js:21 POST http://[mydomain].com/connectors/index.php 403 (Forbidden)
doFormUpload @ ext-all.js:21
request @ ext-all.js:21
run @ ext-all.js:21
(anonymous) @ ext-base.js:21
setTimeout (async)
defer @ ext-base.js:21
doAction @ ext-all.js:21
submit @ ext-all.js:21
submit @ modx.jsgrps-min.js:4
handleClick @ modx.jsgrps-min.js:3
checkConfirm @ modx.jsgrps-min.js:3
fn @ modx.jsgrps-min.js:3
i @ ext-all.js:21
handleKeyDown @ ext-all.js:21
I @ ext-all.js:21
VM484:1 Uncaught SyntaxError: Unexpected identifier
    at doDecode (ext-all.js:21)
    at Object.decode (ext-all.js:21)
    at Ext.form.Action.Submit.handleResponse (modx.jsgrps-min.js:1)
    at Ext.form.Action.Submit.processResponse (ext-all.js:21)
    at Ext.form.Action.Submit.success (ext-all.js:21)
    at o (ext-all.js:21)
    at Ext.data.Connection.s (ext-all.js:21)
    at HTMLIFrameElement.I (ext-all.js:21)

Does anyone know what is causing this or how I can fix it?

- 91 Posts
cottagestuff Reply #2, 8 years, 8 months ago

Speaking from a position of almost total ignorance, but some considerable experience of MODX perpetual saving phenomena, it has usually involved (in my instances) a breach of one or more modsec rules. Could that be the case? Have you tried disabling modsec to see if the problem persists?