When upgrading to CER 3.x from 1.x or 2.x, you MUST clear all your caches before running update.php! This is so new classes can be registered with the autoloader. If you forget to do this you will probably get fatal errors while running update.php.
This is the successor of Corresponding Node References, so a shout-out goes to everyone who ever worked on it!
CER keeps reference fields in sync. If you have two entities that refer to each other using Entity Reference (or some other kind of reference field), it saves you the trouble of double-editing your entities in order to have them point at each other. If entity Alice references entity Bob, CER will make Bob reference Alice, and keep the references up-to-date when either entity is updated or deleted.
- 7.x-3.x depends on CTools, Entity API and Table Element, as well as a soft dependency on Hierarchical Select.
- 7.x-2.x depends only on Entity Reference.
- Prefer 3.x. It's the active development branch and is a quantum leap over 2.x, featuring a better UI, support for field collections, and native support for other field types besides Entity Reference. It includes add-on modules to integrate with Commerce and Profile2, as well as a module to override CER settings for individual entities.
- 2.x is now deprecated, and once there is a stable 3.x release, it will be retired. The only real reason to use it is if you have 1.x and fear database updates -- 2.x does not change the database in any way, so you can drop it in over 1.x safely and easily revert if you run into problems. 2.x's main improvement over 1.x is that it has proper support for Entity Reference fields that use Views as a backend.
CER 1.x is no longer supported. If you're still using it, you should update to 3.x.
This module has been sponsored by Digital Loom.