Field collection does not support node translation properly. Multilingual sites using the node translation method are not able to use Field collection.
Drupal 7 has two methods for translation: the node translation method used in previous versions of Drupal, and the Field translation method that will be used in future versions of Drupal (see Drupal 7's new multilingual systems (part 4) - Node translation). For the issue covering Field Translation, see .
As stated in the module's README.txt
* As of now, the field-collection field does not properly respect different
revisions or languages of the host entity. Thus, for now it is suggested to
only use the field for entities that are not revisionable and translatable.
Provide support to have Field collections work with note translation and utilize the $obj->language parameter.
User interface changes
None at present, though some administrative configuration options may be relevant or necessary. For example: whether files used by image fields or file fields should be physically duplicated or whether translated fields should reference the same fid.
* Use of $langcode and LANGUAGE_NONE would change to be relevant to the host entity.
* Duplication of files for image fields and file fields may occur.
Original (related) reports by dbravender and FiNeX
BEWARE: The patch on #211 includes an implementation of field_collection_update_7005(). When updating the field_collection module after using this patch, keep an eye on your field_collection_update hooks, as if another patch gets in which implements 7005 then that will not be executed on your site - you will need to do so manually.
|FAILED: [[SimpleTest]]: [MySQL] Unable to apply patch 1316162-fix-shared-field_collection_items-217.patch. Unable to apply patch. See the log in the details link for more information. |
[ View ]
|PASSED: [[SimpleTest]]: [MySQL] 162 pass(es). |
[ View ]
|#98||Screen Shot 2013-03-30 at 8.24.08 AM.png||48.95 KB||RobKoberg|