Maybe am I missing something but I can't get taxonomy terms translations to work in custom views. It works well with drupal core, but in my views, these are only shown in english (default) language.

Thanks.

Drupal core: 7.14
i18n: 7.x-1.5
entity_translation: 7.x-1.0-alpha2
views 7.x-3.3

Comments

heretic381’s picture

heretic381 CreditAttribution: heretic381 commented

Finally I wound a workaround for this.
Taxonomy terms are correctly translated in views. After days of looking for any solution it came to my mind that there must be something similar to the node title which comes with two instances(fields) in views. And that was the case. There's two different name fields for taxonomy terms. So we must use both, rewriting the output of the core taxonomy term field with the ET one. Rewriting is needed if user want to preserve the taxonomy link, which is the case most of the time.

IMHO, an effort in writing well detailed documentation is necessary. This would probably save a lot of time to all site builders. Presuming developers are already overwhelmed, some co-maintainers could be in charge of it.

plach’s picture

plach
he/him
Primary language Italian
Location Venezia
CreditAttribution: plach commented

Well, currenlty there is no actual co-maintainer and, yes, as are you saying it's really hard to maintain Title and Entity translation together with core work. I think you've done a godd job in researching and submitting a solution, what about putting your experience together so that we can provide a more useful documentation to new users?

plach’s picture

plach
he/him
Primary language Italian
Location Venezia
CreditAttribution: plach commented
Status: Active » Fixed

Also, I guess this is fixed.

heretic381’s picture

heretic381 CreditAttribution: heretic381 commented

Yes, it's fixed.
I'll try to summarize my drupal translation experience, especially ET and Title module. There's really lot of things to write about, and I've probably already forgot lot of staff done on my site during last two months.
Do you mean a sort of article?

plach’s picture

plach
he/him
Primary language Italian
Location Venezia
CreditAttribution: plach commented

Well, you may write a tutorial on your blog or create a new handbook page with your site recipe.

heretic381’s picture

heretic381 CreditAttribution: heretic381 commented

Ok, keep in touch.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

Anonymous’s picture

(not verified) CreditAttribution: commented
Issue summary: View changes

system info

MXT’s picture

MXT
Primary language Italian
Location Milan
CreditAttribution: MXT commented
Issue summary: View changes
Status: Closed (fixed) » Active

Sorry to reopen this: I would like to know if the mentioned documentation has been written at the end?

I'm having the same issue in obtaining translated term names (with entity translation and title module) in views.

I've partially found a solution in this way:

  1. Add relationship "Content: Taxonomy terms on node" in your view
  2. In the relationship configuration step wizard choose one or more vocabularies to use to retrieving taxonomy terms from
  3. In your views fields you can now add (now available thanks to the relationship in previous step) a field "Taxonomy term: Name" (be sure to choose the replacement of the default term name with a field "name_field" provided by title module)

Result: term name is correctly shown translated in views result (YEAH!) but there is a issue: only and only one term is retrieved per node, regardless of you have chosen more than one vocabulary in the relationship configuration.
What is funny is that the only term showed belongs randomly to one or another vocabulary.

I think this is a bug/inconsistency: If I choose more vocabularies in views relationship configuration, then ALL terms of all chosen vocabularies have to be shown in the related field retrieved in views.

I think a momentary workaround could be the following: add as many relationships for each vocabulary, and then add a "term name" field for each relationship/vocabulary.

What do you think about that guys? Should I open a bug issue for this in views issue queue?

ehsankhfr’s picture

ehsankhfr CreditAttribution: ehsankhfr commented

Check the WillHall's comment:

https://www.drupal.org/node/1062748#comment-4096734

pinkonomy’s picture

pinkonomy CreditAttribution: pinkonomy commented

What about if the view has been created using the Search api?There is no such field to add to the view.Can someone help me?
thanks

pinkonomy’s picture

pinkonomy CreditAttribution: pinkonomy commented

Some help please:I have added the taxonomy term name and I tried to rewrite it.However I cannot see the other field from Entity translation to rewrite.What am I missing?thanks