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
I'd like to discuss how Backdrop treats default values for node fields. The current behavior when adding and creating content with default values, especially for text-based fields, isn't...
Weekly Meetings Nov 5th 2026
Only if you select "Delete all content in these content types before generating new content."
Devel module deletes default images folder
I recently ran into the same error: Exception: The configuration directory in settings.php is specified as 'files/config_[some-random-CMI-ID-here]/active', but this...
Live deployment Configuration Directory error