For a specific vocabulary, I chooze "Localize terms. Terms are common for all languages, but their name and description may be localized".
I translated terms via /admin/build/translate, and refresh.
I added module Views translation (I did not install it first). Empy view cache and drupal cache. Then update my view (change nothing) but to be sure new module will be considered (I have a filter to get language of user, so depending of switcher).
I have a field in my view which is the term. This field in not translated. When I switch between 2 langages, I always have my term in default language.
Other strings/variables are OK.
Default language is French.
I added German.
With, this method "Localize terms", the wiew should show the term in the required language, is not it?
Is it a bug?
Comment | File | Size | Author |
---|---|---|---|
#5 | view.txt | 24.44 KB | vthirteen |
#4 | views-export.txt | 23.93 KB | Danny_Joris |
Comments
Comment #1
sahuni CreditAttribution: sahuni commentedWhy no reply ?
If it's a bug, does someone is looking for a solution for D6?
Does maintener forget to check that issue list since splitting from i18n?
Comment #2
Danny_Joris CreditAttribution: Danny_Joris commentedI have the same issue I think. I have trouble finding answers for this as well...
In full nodes the terms get translated as they should, but when they occur in a views display, it only shows in the original language. For example in node teasers listed by views, or when I use views Arguments to group content by taxonomy term (in summary style).
I have this issue with Internationalization Views enabled and without. Adding this module didn't change anything.
No luck with 2.x-dev either.
Comment #3
dboulet CreditAttribution: dboulet commentedSome ideas of things to try:
-Update your code to the latest versions of Drupal, i18n, and i18nviews (make sure to delete the i18n folder before updating it, to clear out all the old code).
-clear your cache
-try attaching an export of your view here, to make it easier for us to find the problem
Comment #4
Danny_Joris CreditAttribution: Danny_Joris commentedHello dboulet,
Thanks for your feedback. I upgraded Drupal from 6.17 to 6.19 and i18n from 6.15 to 6.17. i18nviews is still the latest 2.x-dev version. Cleared cache, but no results. All remained the same
In attachment is my view export.
Comment #5
vthirteen CreditAttribution: vthirteen commentedexactly same situation here
Comment #6
Danny_Joris CreditAttribution: Danny_Joris commentedI avoided this issue by changing the translation mode of my taxonomy terms to 'Per language terms' instead of 'Localize terms'. It works much better + it's easier for administrators to manage.
Fact is that it doesn't solve the original issue of course.
Comment #7
vthirteen CreditAttribution: vthirteen commented...and it's not really an option in many cases because you should change node terms, views etc.
Comment #8
Gabriel R. CreditAttribution: Gabriel R. commentedThis "seems" to have been fixed, according to #346028: Translate taxonomy term names in Views #3151612 but I can't get it to run.
Comment #9
joachim CreditAttribution: joachim commentedConfirming this is still an issue.
I have latest Drupal core, Views, and i18n modules.
A view showing nodes and term fields correctly has the field labels translated, but not the terms; whereas if I look at the node, the terms are shown translated.
Comment #10
joachim CreditAttribution: joachim commentedIs #346028: Translate taxonomy term names in Views a duplicate?
Comment #11
skolesnyk CreditAttribution: skolesnyk commentedApparently to get this working, you have to:
1. enable translation on images (make sure all fields are cheked on for synchronization -- most important is terms sync)
2. On image galleries vocabulary settings select Per language terms.
3. create respective translations and then bulk update node terms on translated nodes to translated name of your gallery.
It should sync translation names from original taxonomy term to translated one.
Using latest stable Image module and stable Viewsi18n
Wickedly complicated.
Comment #12
sanderc CreditAttribution: sanderc commentedStill, this remains a bug i would like to see fixed. I ran into the same thing.
Comment #13
lhristov CreditAttribution: lhristov commentedIs this the same issue that makes the view with a taxonomy filter to not display the translated version?
I forced translation of terms on the view itself by forcing them through t() with a custom php filter but I can't do the same for taxonomy filter. I really need the filters translated. Any suggestions>
Comment #14
miaoulafrite CreditAttribution: miaoulafrite commented+1
Comment #15
mandreato CreditAttribution: mandreato commentedSomething similar here.
I've a taxonomy vocabulary where terms are on two levels:
- Term A
- Term A.1
- Term A.2
...
- Term B
- Term B.1
- Term B.2
...
All terms are translated via Translation table into 5 languages.
A view (6.x-2.11) lists those terms grouped by parents (i.e. they appear listed as above) and the 2nd level terms (i.e. Term X.1) are shown as links: the parent term on relationship is used as a hidden field just to permits grouping. The view is then attached to a panel via Content pane.
When I switch to a language different from default, only terms on second level are translated, whilst Term A, Term B... remains in the default lang).
I use the last Views translation module version: 6.x-2.x-dev.
Comment #16
chuckbar77 CreditAttribution: chuckbar77 commentedSubscribing
Taxonomy terms are also only showing as original language on my site when outputting via views.
Comment #17
eiland CreditAttribution: eiland commentedFor what its worth, I use the following code to translate the title and the breadcrumb of the replacing taxonomy view.
I am not using language negotiation, so I need the global $language.
under "Arguments -> Taxonomy: Term ID (with depth)" I use the PHP validator
(without php tags)
and the "Basic settings -> header" of the view is:
(with php tags and the php filter)
I haven't tested it more then 1 level deep, assume it needs some recursion.
Comment #18
miro_dietikerThis seems duplicate to me for
#947468: Translate Taxonomy Term Argument
(referred issue provides patch, although it was created later...)
Comment #19
martin.l CreditAttribution: martin.l commentedSubscribing.