Home ›
Maintaining referential integrity with Drupal CCK nodereferenceMaintaining referential integrity with Drupal CCK nodereference
Submitted by Benjamin Melançon on April 20, 2009 - 2:45pm
Searched words:
drupal nodereference not deleting
reference intact
Problem: Drupal does not check to make sure a node isn't being used as a nodereference on another node before it is deleted.
Solution: Agaric's own Stefan Freudenberg has created a module to protect from this.
Notes:
Both of these are about the opposite direction:
-
Inconsistent site left after deleting a parent referenced in a nodereference field
http://drupal.org/node/362649 -
Handling CCK nodereference orphaned nodes when the parent is deleted?
http://drupal.org/node/364539
Resolution
More like this
- Referential Integrity for CCK | drupal.org
- Committing a patch to a contributed module you maintain
- Index and search specified fields for nodereference autocomplete
- Allow users to assign issues to other people in the project group (organic groups and project module integration)
- Drupal Salesforce-integrated Contact Form: Specific Use Case


Comments
Where can I find this module
Where can I find this module you have developed? I would love to test it out or find out more information. This is a huge problem with node references. I have only seen solutions that involve using the RULES module.
Does this module work for you?
http://drupal.org/project/cck_referential_integrity
Post new comment