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
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