Situation:
- All the fields with their values in a particular content type have been translated.
- The translations show on the node view page for this content type when the language is switched.
- However, when using a view with exposed filters (using these fields/values), the translations do not show in the exposed filter form. Only the original English is visible.
Can anyone assist please?
Thanks

Comments

crowna’s picture

When selecting a field for your exposed filter use the translated field. This will appear something like "Category (field_kat) (translated)" instead of "Category (field_kat)".

webflo’s picture

Status: Active » Fixed

crowna is right.

Status: Fixed » Closed (fixed)

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

jalves’s picture

Status: Closed (fixed) » Active

I'm not finding the translated option if the field is translated with Field Translation (Entity Translation). When changing to other languages the content disappears...

thejtate’s picture

I am having the same issue myself.

perke’s picture

Same here, using content type as exposed filter there is no way to have labels translated even though content type name is translated with field translation from i18n

edit: For content type labels in exposed filters, there is a patch at #1687752: Node type name not translated in exposed filter

reptilex’s picture

in #1 crowna is right. But you have to install the i18nviews module for it to work. After that it works like a charm. It is still dev but I had no problems so far.

knalstaaf’s picture

Issue summary: View changes

The labels on exposed filters can be translated with the i18n-Views UI, but I have over 50 blocks with the very same label. One translated string should suffice, no, as is the case with the regular translation interface UI?

I looked it up in the translation interface UI and for every single block there's a separate string, eventhough the string itself is the same everywhere:

Hoogte
views:productoverzichten:block_49:filter:field_data_field_hoogte_cm_:field_hoogte_cm__tid:expose:label	
Hoogte
views:productoverzichten:block_50:filter:field_data_field_hoogte_cm_:field_hoogte_cm__tid:expose:label

Do I have to do the tedious job of translating the same strings for 50 times (x4 labels) now? Or am I overlooking a better option?

mierogul’s picture

I made the site in 5 languages. I translated taxonomies and where I see I translate. BEF but still showing in English. I translated views with "i18nviews". My first website in drupal. I'm looking for a simple solution.

mierogul’s picture

I made the site in 5 languages. I translated taxonomies and where I see I translate. BEF but still showing in English. I translated views with "i18nviews". My first website in drupal. I'm looking for a simple solution. Site: www.istanbulproperty.agency

mierogul’s picture

Status: Active » Closed (duplicate)
knalstaaf’s picture

sano’s picture

Status: Closed (duplicate) » Active

I have followed the advice #1 and have the i18nviews module installed and enabled, but am still unable to translate the items in the exposed filter widgets.

miguelbraga’s picture

I'm having the same issue, any luck?

sano’s picture

I created a module for each exposed filter in my web app and made the strings translatable that way.

sano’s picture

maybe it was an update to i18n or some other module, but I just found out that the first post in this issue (made by crowna) correctly instructs how to make sure the exposed filters show translated. No need for custom modules as I mentioned in my previous post.