| Attribute | Average |
|---|---|
| Features | 4.83 / 5 |
| Reliability | 5 / 5 |
| Ease Of Use | 4.33 / 5 |
| Documentation | 4.67 / 5 |
| Vote Count | 6 |
Description It syncs the node reference between two node types which have a nodereference to each other, so double editing nodes is no more needed. If one node has a reference the other node receives also a reference to the saved node if it is referenced in that node. Updates Since release 6.x-2.0 single... [More...]
| Maintainer: | domidc |
| Links: | |
| Categories: | Administration, Content, Content Construction Kit (CCK), Utility |
| Version | Date | Files | Release notes |
|---|---|---|---|
| 6.x-3.3 | 2010-May-07 | Download | Recommended |
Options: Add a review
I'm migrating a site with some relatively simple many-to-many relationships that are not suitable for solving using taxonomies.
This module has made creating and maintaining the Drupal node references trivially simple.
Good work.
Needed it on a job site. While linking up over a 100 companies with multiple jobs, not needing to tell the jobs afterwards which company they belonged to was awesome. Also when I made a mistake on a company and I would see it on a job I could correct it on the job and it would be ok on the company too. No more the frustration of double editing. Thanks!
I dont think thaddeusmt has checked out the module properly. It is possible to explicitly map which node references you want to use when one content type has multiple reference fields.
Backreference should not be used with shared node reference fields on multiple content types (http://drupal.org/node/572242). A feature cnr does support: Choosing a relation (one-one, one-many, many-one, many-many) by content type and by reference instance. Which makes your instances re-useable on multiple content types
The only thing cnr doesnt support right now is the ability to set the amount of references allowed. It can only choose between one or many references.
Since this is a rare case CNR covers 99% of the cases where this type of functionality is needed.
Going to a separate config page (not the Content Type page) to set the correspondence rules was confusing. Also, didn't let me explicitly map which node references I wanted to use when one content type had multiple reference fields. CNR will probably get the job done, but I would recommend BackReference instead right now. Much easier to use, and more powerful because of it.
Excellent Module ! thanks for the smart implementation.
Goodbye nodeReferrer !
If you user Many-to-Many relationship with Node Reference CCK this is a must have module!!! Thanks
"Simple and easy to use module. It really speeds up the work flow for creating your menu's. I hope it..."
"A must have on a multilanguage site. Not only russian or arabic, but also german or french have their..."
"Very simple and well implemented. Don't need to read docs, just install and enable. Would be nice if..."
