I have this problem with translation of a custom checkbox (boolean) field. To be specific, I'm able to translate everything but the options (Yes / No) that are shown on node view page.

I have the modules locale, i18n_nodes, and i18n_fields enabled, and translation strings imported (with corresponding context and to appropriate textgroup), and default language set to English. The translation shows correctly everywhere but on node view where it's still untranslated.

The content type is custom and is created via hook_node_info() and it's fields via field_create_field, and field create_instance.

BTW: I don't need translation of the content (every node will always have just one language and should be accessible regardless of what language the user has selected) but only of the user interface (descriptions, titles, ...). So if there's a simpler way to translate my custom fields and content types, please let me know.

Screenshot proofs that I've done everything I could:

Settings: Language settings Field settings .po file that is uploaded to appropriete textgroup (field) An edit from translate option that shows .po is loaded

Edit page: Everything is correctly translated on edit

View page (note the only string that is in English but should be in Czech and should be Aktivni) Active is not translated

  • That's odd. Have you tried translating the string with Localization Client? Jul 13, 2015 at 17:56
  • @othermachines tried that but it didn't work with fields at all... (it showed circa 50 % of field related strings on page) and of course if found nothing for "Active"...
    – Petrroll
    Jul 13, 2015 at 18:14

1 Answer 1


Try what's mentioned in Comment #1 of issue # 1762488, i.e:

... visit 'Manage Display' and switch from "Default" to "Default translated".

  • Thanks for the accept! Looks like that was the missing piece of your i18n 'puzzle' ... Oh well, multilanguage sites, so much things to know and remember to make it work ... Anyway, I slightly enhance the title of your question also, to ake it more accurate, ok? Jul 14, 2015 at 9:22
  • Yep, that looks better and thanks for the info. I wouldn't have found out about that myself :).
    – Petrroll
    Jul 14, 2015 at 11:37
  • "Merci" (oeps, no French here ...: thank you) ... To be honest, when I first saw your question, it occured to me that I never ran into such (detailed) translation issue. So I learned from it myself also, for new time I have a similar field ... Note: I might soon "investigate" drupal.stackexchange.com/search?q=user%3A17790+is%3Aq Jul 14, 2015 at 11:44

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.