Hi,

After I updated i18n to the latest release (7.x-1.8), translations for some fields became broken. I digged deeper and found that there are two problems:

1. in i18n_field_field_widget_form_alter() on line 180: if $element['#entity'] is empty field is not translatable. But this #entity could be stored in the other place in array (see at three screenshots attached). I suggest to remove this line at all.

2. According to the first item, some fields (even if their cardinality = 1) may store their labels into [0] array key. So we should process that situation too.

Patch that works for me attached.

As this release brokes translations for some fields I consider that this issue is major.

CommentFileSizeAuthor
i18n_field-not-all-fields-are-translated-0.patch1.75 KBspleshka
field_i18n_example_3.png60.33 KBspleshka
field_i18n_example_2.png95.6 KBspleshka
field_i18n_example_1.png60.42 KBspleshka

Comments

sergiu.popa’s picture

sergiu.popa commented

I had problems for an integer field. The translated label was not showing. After applying the patch, everything's okay. Thank you

bnadem’s picture

bnadem commented

Me too, I had problems translating a float field, now every thing seems OK, Thank you very much !

jibran’s picture

jibran
he/him
Primary language Urdu
Location Toronto, Canada
commented

Related #1157512: Labels are not translated with i18n_field for Drupal core. and #1961750: Unable to translate field label and description containing html tags/entities.

bojanz’s picture

bojanz commented
Status: Needs review » Closed (duplicate)

The most complete fix for this is in #1904368: [7.x-1.8 regression] Field translation fails in numerous situations. I am rerolling it now.
Closing this one.