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
Thanks for the response, Herb! Since I posted that I did some more testing and have posted this issue https://github.com/backdrop-contrib/tfa_basic/issues/33 In fact, if both email...
TFA - how to setup fallback options 'per user'
I'll test this tomorrow to see if I can replicate the problem and report back. It's not "per user" so it should be working.
TFA - how to setup fallback options 'per user'
As I work through things I flush the caches after every change I make. As far as I can tell I have the custom module in the correct place (/modules/custom/fix_zero_search) and the file...
custom module not showing up in modules list