Closed (outdated)
Project:
Search API
Version:
7.x-1.x-dev
Component:
Views integration
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
5 Sep 2012 at 20:50 UTC
Updated:
10 Jan 2019 at 08:26 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
merilainen commentedI did some further debugging by installing vanilla Drupal and minimum required modules, only search_api_et is in dev state. In the listing, the terms always appear in their source language, exposed filters and non-search_api views show everything as I expect.
Bumping up to major to get some attention!
Comment #2
finex commentedI'm experiencing the same problem. It can be reproducible when the vocabulary is configured with the following setting:
Regular views or node display settings allow to use a special formatter "Link (localized)". But search API doesn't make use of it. Moreover this problem affects "Facet API" too.
Comment #3
papirrin commentedI have the same probem. Have you guys found a solution?
Comment #4
merilainen commentedI think the problem is in search_api because it's storing the name of the taxonomy term when it is chosen to be indexed instead of storing term ID (tid) which is more useful and can be used to get the term name in the user's language.
I came up with a quite ugly workaround using Views PHP module and processing the term ID with some php:
Notice that this snippet uses the i18n_taxonomy_term_name() function from i18n module.
So you include the taxonomy term field you need in the view and exclude it from display, then adding a PHP field with the snippet above will print the term in localized form.
Comment #5
legolasboThis issue has not seen activity in over 2,5 years. I am therefore closing this issue to clean up the issue queue. Feel free to re-open and update this issue if you feel this issue is still relevant and of importance.