Hey Thomas,

are there any plans or thoughts about support for translated field in search_api?
When using http://drupal.org/project/entity_translation there's only one entity/node containing several translation via translated fields, as opposed to multiple nodes for each language in the traditional i18n/content translation solution.

As of now, there is no possiblity to cleanly implement a language-aware search for content with translated fields. Hm.
Adding support in search_api for entity translation / translated fields would make great sense - given the usfulness of entity translations and the statements hinting that translation in D8 could be based on translated fields instead of multiple nodes in translations sets.

We're working an a project in need for such a solution, so we are willing to help and support this in any way.
What would be necessary to get this working (changes, work, prerequisites)?
What are your thoughts about this?

cheers,

daniel

Comments

drunken monkey’s picture

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

I think the right link is #1323168: Add support for translated fields :)

danielnolde’s picture

Hey guys!

Finally we have a dedicated place to get support for entity translations into Search API:

The "Search API Entity Translation" module already offers very basic support to search through all entity translations of an entity via Search API:

http://drupal.org/project/search_api_et

This is a really handy quick win for all those in desperate need of somehow searching though multilingual content managed via Entity Translation.
More important: There is an issue to discuss and decide on how to support a more delicate and truely language-aware searchability for Entity Translation in Search API:

http://drupal.org/node/1393058

You're all invited to participate in this discussion!