Hello. Since some time I'm struggling with the translation of the help text of some fields. On my drupal 7.41 I've 3 different languages, and English is the default. Before I was using Field translation 7.x-1.13 but I couldn't get the translations for the help text, only the default eng appeared. I've then installed Localize fields, imported the old translations (without errors), disabled and uninstalled Field Translation, but now I'm getting duplicated entries, first the translated text and then the English source! I'm thinking maybe another module is interfering but I don't know which.
Currently, apart from localize fields, I've installed, among the others,
Entity Translation (But it is disabled, I've used it some time ago but not now)
Localization client 7.x-1.3
Internationalization 7.x-1.13 (Filed translation disabled) which provides most of the translations for the website
Token 7.x-1.6+7-dev (installed but disabled, needed by Entities mod & others)
Localize Field configuration:
- Use translation context
- Yes, no fallback. Clean and predictable, but not the right choice if you're only testing this module. (nothing changes if I flag another option here)
- Don't translate the label and/or description that gets passed to other widget alterers (unflagged)
- Clear translation cache for affected languages for every change in the Field user interface (flagged)
- Clear translation cache of all languages now! (unflagged)
- Log and display translation changes (Log+display)
The fields where I'm testing Localize Field are Address Field & Flickr Photo (upload) Before I've thought it was a problem of Address Field, because for field Taxonomy it was working, but later I've noted that Flickr field wasn't correctly displaying the translation too. Maybe I'm missing something or I didn't configure Localize Filed in the right waybut after many tries now I don't know where to look anymore...
Thank you
Kinmen
Comments
Comment #2
jacobfriis commented@kinmen Thanks for your thorough report - great!
Your setup seem compatible with Localize Fields - particularly that competing utilities like i18n_field are disabled.
So, my immediate suspicion is that those custom field types - Address Field and Flickr Photo (plz provide drupal.org project links; I can't find these modules) - implement the Field API in a manner which deviates so much the from the core field modules, that Localize Fields cannot handle them.
So I would like you to try with a core field type - like text - too.
On the other hand, translation in itself does work, so those custom field types may not be the cause at all.
But please try with a core field type, anyway.
Another guess could be the Localization Client module.
I don't know what it does/how it works, but please try turning it off - and see if that makes a difference.
Comment #3
kinmen commentedHi. Thank you for the answer
I've added a text field in the "article" content type, and this works as expected, without duplicated entries in the translated text.
About Localization Module, it provides an "easy way" to translate text strings on the fly and send them (optionally) to the localization server of drupal
I've disabled it, cleared the cache of drupal & browser, but the problem persists
Address field project is here: https://www.drupal.org/project/addressfield
Here the issue which I've opened before https://www.drupal.org/node/2642518
Both source text and translation appear in a separate DIV with class=fieldset-description, inside
FlickrUP (https://www.drupal.org/project/flickrup) shows other duplicated text strings too, due to redundant labels in a table. I think I've found the problem here, it is related to css and labels there which cause redundancy of some text string and probably some in some containers were translated and other no.
BTW,
Under Translate interface->Translate[TAB] I've looked for my source string (translated+untranslated, all languages, etc) and I only get a reference for every field where it really should appear, for each related content type; apparently, no duplicated text strings there...
Thank you again for the help
Kinmen
Comment #4
jacobfriis commentedYou're ever so welcome. Glad things worked out for you ;-)