i18n - Internationalization - Multilingual : Tree widget is only available in the default language

thekayra - August 10, 2009 - 21:54
Project:Content Taxonomy
Version:6.x-1.0-rc1
Component:Taxonomy Tree
Category:support request
Priority:normal
Assigned:Unassigned
Status:active
Description

Hi all,

First of all, a big big applause for the module. It is working great and very useful.

Currently, I am trying to implement i18n on my multilingual website. My goal is to show taxonomy tree in the edit mode in the current language (selected by user, not default) of the site.

I read quite a few issues about it and also tried a couple of different scenarios to make things work.

1- with Localized Terms:
The tree widget is only available in the default language. It is blank in other languages and if it is required (as in my case) it is impossible finish editing.

2- with Per language terms:
If the relations are constructed properly, the tree widget works fine in all languages. However, this does not fit my requirements. As the node that I am trying to create is neutral in language and does not need to be translated, so no syncing features to take advantage of.

I have seen that some development was going on at http://drupal.org/node/298146. But from what I understand, it does not solve the issue for autocomplete or the tree widget.

Is there something that I am missing? And/or are you planning to do any development regarding that issue? Or should I find my own way of dealing with that?

Thanks all in advance,
Kayra.

#1

mh86 - August 11, 2009 - 08:30

I was recently working on i18n support for the Taxonomy Manager, but I focused on multilingual vocabularies (per language terms). If you want to localize terms, you can try this patch here http://drupal.org/files/issues/taxonomy_manager_localization_0.patch and report how it works :)

#2

thekayra - August 11, 2009 - 10:08

Thanks a lot for quick response.

Tried it. From what I can tell did not change anything for me.

# patch -b < taxonomy_manager_localization_0.patch
patching file taxonomy_manager.module
Hunk #1 succeeded at 402 (offset 11 lines).

I am also adding two screenshots. One in english, the other one in french. As you can see the tree widget disaapears in the french version.

AttachmentSize
tax_tree_en.JPG 38.76 KB
tax_tree_fr.JPG 23.59 KB

#3

thekayra - August 20, 2009 - 19:37

*bump*

#4

pixelmord - August 26, 2009 - 16:00

Hi,

I have the same issue with the "standard" select widget.
I also want to use localized terms of a vocabulary.
I can use the select box while creating and it is displayed in the current language, but when I want to edit the content item in a non default language, the widget (select-list) is displayed empty. I only can edit the version in the default language, if it exists, otherwise I have to temporarily switch the language to be able to edit.

Thanks for looking into that

Andi

#5

workonwomen - September 8, 2009 - 14:55

I think I have the same issue.
A content is created in the native language under the taxonomy/term/9
when I create a translation with "Create translation" /node/add/page?translation=127&language=de , then it is creating it, but
de/taxonomy/term/9 is not showing it.

Or if I decide to add the translation on "de" I mean German, then I have the same issue as the poster, that there is no tree view to select however I have choosen "Localize terms. Terms are common for all languages, but their name and description may be localized."

What can I do? Might the patch help?

#6

pixelmord - October 21, 2009 - 14:51

I solved my issue now with installing the active_translation module. It seems that the modified queries to display also the "original" language as fallback also helps with the query that is selecting and rendering the taxonomy terms of a localized vocabulary in edit mode.

steps I took:
- I installed active_translation module
- made the setting to display all nodes in all languages in the administration page for i8n (/admin/settings/language/i18n/configure)
- also set there to switch interface language in edit mode (although that wasn't needed to fix the problem, I think)

Hope that helps you too!

 
 

Drupal is a registered trademark of Dries Buytaert.