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
@yorkshirepudding, In the end I fixed it by deleting the config/active folder contents, copying the config/staging/ files into config/active, importing the database again and clearing the caches...
Importing the staged config throws an error: another field with the same name already exists
Thanks, I have to go out now, I will try later on and report back
Importing the staged config throws an error: another field with the same name already exists
Hi Francis. Yes, what config do you have in staging for it? You might have configs like: field.field.field_video_embed field.instance.node.page....
Importing the staged config throws an error: another field with the same name already exists