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.
Right now, if a file is not currently being used on any piece of content, it is being deleted. That makes sense if the only way to add files is through a node form, and there is no easy way to reuse the file across the site in multiple places. However, as we move to a media library paradigm, where files are available for placement, it seems like people will expect files to stick around in the library even if they are not currently being used.
We should look at providing some site-wide controls for when and whether orphan files are deleted, with the ability to turn off the garbage collection, or set it to a custom amount of time that a file is not used before it is cleaned up.
Recent comments
Thanks!! Easiest for me to just give permission for anon users to see the admin theme. That worked. It's just for this one page.
Link field in a Content Type is malformed for annonymous user- Permission issue?
It looks like the screenshot of what you show it should look like is the admin theme whereas what they see is the front end theme. By default, such users won't have permissions to see the...
Link field in a Content Type is malformed for annonymous user- Permission issue?
I've added a new recipe. The recipe has no PHP code. It has two module dependencies (one of those depends on another contrib module and both depend on core modules that are normally enabled)...
The Future of Configuration Recipes for Backdrop CMS