Closed (fixed)
Project:
Search API
Version:
8.x-1.x-dev
Component:
Plugins
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
23 Feb 2017 at 17:10 UTC
Updated:
12 Apr 2017 at 08:20 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
drunken monkeyNo, from what I can see this should be fine. See the documentation for
DatasourceInterface::viewItem(): the$langcodeparameter already defaults to the language the item/entity has been loaded in – which, for us, is of course the item's language.To make sure, I've also written a bit of test code, to ensure this works correctly, and that also came back fine – see the attached patch. We should of course add this, to make sure this keeps working in the future.
If you are certain this doesn't work correctly, please try to write a test that does fail.
Comment #3
ekes commentedI'll see if I can make a test - maybe _yet_ another thing for DDD? But what about when the fields have multiple languages?Stepped through the test, and the indexing logic, and yes it will render as a separate item as best as possible the correct rendering of the fields per language as they exist.
Comment #4
ekes commentedComment #6
drunken monkeyGood to hear, thanks for testing/reviewing!
Committed.
Comment #7
drunken monkey