Answers.Body: <p>Looks like this was a <a href="https://www.modsecurity.org/" rel="nofollow noreferrer">ModSecurity</a> tripping up the contents of the particular Redactor field in the POST request.</p>
  
  <p>The nuclear option for a fix is to disable ModSecurity.  The more nuanced fix is to find the particular rule that is tripping up the request and either disable it or to modify it so it allows that content through.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-10-28T01:32:40.090Z
Answers.LastActivityDate: 2018-10-28T01:32:40.090Z
Answers.UserDisplayName: Brad Bell
Body: <p>I'm having a weird issue with the Rich Text Editor (Redactor -> simple.json, only "bold" and "italic") on newly added fields and only ONE (that i know of) older field.
  Every time i add a "bold" format and then save the entry, it goes back to its previous state and never actually saves it.</p>
  
  <p>If there is a bold word in that block and i try to add / modify other blocks, nothing saves either.</p>
  
  <p>If i don't use "bold" in THAT specific field or newly created ones, it all works perfectly. Even the "italic" option works. If i use "bold" in an other older field, it works perfectly.</p>
  
  <p>It used to work like a charm, no updates has been done since (i did it afterwards to try and solve it: nothing changed).</p>
  
  <p>No trace about that in the craft logs.</p>
  
  <p>Any idea what's the problem? Or how to debug further? </p>
  
  <p>PS: That one is on Craft 2.7.2!</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-10-20T03:11:55.377Z
Comments.Text: Any chance you've got something like mod_security or Suhosin installed on your server?
Comments.UserDisplayName: Brad Bell
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-10-25T15:14:48.720Z
Comments.Text: @BradBell Right, i disabled mod_security on that specific dev, but is there a more stable solution, where i can keep mod_security in production mode?
Comments.UserDisplayName: Cryptomothy
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-10-27T21:46:41.107Z
Comments.Text: You'd need to find the specific mod_security rule that's tripping up the request and disable it or modify it so it allows that POST data through.
Comments.UserDisplayName: Brad Bell
Tags: <entry><redactor><saveentry><saving><onsaveentry>
Title: Entry not saving when Redactor bold
ThreadText: # Entry not saving when Redactor bold
  
  (Asked by: username_0 on 2018-10-19)
  
  I'm having a weird issue with the Rich Text Editor (Redactor -> simple.json, only "bold" and "italic") on newly added fields and only ONE (that i know of) older field.
  Every time i add a "bold" format and then save the entry, it goes back to its previous state and never actually saves it.
  
  If there is a bold word in that block and i try to add / modify other blocks, nothing saves either.
  
  If i don't use "bold" in THAT specific field or newly created ones, it all works perfectly. Even the "italic" option works. If i use "bold" in an other older field, it works perfectly.
  
  It used to work like a charm, no updates has been done since (i did it afterwards to try and solve it: nothing changed).
  
  No trace about that in the craft logs.
  
  Any idea what's the problem? Or how to debug further?
  
  PS: That one is on Craft 2.7.2!
  
  **Tags:** entry, redactor, saveentry, saving, onsaveentry
  
  > **Comments:**
  > **username_1**: Any chance you've got something like mod_security or Suhosin installed on your server?  
  > **username_0**: @username_1 Right, i disabled mod_security on that specific dev, but is there a more stable solution, where i can keep mod_security in production mode?  
  > **username_1**: You'd need to find the specific mod_security rule that's tripping up the request and disable it or modify it so it allows that POST data through.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2018-10-28. Score: 1
  
  Looks like this was a [ModSecurity](https://www.modsecurity.org/) tripping up the contents of the particular Redactor field in the POST request.
  
  The nuclear option for a fix is to disable ModSecurity. The more nuanced fix is to find the particular rule that is tripping up the request and either disable it or to modify it so it allows that content through.
  
  
  ---
  
  