On a multilingual site (i18n), if a vocabulary is set to "Localize. Terms are common for all languages, but their name and description may be localized.", views query doesn't show the translated vocabulary name and/or terms but the site default language.

Comments

aristeides’s picture

Status: Closed (works as designed) » Active

Please ignore, not a views issue.

fuse’s picture

Did you find a solution for this issue? I am having the same problem.

aristeides’s picture

Status: Active » Closed (works as designed)

Yes. It actually is NOT an issue, it's just not obvious. :)
When you set your vocabularies to localize a new formatter appears on that view field.
Default formatters are "plain text" and "link".
After localizing the vocabularies there are formatters "plain text (localized)" and "link (localized)".

fuse’s picture

Status: Active » Closed (works as designed)

Yes, but only when you have a view of "Type: content". I am using a view of "type: term" and you don't have any options to choose the formatter.
So I think this issue still exist and should be solved?

fuse’s picture

Status: Closed (works as designed) » Needs work

Changing the status unless someone can explain how to do this.

dawehner’s picture

Project: Views (for Drupal 7) » Internationalization Views
Issue tags: -i18n, -taxonomy term

Move to i18nviews and remove silly tags.

fuse’s picture

Could you explain a bit more? I had i18n views already installed, but that doesn't help, unless I am missing something?

What I have is:

View of taxonomy terms (type: term) with "Taxonomy term: Name" as one of the fields. My taxonomy is set to: "Localize. Terms are common for all languages, but their name and description may be localized" and all terms have been translated, but when I switch language my terms are not translating.

vflirt’s picture

Where you select the "Taxonomy term: Name" should be changed, you should select "Taxonomy term: Name (translated)" . This will show the translated name.

fuse’s picture

Status: Needs work » Closed (works as designed)

Ok, this does indeed work. Thank you for the feedback.

Changed the status.

alauzon’s picture

In which admin page do you do that selection : "Taxonomy term: Name (translated)"?

aristeides’s picture

it's a views field. When you add a new field, you can choose from many options. Among them there is one called "Taxonomy term: Name (translated)". So instead of adding "Taxonomy term: Name", choose that one instead. At least for me it worked...

alauzon’s picture

Is it in the uc_catalog view?

alauzon’s picture

I tried to add a field but "Taxonomy term: Name (translated)" was not listed, only "Taxonomy term: Name" was. What do I need to do?

alauzon’s picture

Ha, I found it. I needed to install i18n_views!

Thank you for your answers, guys.