Closed (duplicate)
Project:
Title
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
20 Apr 2012 at 13:24 UTC
Updated:
6 Feb 2013 at 03:25 UTC
I have a view that includes a taxonomy term reference which I have translated using entity translation. When I show the field in views results, the translated value shows up properly. However, when the value is displayed in an exposed filter, the default language (English) is always shown. Is there a way to show translated values in exposed filters?
Comments
Comment #1
plachThis is a Title-Views integration issue and not an easy one, I fear.
Comment #2
mindaugasd commentedAny plans to make this work in the near future?
Comment #3
mindaugasd commentedFor me things are a bit different. If I change to non-default language nothing shows up in the exposed filter box. I only see filter values if I choose default taxonomy language (non-english).
Comment #4
mindaugasd commentedMaybe I could use t() function to translate filters, but it is not possible than no values are shown at all in other languages.
Comment #5
mindaugasd commentedIf somebody needs a solution, you can install http://drupal.org/project/i18nviews module and add the '... (translated)' Handlers to your view, then filter will be translated.
But it does not work with Title module, still no translated values shows up.
And I still need entity_translation & title modules, becouse I import terms with feeds.
Comment #6
payamspot commentedThanks mindaugasd :) #5 Worked for me.
And for further reference: I chose "Localize. Terms are common for all languages, but their name and description may be localized. " as the "Translation mode" of the vocabulary.
Comment #7
jherencia commentedWell, I've been having this issue and have found a temporary solution for my project that could help:
The problems this has are:
Comment #8
tuwebo commentedHello,
I am not pretty sure but maybe this patch #1651726: Use entity_label instead of term name for term reference exposed filters could help to solve this problem, although could have performance issues.
Comment #9
ptmkenny commentedExcellent! The patch in #8 worked for me! Marking this as a duplicate of #1651726.