Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
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
Comment #1
crowna CreditAttribution: crowna commentedWhen 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)".
Comment #2
webflo CreditAttribution: webflo commentedcrowna is right.
Comment #4
jalves CreditAttribution: jalves commentedI'm not finding the translated option if the field is translated with Field Translation (Entity Translation). When changing to other languages the content disappears...
Comment #5
thejtate CreditAttribution: thejtate commentedI am having the same issue myself.
Comment #6
perkeSame 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
Comment #7
reptilex CreditAttribution: reptilex commentedin #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.
Comment #8
knalstaaf CreditAttribution: knalstaaf commentedThe 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:
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?
Comment #9
mierogul CreditAttribution: mierogul commentedI 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.
Comment #10
mierogul CreditAttribution: mierogul commentedI 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
Comment #11
mierogul CreditAttribution: mierogul commentedComment #12
knalstaaf CreditAttribution: knalstaaf commented#6
Comment #13
sano CreditAttribution: sano commentedI 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.
Comment #14
miguelbraga CreditAttribution: miguelbraga commentedI'm having the same issue, any luck?
Comment #15
sano CreditAttribution: sano commentedI created a module for each exposed filter in my web app and made the strings translatable that way.
Comment #16
sano CreditAttribution: sano commentedmaybe 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.