Field Collection integration

Will these pathless entities become translatable ?

The first idea that comes to my mind is that their field could be translatable in the edit form of the parent entity, however proper integration with ET will need to be addressed by the Field collection module. What we can do here is introduce any change needed to make Field Collection integration straightforward.

Any patch is welcome if the modifications it introduces make sense, please be sure the problems you are experiencing are not related with #1341314: Nested call of entity_get_info() due to menu_get_router() in entity_translation_entity_info_alter() .

I get this notice as well. There is a tab for field translation in the entities' fields. I can translate all fields with labels/titles and values/field settings (e.g. in a html-select-element)

I'm not sure if these is afford of the title or the entity collection module, because there is no documentation of these modules as far as I can see.

My idea - if I'd got rid of the notice the translation will show up. I found a thread about a module, which implements the requirements of the entity translation module here: http://drupal.org/node/1587108#comment-6180310.

Or could you, plach kindly post a pathed version of the module here, if you succeeded?

Some related issues in the field collection queue, possibly duplicates:

• #1344672: Field Collection: Field translation (entity_translation) support.
• #1366220: Field collection translatable Field language for setHostEntity
• #1683784: Field Collection entities are untranslatable because they do not define valid base path

I haven't sorted through all the patches in the issues mentioned in #6, but it looks like respective patches are either for the old version of ET (current alpha2) or do not work at all.

To me it looks like the first step would be to properly register all base/edit paths for different field collection bundles. With #1418076: Allow for multiple base paths being committed this should now be possible.

One potential problem: ET currently requires the definition of a "default base path", and as far as I can see "field collection item" entities do not have one common base path. We might have to add an option to avoid adding a default path if it's not defined explicitly...

Please review new patch: #1344672-13: Field Collection: Field translation (entity_translation) support..

Actually all the needed work is being done in:

#1865244: Allow multiple translation handlers on the same form
#1344672: Field Collection: Field translation (entity_translation) support.

Marking as duplicate.