Closed (fixed)
Project:
Search API
Version:
7.x-1.x-dev
Component:
Plugins
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
12 Mar 2014 at 15:37 UTC
Updated:
2 Jul 2014 at 12:50 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
drunken monkeyHave you tried the latest dev release as well? Some highlighting processor issues were fixed since 1.11.
Comment #2
tobiberlinThank you for your reply... no I did not try the latest dev version - I simply deactivated the highlighting processor for my indexes as I do not really need it
Comment #3
bacardi55 commentedHi,
I still have the issue after upgrading to the search_api-7.x-1.x-dev version.
I'm using search_api_elasticsearch, not sure if the issue come from a difference between search_api_elasticsearch and search_api_solr.
In any case, I wrote that patch that fix the issue (at least in my use case).
Please let me know if you have comment/remarks or idea to improve the patch
Comment #4
drunken monkeyThanks for providing a patch!
Might be that the Elastic Search module you're using returns the field values in a weird format – i.e., a multi-dimensional array (instead of, at most, a normal array of strings). Please investigate whether that might not be the issue.
But otherwise, I guess this patch could also make sense. Looks good, thanks!
Comment #5
fabianderijkI've just updated this patch to also fix the
Warning: preg_split() expects parameter 2 to be string, array given in SearchApiHighlight->highlightField()warning.Comment #7
drunken monkeyLooks good, thanks!
Committed.