Tell me more ×
Drupal Answers is a question and answer site for Drupal developers and administrators. It's 100% free, no registration required.
up vote 1 down vote favorite

I'm using the Views, i18nviews, and Entity Translation modules. All of my terms have already been translated using Entity Translation. In views displays, the translated terms appear in the correct language except in exposed filters. In exposed filters, the terms always appear in the default language for the site.

A search of the issue queues reveals a thread of monstrous length here. So, while support for this is still a work in progress, is there any way (quick and dirty hacks are ok) to get this working today?

share|improve this question

1 Answer

up vote 0 down vote

Editing the View, try to add a new Filter Criteria and look for one you want to translate. There should be a duplicate entry, but the second indicates: (translated). You should use add this (exposed) filter, and delete the other one.

share|improve this answer
Though (translated) filters appear for i18n taxonomy translation, they don't appear for Entity Translation... – Patrick Kenny Apr 22 '12 at 2:24
Well then... After enabling i18n_taxonomy, does this resolves the problem? – hiphip Apr 22 '12 at 14:50
I can't enable i18n_taxonomy. It conflicts with Entity Translation. My question is specifically about Entity Translation. – Patrick Kenny Apr 22 '12 at 14:54
Some versions of i18n have conflicts with Entity but these should be circumstantial (I already had them both enabled with no problem). I would go that way. i18n_taxonomy also has this nice function i18n_taxonomy_localize_terms which is very handy when translating terms in your code. But ok, that's up to you, sorry I couldn't help you. I'll leave my answer anyway, for others info. – hiphip Apr 22 '12 at 21:26

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.