Field Collection has generally been working well with Entity Translation after some updates over the past year - as long as the field is set to be translatable from the beginning.

But there is a problem with a current site where I have existing non-translatable field collections, and I then enable translation afterwards. Looking in the database the fields for each language point to the same field collection ID, which means that if I update one then it updates the other.

This is a very large database of content and looking for a way to bulk update so that the translations point to a different (cloned) version of the field collection.

I attach a screenshot of a field table to show you what I mean. Is there any way to fix this retroactively?

Only local images are allowed.

CommentFileSizeAuthor
#2 thRxT.jpg117.19 KBmrchristophy
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

mrchristophy created an issue. See original summary.

mrchristophy’s picture

FileSize
117.19 KB