Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
[SOLVED] Save page/style in backend = error 403??
Issue is resolved, 2nd post below explains why.
After updating a 4.5.7 TXP to 4.6.2 – After a server cpanel update incl. MariaDB i can not save edited pages or style sheets in backends anymore , across various 4.5.7 and 4.6.2 installs.
I am getting a 403 error upon saving a page (not an article) or style sheet
Additionally in the frontend i get errors for certain default articles of sections, stating
“Tag error: <txp:article id=“195” /> -> Textpattern Error: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ‘) LIMIT 0, 10’ at line 1 while parsing form None on page default”
EDIT: I get this error also on a fresh install of TXP 4.6.2 – seems server related.
More server info:
cPanel Version 64.0 (build 36)
Apache Version 2.2.34
PHP Version 5.4.45
MySQL Version 10.0.31-MariaDB
Any hints appreciated!
Last edited by jayrope (2017-08-29 19:20:54)
A hole turned upside down is a dome, when there’s also gravity.
Offline
Re: [SOLVED] Save page/style in backend = error 403??
Issue is resolved. Server provider reported issue with “our rules in mod security”.
Note, that this was the very end of an 8 days struggle, which at first returned white pages on txp 4.5.7 installs.
Then, after downgrading php to 5.3, they left any and all txp installs with non-working special char display (äöü √ ø etc.).
The after fixing this with cpanel service (strange things going on with MariaDB) we got to the error 403, which started this thread.
Thanx for reading. I hope the sparse insights help anybody.
Last edited by jayrope (2017-08-29 19:20:15)
A hole turned upside down is a dome, when there’s also gravity.
Offline
Re: [SOLVED] Save page/style in backend = error 403??
Hi jayrope
I’m glad it was resolved.
Yiannis
——————————
NeMe | hblack.art | EMAP | A Sea change | Toolkit of Care
I do my best editing after I click on the submit button.
Offline
Re: [SOLVED] Save page/style in backend = error 403??
Thanx Colak, yet certain plugins like cbe_frontauth or even TXP itself use cookies upon login, that can’t make a difference between a URL like example.com or www.example.com or using an http or https connection for this. So the kind of stuff always can throw you out of being able to save in backend. However, i fixed half of that problem redirecting non-www URLs to www in htaccess.
A hole turned upside down is a dome, when there’s also gravity.
Offline
#5 2018-02-08 23:42:12
- Vitruvius
- Plugin Author
- Registered: 2004-09-21
- Posts: 125
Re: [SOLVED] Save page/style in backend = error 403??
I have just migrated 4 TXP sites to a new host and have only just noticed this error as well. It seems weird that it is only occurring when saving Pages or Styles…
I’ve shared a link with the host support to this thread – but I’m wondering if there was anymore information about the fix your host implemented when they said “our rules in mod security”.
Thanks
Offline
Re: [SOLVED] Save page/style in backend = error 403??
Vitruvius, that situation came up here twice.
First time in last August or so it took them 8 days to fix it.
This time, some weeks ago, they simply switched off mod_security.
Later on I read, that this is a common way of server space providers to deal with almost any other CMS, than Wordpress. But even there it seems a common way.
I suppose, that there is some deep difference between CMS devs and server administrators, or the devs of their software.
More, unfortunately, I don’t know.
Hope that helps, although I am still heavily wondering about the possible inclinations of switching mod_security off.
Anybody got insight into that?
Last edited by jayrope (2018-02-09 00:25:46)
A hole turned upside down is a dome, when there’s also gravity.
Offline
#7 2018-02-09 01:53:42
- Vitruvius
- Plugin Author
- Registered: 2004-09-21
- Posts: 125
Re: [SOLVED] Save page/style in backend = error 403??
Thanks for that information!
As a quick update in case anyone stumbles on this thread – I found an old thread with a similar problem and some advice to turn mod_security off in the .htacess file by adding this line near the top:
SecFilterEngine Off
I’ve also heard back from my host who reported that mod_security did appear to be the culprit, specifically:
The rule list in play:
212700
212740
212860
212890
212970
212980
Once these were whitelisted the problem went away.
So in summary – turn mod_security off either via your host or the .htacess method or whitelist
Thanks again for your help
Offline