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
For our DEV meeting: an older bug needs (and could have) a fix. Issue #5729 - Views: Search Filter: On Empty Input "Show None" option Shows All There are 2 pull requests, but one...
February 26th, 2026 - Weekly Meetings
Ruby Text can be a bit of a hassle to edit... Yes, I can imagine that. No idea, how an editor dialog (or whatever) for easier editing of those should look like - in terms of...
Specific tags to work in CKEditor 5
"why are these tags only relevant for admins?" I'm allowing the editor as well. That being said, Ruby Text can be a bit of a hassle to edit... easy to accidentally delete a tag or part of a...
Specific tags to work in CKEditor 5