Closed (fixed)
Project:
Search API
Version:
8.x-1.x-dev
Component:
Plugins
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
14 Sep 2015 at 15:52 UTC
Updated:
9 Oct 2015 at 11:34 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
mkalkbrennerComment #3
mkalkbrennercleaned up the patch
Comment #5
mkalkbrennerComment #6
drunken monkeyThanks a lot!
However, I think overriding
process()would be the proper thing to do here, since that way you'll also catch filter values (in the rare cases of filters on fulltext types).Comment #7
mkalkbrennerAs long as "process" doesn't conflict with "processFieldValue" that exists in this class I'm fine. As I understood the API "process" is for everything. If you want to do separate things for index and search you have to use "processFieldValue" and "processKey".
Comment #9
drunken monkeyYes, more or less correct,
process()is the default implementation forprocessFieldValue(),processKey()andprocessFilterValue(). But when you overrideprocessFieldValue(), that's no longer the case, soprocess()is a good shortcut to override both of the other methods at once.Since it seems to be fine with you otherwise: committed.
Thanks again for your work!