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.
GitHub Issue #:
2899
Recent comments
In page.tpl.php you can get the current path and add it to the class array $classes[] = 'path-' . str_replace('/', '', $_SERVER['REQUEST_URI']); You will get an original class for each page....
Insert custom class into body tag
https://www.drupal.org/project/views/issues/1266388 shows that this is an architectural issue, and requires another 2 hooks being adjusted. It would be really nice to add comments/notes to...
node access
Hmmm, from D7 ancient tomes: from https://drupal.stackexchange.com/questions/7056/limit-which-roles-can-view-a-node-basing-on-its-content-type yet https://docs.backdropcms.org/api/...
node access