Needs review
Project:
Search API Entity Translation
Version:
7.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
13 Sep 2015 at 13:51 UTC
Updated:
11 Jul 2019 at 13:33 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
leksat commentedAttached patch fixes the issue for me.
Comment #3
leksat commentedComment #4
thepanz commentedHi Leksat, do you have an example for that?
I am indexing an entity A, and from a referenced entity B, the B.title_field
I am able to get the correct title_field indexed without your patch.
Is this a 'too simple' to test?
Furthermore: could issue #2335885: 'langcode' option in info array is not applied be related?
Comment #5
thepanz commentedComment #6
fmfpereira commentedHi i'm having the same issue.
On my scenario we are indexing a text field from an entity referenced entity.
We are using entity translation and the entity reference field is not translated (to allow entity translation display based on current language).
In summary this mean that the parent entity language must be used for the referenced entity.
I've rewritten the patch #2 according module codding standard and against last branch dev version.
Comment #7
fmfpereira commentedComment #8
berdirAlso had this problem, additionally, in my case it was multi-value fields, and the list wrapper doesn't have a language() method, so I added an extra check for that. Maybe there would be a better way to do this, don't know the entity wrapper in 7.x very well.