Posted by miaoulafrite on November 2, 2010 at 8:21am
10 followers
Jump to:
| Project: | Internationalization Views |
| Version: | 6.x-2.x-dev |
| Component: | User interface |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (duplicate) |
Issue Summary
Dear maintainers,
thanks a lot for this marvelous module.
i'm using views 6.x-2.11 with drupal 6.19
i have created some taxonomy vocabularies with option "Per language terms. Different terms will be allowed for each language and they can be translated."
taxonomy terms have then be translated. when creating node where the vocabularies apply, translations are working fine, but in views, it displays both translations in the exposed filters.
is there a way to only show terms in the current user navigation language? how?
thanks for your help
Comments
#1
it also seems that filters "content types" do not show translations if content types names have been translated.
#2
Move to i18n. Drupal-Core/Views does not know of translations for taxonomy terms.
#3
Actually, the terms are properly translated and in other places the translations are displayed accordingly so i thought it was more views-related since the problems appear only in views. or?
#4
Well not everything which is displayed in views is handled by views. It's like assign every issue to drupal because the content X appears in drupal.
#5
It's sometimes definitive quite hard to find the right project.
#6
see also #929368: Terms in exposed filter not translated #337348: Localise views exposed forms and #788290: Fix views compatibility issues (2.x, 3.x), spin off i18nviews module?.
#7
Yes, same kind of problem exists also for common/localizable terms (#929368: Terms in exposed filter not translated, #295315: Views: taxonomy terms shown in dropdown lists of exposed filters are not translated).
#8
Subscribe.
#9
This issue is a little bit confusing because it's repeating along the involved modules:
I am using Drupal 6.22, Internalization 6.x-1.9, Views 6.x-2.12 and Views Internalization 6.x-2.0 and the last International Views patch works for me!
PD: I've noticed that i18ntaxonomy module has this comment "It also translates terms for views filters and views results." so I am not sure about who's the responsible of that issue... I hope next version solves this problem.
#10
Subcribing
#11
#12
Closing as a duplicate of #929368: Terms in exposed filter not translated. If I'm wrong, please re-open.