intro.html 1.1 KB

1234567891011121314151617
  1. <p>CER's purpose is to keep reference fields synchronized with each other.
  2. For example, if you have a node (&quot;Alice&quot;) with a user reference field,
  3. and a user (&quot;Bob&quot;) with a node reference field, and you make Alice
  4. reference Bob, CER will automatically give Bob a back-reference to Alice. If
  5. Alice subsequently dereferences Bob, Bob will automatically deference Alice.
  6. Or, if Alice is deleted, Bob will lose his reference to Alice. CER does all
  7. this transparently.</p>
  8. <p>CER is a powerful module. It lets you create relationships between different
  9. &quot;reference-type&quot; fields. A <dfn>reference-type</dfn> field is, simply,
  10. any kind of field that references another entity. Out of the box, CER supports
  11. Entity Reference, Node Reference, User Reference, and core Taxonomy Term
  12. Reference fields. It also includes a pair of add-on modules supporting Profile2
  13. and Commerce Product Reference fields. CER also has an object-oriented plugin
  14. API that you can leverage if you need to support other types of reference
  15. fields or alter CER's behavior. (More information about CER's API
  16. can be found in cer.api.php.)</p>