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
@themetman Good to hear your solution. May be helpful for others in the future.
Write Permission Problems on files, ../private and /tmp on my Laptop
It was the ProtectHome setting in the apache service which was the problem. I did this: systemctl edit apache2.service Then added this: [Service] ProtectHome=no...
Write Permission Problems on files, ../private and /tmp on my Laptop
I don't have leaflet, but I have experienced random disappearances of the bar over the years. I quit spending time on it, but not before adjusting the css spacing, which did reduce the number of...
Disappearing administration bar. Is this a Leaflet or a Backdrop bug?