I have a strange problem. While our EE 2 installation was working normally for years, suddenly weeks ago I began to not be able to edit our “snippets”, then a week later the same happen to templates. I still can create snippets and templates, but when I put code in it, it won’t save. I can put regular words in it, but not certain code. Since then, I edit my templates by ftp.
Now, this week, I can’t any more edit or publish entries. Our sites still works, but can’t be updated.
First I thought that maybe our hosting server was upgraded to a php or mysql versions that might not be compatible with the old EE 2, so I upgraded to EE 3, and sadly, I still can’t edit or publish entries and still can’t edit snippets and templates.
We use Multiple Site Manager for some 15 sites.
In fact, when I save I get out of the CP and always get our main home page. Nothing got saved.
Any idea what is going on ? Thanks !
This really sounds like something environmental. And this bit:
> I can put regular words in it, but not certain code.
That sounds a whole lot like mod security. It’s not super unusual for it to object to javascript or a query. But- it does sound like it’s going hog wild all of a sudden if indeed mod_security is the problem.
Drop your host a support request, let them know you are having trouble with post data and you think it may be a security filter server side objecting to the content. As them to check the logs and also ask if anything has changed recently. If all of a sudden it’s behaving different, something changed. They should know what it is and be able to help fix it.
And let us know what you find- I’m always curious!
Something similar has also happened to us. We receive a 403 Forbidden error message when trying to do quick save or update. Changes don’t save. This started very recently. We’re using EE 1.6. Our web host support felt that this might be the cause and suggests upgrading to the current EE version. We might have to do that or change to another CMS.
How simple will it be to upgrade from 1.6 to 5.3?
Finally, our hosting server, after days of playing with mod_security settings, came to fix things. But, until we got to EE 5, we still had some problems; getting logged out quickly without reason, which we fixed by changing the cookie settings; and we were still unable to edit code in “snippets” (template partials).
So, now that we are on EE 5, everything seems to work as it should.
And our own experience with upgrading from EE 1 to EE 5:
From EE 1.6 to 2.0; it was hell: much new code and the loss of the “photo album” module gave us a lot of trouble (we are not programmers…).
But, from 2.11.9 to 5, it was relatively easy. Note that at the passage from 2.11.9 to 3.5.17 we had a bug which stopped the upgrading sequence: the EE addon; “email_address” was causing trouble. So, we removed it from the “Addons” folder and we were able to finish the upgrade. After that, we put it back.
Then, the “one click” upgrade from 4 to 5, didn’t work, so we followed the instructions of what to do if so, and then it worked. Now everything seems to be OK.
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.