How to get this bug:

first build a new content type. It's very important that the content type must bee new, and make the steps with the first node.

Add an imagefield field with a default image.
Add a filefield

first step:
* Create the first node.
* We add a file to the node.
* The node will be see ok.

Second step:
* Edit the node.
* Remove the image.
* Save the node.

Or

first step:
* Create the first node.
* We add a file to the node.
* The node will be see ok.

Second step:
* Edit the node.
* Remove the image.
* Add a new image.
* Save the node.

Thirsth step:
* Edit the node.
* Remove the image.
* Save the node.

In both case the default image is delete from the node and from the files folder, but the image field default configuration is looking for it.

If you save the first node with the default image, and them delete o try to make the same with the second node or another one the image is not delete.

Thanks

Oskar

Comments

Interesting thanks for the report. When you edit a node, you shouldn't see the default image at all (it should only be shown on node view), so it sounds like something may be going wrong that the default image is appearing in the editing process at all. I'll see if I can reproduce this next time I'm working on FileField (which isn't very often these days, so this may be a while before I can confirm).

Version:6.x-3.9» 6.x-3.10

Issue confirmed on one of my site. Default image is inserted as a regular file with a unique fid but with the filepath set to the default image.
As soon as the image is removed, replaced by another one or the node is deleted, then the file on disk is deleted leading to broken images for other nodes using the default image.
This make default images unusable. Haven't tried on a clean install tho.

  • filefield 6.x-3.10
  • imagefield 6.x-3.10
  • cck 6.x-3.0-alpha3+13-dev