Answers.Body: <p>Does everything else seem to be working? Maybe try removing the field from your section and then re-add it?  </p>
  
  <p>You might also try clearing the caches: Settings -> Clear Caches.</p>
  
  <p>Craft logs various things to <code>craft/storage/runtime/logs/craft.log</code> If there's an error of some kind, maybe with your database, it'll show up there.</p>
  
  <p>If that doesn't clear it up, shoot P&amp;T a message and have them take a look at your install. You can do that right from the control panel.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-02-22T11:19:43.203Z
Answers.Text: Everything else is working just fine. The log contains so much data that I can't really make any sense of it - there's not anything in there that looks like an error, and the CP doesn't display any error messages which I would expect if there was a DB or application error.
  
  I've sent a message to P&T for further analysis, as this would seem to be a bug.
Answers.UserDisplayName: binarymonkey
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-02-21T22:24:20.767Z
Answers.LastActivityDate: 2016-02-21T22:24:20.767Z
Answers.UserDisplayName: RitterKnight
Answers.Body: <p>After speaking with Brandon from the Craft team, we narrowed this issue down to a PHP module called <strong>Suhosin</strong>.</p>
  
  <p>The module apparently strips POST variables that are zero length / empty, before they hit PHP. Craft needs to see those to know the field is to be set to empty, otherwise the field won't be changed.</p>
  
  <p>The Suhosin config setting <code>suhosin.post.disallow_nul</code> may help others who wish to keep Suhosin running, however I opted to simply remove the module entirely after reading a few less than favourable notes about it elsewhere.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-02-23T13:55:53.247Z
Answers.LastActivityDate: 2016-02-23T13:55:53.247Z
Answers.UserDisplayName: binarymonkey
Body: <p>I've installed Craft Personal 2.5.2763, and have set up my own simple blog.</p>
  
  <p>For each Entry in the Blog Channel, I've set up an Asset Field, which is used for the header image displayed on the blog entry template.</p>
  
  <p>I'd like this Asset field to be optional, as I'll be displaying a default image if one isn't defined in the Control Panel.</p>
  
  <p>Adding an image to the field works great, but I'm seemingly unable to remove it once it has been assigned and saved when I go to edit the Entry and click the "Remove" icon.</p>
  
  <p><a href="https://i.sstatic.net/Ocp1w.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/Ocp1w.png" alt="Screenshot of CP remove asset"></a></p>
  
  <p>When clicking the Remove icon, The image disappears from the CP edit page as you'd expect, but when clicking "Save", it seems the removal of that image is <strong>not</strong> actually being saved, as it is still there when I go back in to edit the Entry.</p>
  
  <p>UPDATE: I've also found this issue on a normal Text field too. If you set the Text field to some data, save, then go back to edit, delete all text, save, then the data is not removed and the original data remains.</p>
  
  <p>Am I doing something wrong, or is this a bug?</p>
  
  <p>Thanks in advance for any help.</p>
  
Tags: <assets><control-panel><field>
Title: How to allow Asset removal in the Control Panel for an Entry
ThreadText: # How to allow Asset removal in the Control Panel for an Entry
  
  (Asked by: username_0 on 2016-02-21)
  
  I've installed Craft Personal 2.5.2763, and have set up my own simple blog.
  
  For each Entry in the Blog Channel, I've set up an Asset Field, which is used for the header image displayed on the blog entry template.
  
  I'd like this Asset field to be optional, as I'll be displaying a default image if one isn't defined in the Control Panel.
  
  Adding an image to the field works great, but I'm seemingly unable to remove it once it has been assigned and saved when I go to edit the Entry and click the "Remove" icon.
  
  [![Screenshot of CP remove asset](https://i.sstatic.net/Ocp1w.png)](https://i.sstatic.net/Ocp1w.png)
  
  When clicking the Remove icon, The image disappears from the CP edit page as you'd expect, but when clicking "Save", it seems the removal of that image is **not** actually being saved, as it is still there when I go back in to edit the Entry.
  
  UPDATE: I've also found this issue on a normal Text field too. If you set the Text field to some data, save, then go back to edit, delete all text, save, then the data is not removed and the original data remains.
  
  Am I doing something wrong, or is this a bug?
  
  Thanks in advance for any help.
  
  **Tags:** assets, control-panel, field
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_1 on 2016-02-21. Score: 1
  
  Does everything else seem to be working? Maybe try removing the field from your section and then re-add it?
  
  You might also try clearing the caches: Settings -> Clear Caches.
  
  Craft logs various things to `craft/storage/runtime/logs/craft.log` If there's an error of some kind, maybe with your database, it'll show up there.
  
  If that doesn't clear it up, shoot P&T a message and have them take a look at your install. You can do that right from the control panel.
  
  > **Comments:**
  > **username_0**: Everything else is working just fine. The log contains so much data that I can't really make any sense of it - there's not anything in there that looks like an error, and the CP doesn't display any error messages which I would expect if there was a DB or application error.  I've sent a message to P&T for further analysis, as this would seem to be a bug.  
  
  ---
  
  ### Answer by username_0 on 2016-02-23. Score: 0
  
  After speaking with Brandon from the Craft team, we narrowed this issue down to a PHP module called **Suhosin**.
  
  The module apparently strips POST variables that are zero length / empty, before they hit PHP. Craft needs to see those to know the field is to be set to empty, otherwise the field won't be changed.
  
  The Suhosin config setting `suhosin.post.disallow_nul` may help others who wish to keep Suhosin running, however I opted to simply remove the module entirely after reading a few less than favourable notes about it elsewhere.
  
  
  ---
  
  