As we explore the interface around file management in #1448, we might want to think about how the user interface should work in regards to orphaned files which will deleted once they are removed from the content to which they have initially been uploaded.
Right now if you remove a file from a node, it will be cleaned up by garbage collection if it is not being used on any other nodes. We might want to ensure that the user knows that will happen, by providing a confirmation message during the save that orphans the file, perhaps along with the options to either delete the file now or mark it permanent.
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?