We use cookies to improve your experience. No personal information is gathered and we don't serve ads. Cookies Policy.

ExpressionEngine Logo ExpressionEngine
Features Pricing Support Find A Developer
Partners Upgrades
Blog Add-Ons Learn
Docs Forums University
Log In or Sign Up
Log In Sign Up
ExpressionEngine Logo
Features Pro new Support Find A Developer
Partners Upgrades
Blog Add-Ons Learn
Docs Forums University Blog
  • Home
  • Forums

403 error saving a field with XHTML text formatting

How Do I?

Marcus Lee-Steere's avatar
Marcus Lee-Steere
11 posts
3 years ago
Marcus Lee-Steere's avatar Marcus Lee-Steere

Hi all, I am in the process of manually uploading a site from dev to the live environment and recreating all the data fields.

Seems that as soon as I select “XHTML” under text formatting (for a Textarea field type) I get a 403 error, though saving the field with “none” or “auto line break” causes no issues and the field saves.

Even if I then try to change the text formatting back to XHTML after it initially saves using “none” still produces the error.

Any thoughts as to where I might look to fix this would be very helpful.

Cheers

Marcus

       
Marcus Lee-Steere's avatar
Marcus Lee-Steere
11 posts
3 years ago
Marcus Lee-Steere's avatar Marcus Lee-Steere

OK, for anyone with similar issues, this turned out to be the result of a mod security rule being triggered. I also had an issues (also 403 errors) saving new channels and this was corrected when the host white listed the rule in question.

Marcus

? 1
       
bartrea's avatar
bartrea
2 posts
2 years ago
bartrea's avatar bartrea

@Marcus my issue is the same with yours, how do you fix it? Can you show me?

       
Marcus Lee-Steere's avatar
Marcus Lee-Steere
11 posts
2 years ago
Marcus Lee-Steere's avatar Marcus Lee-Steere

@bartrea as I mentioned above - for me at least - it was a mod security rule being triggered. To fix this I needed to log a ticket with my web hosting company and they were able to white-list the offending rule each time. I say each time because it happened several times over a period of two or three weeks, sometimes in very quick succession. In each case, apparently, a different rule was being triggered and needed to be white-listed each time. I think the short answer is to speak to your web host.

Also as an FYI, the last time this happened I worked out that there was a js and a css include in one of my templates for an image gallery script that didn’t have crossorigin=”anonymous” set. As soon as I added this the problem went away. I assume it was also a mod security problem but adding the crossorigin=”anonymous” element to the link addressed that particular issue.

       

Reply

Sign In To Reply

ExpressionEngine Home Features Pro Contact Version Support
Learn Docs University Forums
Resources Support Add-Ons Partners Blog
Privacy Terms Trademark Use License

Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.