With Search API Entity Translation we can have different index for each language for an entity.
For example if we had 1 element for node 1 in SOLR, with this module will be multiply by the languages enabled on the site, or with the full entity translation of a node or with partial. So instead of item_id:"1" and 1 index we will get something like:
index 1 -> item_id:"en_1"
index 2 -> item_id:"de_1"
index 3 -> item_id:"fr_1"
So far no problem, but if want to index the View Mode with the "Complete entity view" the SearchApiAlterAddViewedEntity->alterItems
does not offer support for multilingual content.
So i made a patch to fix this issue.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | 2592231-3--viewed_entity_language.patch | 772 bytes | drunken monkey |
| #2 | 2592231-1--search-API-Entity-Translation-incompatibility.patch | 761 bytes | balintcsaba |
Comments
Comment #2
balintcsaba commentedComment #3
drunken monkeyYou're right, the language is missing there. Thanks for reporting!
However, your patch would lead to warnings for entities which don't have a
languageproperty. The proper fix, I think, is to use our ownsearch_api_languageproperty, which will always be there. I'm just not sure whether we should also passLANGUAGE_NONE, if that's set there – but I guess this will even have the hidden "feature" that it will make the process more predictable. (Now, indexing in different contexts might lead to different results in the search index, which should of course be avoided where possible.)Please test whether the attached patch still fixes the problem for you!
Comment #4
balintcsaba commentedTested, works
Comment #5
drunken monkeyGreat to hear, thanks for testing!
Committed.