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
Did it on my end on some sites without problem. I don't know why this update would be different for you. Perhaps some file permission changes?
Update 1.35.1 appears to install but hasn't
The issue with checking for updates in the BackdropCMS dashboard makes website development and maintenance more difficult. I manage more than ten websites hosted by two different providers, one...
Unable to run update - fails with Connection timed out
Recently came back to see if translation issues are fixed, with the latest version: Page translations are fixed, but the issue with taxonomy and menus are still there. Localized terms show...
Taxonomy localization, pathauto and tokens