Resources in certain context will not save

Hello all,

I'm afraid this may turn out to be a complex problem, but I have no idea what may be going wrong, so maybe one of you can help me.

I'm using Revo 2.2.2, and I have five contexts. The first context is web, and the other four correspond to subdomains. In one of my contexts, I cannot save resources. If I edit one and hit "Save", the "Please Wait..." box comes up and goes and goes for quite a while. Finally it disappears, leaving the page still unsaved.

There's nothing in my error log, and this behavior is the same across browsers. Can anyone help give me an idea of why this is happening for resources in this context only? The other contexts don't have this problem, so all I can think is that it is related to the context somehow. Let me know if I can provide any more information that would help solve the problem.

Thanks!

One possibility is that your Context Access ACL entry for that context has a Policy without the "save_document" permission.

Another is that the Resource is protected by a Resource Group Access ACL entry and you don't have "save" permission in the relevant Policy.

It could also be a weird mod_security problem based on the name of the context or some phrase that's part of the data for resources in that context that modx_security thinks is suspicious.

OK, quick update. I checked the ACL permissions, and all is well there. Also, I realized I didn't quite diagnose the problem correctly. I narrowed it down to only resources in a certain container within a container that were having this problem (so it's not context related). Finally, I discovered that if I do Quick Update Resource instead of Edit, the resource saves just fine.

So, it's still a mystery, but at least I can get done what I need to do. Thanks!

I know it sounds far-fetched, but I've seen some very similar cases that were caused by a mismatch between the data/timezone setting for PHP, the server, and the MODX System Setting.

I checked timezone settings, and I don't think that's it.

I've actually narrowed down the problem even more, and it's very strange. Any time I try to save a resource that includes the word "echo" in the content text, it will not save (behaviour described in previous message). When I remove the offending word, the resource saves in seconds.

I'm guessing this is a bug in MODX itself--it occurs with or without a rich text editor.

Do you have a suggestion of where I should go from here? Should I try upgrading to a newer version? I tried saving "echo" in a resource on a 2.2.6 install and it worked fine.

Sounds like a mod_security setting to me. They can be set to prevent POST values from being passed to a form processing script. Often words having to do with email or "x-rated" words or in one recent case the word "casino" was blocked. Was the 2.2.6 installation on the same server?