Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Currently, when using on i18n websites with Entity Translation EF just breaks translations.
For example, when viewing nodes in a translated language then pressing "save" on any EF-enabled field makes the node to lose title_field on original language which is overwritten with translated value.
Or another example - when a translatable field is not initialized with any value yet, it's language becomes 'und', instead of a node language.
Setting it to critical as it makes the module unusable on i18n sites.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | i18n-fields-fix-2015625-1.patch | 635 bytes | marc.mantha@outlook.com |
Comments
Comment #1
marc.mantha@outlook.com commentedProblem seems to be that there are variables to set field language, but the language is not detected anywhere. Try this patch.
Note: I made it against 7.x-1.0-alpha3, not sure if i should have made it against 7.x-1.x, it is the first time that create and submit at patch, let me know if I did something wrong.
Comment #2
marc.mantha@outlook.com commented