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