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
I second this-- I have a module in contrib now that I just marked as "deprecated", and I removed its sole alpha release (because a fix in Core made it obsolete). Just plain deleting the module...
Weekly Meetings July 23rd 2026
If there's some time left in the dev meeting - although it might rather be a topic for the PMC: We have nice documentation and procedures, how to provide projects in backdrop-contrib space...
Weekly Meetings July 23rd 2026
The need for a clear AI policy is growing. Please can this be a priority.
Weekly Meetings July 23rd 2026