- Issue created by @mrshowerman
- 🇩🇪Germany hexabinaer Berlin, Germany
This is an unfortunate known issue. To be honest, we didn't take it seriously enough because it appeared during test nodes cleanup. To avoid unintended damage, we introduced the "unpublish" workflow state and restricted the node delete permissions to higher privileged roles.
But now that the scenario has been reported for the 3rd time already (2 off-platform) we should find a robust solution.
I am still having a hard time understanding the user story that makes people delete a (reusable) event description. Understanding the situation would help deciding upon one of the possible solutions.
By the way, the solution must handle any entities that are referenced by a mandatory field as well. Plus cleanup of non-mandatory fields like article "mentions" references.
The decision is to be made between these 2 principles
- Disallow deletion with reference to dependencies (feedback information page lists referencing nodes linked)
- Bulk deletion based on dependency detection (confirmation page lists current and referencing nodes, confirmation option complete - or cancel) - 🇩🇪Germany mrshowerman Munich
I know this is a tough one.
We used the Entity Reference Integrity → module in one of our projects in order to deny people from deleting nodes that are still referenced somewhere.
But I have to admit that this introduced so many problems (e.g. false positives) that we decided to remove the module again.