in D5 and 6 it was more a feature request. in D7 I sadly have to mark it as bug because it took me a week to find out that it was content taxonomies tree level limiter in the field management, which suppresses the locale and i18n support of the term field select list widget. This causes that the list is in default language only.
content taxonomy is an awesome module and thanks for the sharing! But we should put it in the info that it doesn't support it yet (suppress it)! There is no error message, and taxonomy translation is still a hussle for many. They will think it is caused by wrong translation method, and the search and try goes on and on.
Is there any line of code I can look on to contribute a patch for the next dev shot?
Best regards,
Digidog
Comments
Comment #1
devad commentedHi
I have i18n taxonomy translation enabled vocabulary.
I have chosen vocabulary / parent term to populate term reference field.
Autocomplete widget works fine in all languages, but select and checkbox lists are always populated with default language terms.
If diqidoq is still available to help with patch... it would be wonderful if someone can help with some tips or ideas where to look for bug-fix.