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
Hi ian, so, in your case all the other admin pages work fine, including the status page, only admin/reports/updates fails? But you can access admin/reports? Weird... I...
Update Report thows "Access denied You are not authorized to access this page."
The File (Field) Paths module should be able to move existing files. I've not tested it, but the module description says: Retroactive updates - rename and/or move...
Moving from /files into subdirectories
Yes indeed. We are exploring a few other more costly options, but as we are a low-resource start-up, we could save a lot of money by integrating Backdrop, CiviCRM and Ubercart for our membership...
UberPOS for Backdrop?