As we proceed with the issues in #1448, and add more features to file entities, it seems like the expectations around how files are cleaned up by the system will change, and if we allow site-wide settings for garbage collection in #2896, we should also look at settings on a per-file-entity basis.
We currently have a flag in the database to mark whether files in the database are permanent, which excludes files from being deleted during garbage collection. I believe that this is checked if a file is uploaded outside of the context of a node field.
We might want to expose that flag to users, so that when they are adding/editing a file entity, they can mark whether a file should be excluded from garbage collection if it is no longer being used.
Recent comments
Correct, if you add multiple condition statements they are treated as AND so it would appear to the system as: node/103 AND node/91 which will never happen. Glad you found the way to...
Blocks (custom) not displaying in Harris sidebars with visibility condition set to more than one url path (node)
YES! That works. This whole thing is extremely bizarre, though. On the site I'm building (not the sandbox demo), I had a view that was displaying multiple images correctly (i.e. once, not...
Duplicated images in view
Maybe "Query settings" : "Distinct". If there are multiple identical items, each will be displayed only once. You can use this to try and remove duplicates from a view, though it...
Duplicated images in view