Révision a1cafe7e
Ajouté par Assos Assos il y a plus de 4 ans
| drupal7/sites/all/modules/field_collection/README.txt | ||
|---|---|---|
| 1 |
Field collection |
|
| 2 |
----------------- |
|
| 3 |
Provides a field collection field, to which any number of fields can be attached. |
|
| 1 |
CONTENTS OF THIS FILE |
|
| 2 |
--------------------- |
|
| 3 |
|
|
| 4 |
* Introduction |
|
| 5 |
* Requirements |
|
| 6 |
* Installation |
|
| 7 |
* Configuration |
|
| 8 |
* Using field collection with entity translation |
|
| 9 |
* Maintainers |
|
| 10 |
|
|
| 11 |
|
|
| 12 |
INTRODUCTION |
|
| 13 |
------------ |
|
| 14 |
|
|
| 15 |
Provides a field collection field to which any number of fields can be attached. |
|
| 4 | 16 |
|
| 5 | 17 |
Each field collection item is internally represented as an entity, which is |
| 6 | 18 |
referenced via the field collection field in the host entity. While |
| ... | ... | |
| 8 | 20 |
field collection item may also be viewed and edited separately. |
| 9 | 21 |
|
| 10 | 22 |
|
| 11 |
Usage |
|
| 12 |
------ |
|
| 23 |
REQUIREMENTS |
|
| 24 |
------------ |
|
| 25 |
|
|
| 26 |
This project require the following projects: |
|
| 27 |
|
|
| 28 |
* Entity API (https://www.drupal.org/project/entity) |
|
| 29 |
|
|
| 13 | 30 |
|
| 14 |
* Add a field collection field to any entity, e.g. to a node. For that use the |
|
| 15 |
the usual "Manage fields" interface provided by the "field ui" module of |
|
| 16 |
Drupal, e.g. "Admin -> Structure-> Content types -> Article -> Manage fields". |
|
| 31 |
INSTALLATION |
|
| 32 |
------------ |
|
| 17 | 33 |
|
| 18 |
* Then go to "Admin -> Structure-> Field collection" to define some fields for |
|
| 34 |
Install as you would normally install a contributed Drupal. See: |
|
| 35 |
https://drupal.org/documentation/install/modules-themes/modules-7 for further |
|
| 36 |
information. |
|
| 37 |
|
|
| 38 |
|
|
| 39 |
CONFIGURATION |
|
| 40 |
------------- |
|
| 41 |
|
|
| 42 |
* Add a field collection field to any entity, e.g. to a node. For that use the |
|
| 43 |
the usual "Manage fields" interface provided by the "field ui" project of |
|
| 44 |
Drupal, e.g "Admin -> Structure -> Content types -> Article -> Manage fields" |
|
| 45 |
|
|
| 46 |
* Then go to "Admin -> Structure-> Field Collection" to define some fields for |
|
| 19 | 47 |
the created field collection. |
| 20 | 48 |
|
| 21 |
* By the default, the field collection is not shown during editing of the host
|
|
| 49 |
* By the default, the field collection is not shown during editing of the host |
|
| 22 | 50 |
entity. However, some links for adding, editing or deleting field collection |
| 23 | 51 |
items is shown when the host entity is viewed. |
| 24 | 52 |
|
| 25 |
* Widgets for embedding the form for creating field collections in the
|
|
| 53 |
* Widgets for embedding the form for creating field collections in the |
|
| 26 | 54 |
host-entity can be provided by any module. In future the field collection |
| 27 |
module might provide such widgets itself too.
|
|
| 55 |
project might provide such widgets itself too.
|
|
| 28 | 56 |
|
| 29 | 57 |
|
| 30 |
Using field collection with entity translation
|
|
| 31 |
-----------------------------------------------
|
|
| 58 |
USING FIELD COLLECTION WITH ENTITY TRANSLATION
|
|
| 59 |
----------- |
|
| 32 | 60 |
|
| 33 |
* Field collection items must be selected as a translatable entity type at
|
|
| 61 |
* Field Collection items must be selected as a translatable entity type at
|
|
| 34 | 62 |
Admin -> Config -> Regional -> Entity Translation. |
| 35 | 63 |
|
| 36 | 64 |
* The common use case is to leave the field collection field untranslatable |
| ... | ... | |
| 45 | 73 |
language for the host will have a completely separate copy of the field |
| 46 | 74 |
collection item(s). |
| 47 | 75 |
|
| 48 |
* When using nested field collections the configuration of the fields and |
|
| 76 |
* When using nested field collections, the configuration of the fields and
|
|
| 49 | 77 |
field collections is very important. The recommended approach is to first |
| 50 |
enable entity translation as defined in step 1, and set the outer
|
|
| 51 |
field collection field as translatable, and all it’s sub-fields to language
|
|
| 52 |
undefined. Also the sub-field collections and it’s sub-fields should be
|
|
| 78 |
enable entity translation as defined in step 1, and set the outer |
|
| 79 |
field collection field as translatable and all its sub-fields to language
|
|
| 80 |
undefined. The sub-field collections and its sub-fields should also be
|
|
| 53 | 81 |
set to language undefined. This will ensure that every language of the host |
| 54 | 82 |
will have a completely separate copy of the field collection item(s) and |
| 55 |
it’s fields. |
|
| 83 |
its fields. |
|
| 84 |
|
|
| 85 |
|
|
| 86 |
MAINTAINERS |
|
| 87 |
----------- |
|
| 88 |
|
|
| 89 |
Current maintainers: |
|
| 90 |
* Joel Muzzerall (jmuzz) - https://www.drupal.org/user/2607886 |
|
| 91 |
* Joel Farris (Senpai) - https://www.drupal.org/user/65470 |
|
| 92 |
* Lee Rowlands (larowlan) - https://www.drupal.org/user/395439 |
|
| 93 |
* Nedjo Rogers (nedjo) - https://www.drupal.org/user/4481 |
|
| 94 |
* Ra Mänd (ram4nd) - https://www.drupal.org/user/601534 |
|
| 95 |
* Renato Gonçalves (RenatoG) - https://www.drupal.org/user/3326031 |
|
| 96 |
* Wolfgang Ziegler (fago) - https://www.drupal.org/user/16747 |
|
Formats disponibles : Unified diff
Weekly update of contrib modules