It is said that "no Drupal search solution currently supports the field based translation it [Entity Translation module] is built on", so the new Search API Entity Translation module is needed to make field-based translations searchable.
I have just made an entity-translated site, I'm searching for some words in the second (non-default) language... and somehow it does work even without Search API ET, I do find them.
Am I missing something?
Maybe it makes sense to explain in more detail why do we need to install Search API ET?

Comments

danielnolde’s picture

danielnolde commented
Status: Active » Closed (works as designed)

Hey GN,

in my knowlegde and that of Search API author and maintainer drunken_monkey, Search API itself does _not_ index multiple Entity Translation version of one content (node/entity/whatever), but only the node rendering or field content rendered at indexing time.

Non-standard-language field or node/entity content _can_ _accidentially_ happen to land in the Search API index, in quite some edge cases, e.g.:
* the indexing is done using the second language (e.g. you indexed some nodes via the user interface instead of cron while using that second language as current language)
* the language fallback of ET is configured in a way that leads to the second language as fallback for a missing field content in the language active at indexing time
* field content in the second languiage is accidentially typed into a wrong translation

... and so on, there a lot of cases where that happens, and one can only speculate what's the case in your installation, without inspecting it directly. Anyway, that's not part of what is done here. The sentence in question is correct as i know.