Dealing with unexpected file deletion due to incorrect file usage

I think @Paul Dudink had a good suggestion in #87 to look into the entity_usage → module. If all this is caused by file_usage counts being wrong, shouldn't we look at how a contrib module is doing the same thing and see if it's better?

I'm also wondering has anyone has tried media_files_handler → ?

For those of us who need deleted files to actually be deleted, what is the best option? Just enable $config['file.settings']['make_unused_managed_files_temporary'] = TRUE; and cross our fingers?

For those of us who need deleted files to actually be deleted, what is the best option? Just enable $config['file.settings']['make_unused_managed_files_temporary'] = TRUE; and cross our fingers?

Not cross your fingers, but actively verify that it works for your site and your use cases.

That this setting even exists is a stopgap workaround, to remove it again, we need to fix the bugs around file usage and we need people to test it and report issues they find, if any. FWIW, 🐛 $entity->isDefaultTranslation() behaves incorrectly when changing default translation, causing file/image field usage to be set to zero, causing files to be deleted Fixed is the only one that I'm aware of, we have that setting enabled on quite a lot of production sites and it's working well for us.

If you have a multilingual site, you definitely want to use that.

I started researching what's going on around this issue. I will likely use 'make_unused_managed_files_temporary' for now, but I was wondering if a module that (as opposed to most of the modules out there that tries to add some smarter capability) that adds a setting to each file field so that you can manually set which file file flags a file for deletion when the entity is removed.

Adding 🌱 Add a reliable entity-usage system to core Active to related issues.