M
M
mletov2018-01-23 21:48:52
MODX
mletov, 2018-01-23 21:48:52

How to fix error in modx admin?

Here is the problem:
In Modx, when creating a new material, the save block is not removed, an error occurs in the console

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)

Googled. They write that the problem is in the time zone (I still do not understand how this is connected). Changed London (+0000) to Saratov (+0400). The server rebooted. Did not help. I also tried to put Moscow (+0300)
How can I fix this?
Locally on Denver everything works fine. Another lingering question. Locally on Windows, the time zone is Moscow (+0300), but at the same time in php echo date("O"); returns +0400 (it looks like Saratov). I thought server time comes from the system.

Answer the question

In order to leave comments, you need to log in

3 answer(s)
M
mletov, 2018-02-18
@mletov

Switched to PHP 7, the error is gone

Y
Yana Mitrofanova, 2018-02-18
@Raina97

Try this solution: https://modx.ru/vopros-answer/info/1990/#7601

D
Dima Neigraysnimi, 2021-03-02
@dimaneigraysnimi

Maybe it will help someone, I fixed it like this:
In the console, when saving a large resource, it also hung in endless loading. There were ext-all.js errors to the browser console. In the domain log - the server section (web, where the sites are) saw the error "HTTP request length 135006 (so far) exceeds MaxRequestLen (131072), referer: https://*******/***** *panel/index.php?a=resource/u... ".
It turned out to fix it this way:
In vestacp, go to the server tab, server configuration and specify MaxRequestLen 10485760 in IfModule.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question