README.txt 2.1 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546
  1. Field collection
  2. -----------------
  3. Provides a field collection field, to which any number of fields can be attached.
  4. Each field collection item is internally represented as an entity, which is
  5. referenced via the field collection field in the host entity. While
  6. conceptually field collections are treated as part of the host entity, each
  7. field collection item may also be viewed and edited separately.
  8. Usage
  9. ------
  10. * Add a field collection field to any entity, e.g. to a node. For that use the
  11. the usual "Manage fields" interface provided by the "field ui" module of
  12. Drupal, e.g. "Admin -> Structure-> Content types -> Article -> Manage fields".
  13. * Then go to "Admin -> Structure-> Field collection" to define some fields for
  14. the created field collection.
  15. * By the default, the field collection is not shown during editing of the host
  16. entity. However, some links for adding, editing or deleting field collection
  17. items is shown when the host entity is viewed.
  18. * Widgets for embedding the form for creating field collections in the
  19. host-entity can be provided by any module. In future the field collection
  20. module might provide such widgets itself too.
  21. Using field collection with entity translation
  22. -----------------------------------------------
  23. * Field collection items must be selected as a translatable entity type at
  24. Admin -> Config -> Regional -> Entity Translation.
  25. * The common use case is to leave the field collection field untranslatable
  26. and set the necessary fields inside it to translatable. There is currently
  27. a known issue where a host can not be translated unless it has at least
  28. one other field that is translatable, even if some fields inside one of
  29. its field collections are translatable.
  30. * The alternate use case is to make the field collection field in the host
  31. translatable. If this is done it does not matter whether the inner fields
  32. are set to translatable or not, they will all be translatable as every
  33. language for the host will have a completely separate copy of the field
  34. collection item(s).