Closed (fixed)
Project:
Search API
Version:
7.x-1.x-dev
Component:
Views integration
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
23 Aug 2017 at 22:17 UTC
Updated:
20 Sep 2017 at 15:15 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
pobster commentedComment #3
pobster commentedComment #4
drunken monkeyThanks a lot for reporting this issue and providing a patch!
I don't know that module, but your patch looks simple enough (and also pretty good), and if you say it works, that's good enough for me. It should, in any case, not affect anyone not using that module.
However, to be consistent with the other two "special" values, could we use
'fallback'for the option key?Also, the global is already imported at the start of the
query()method, no need to do it again.Please tell me if the attached patch still works for you and I will commit it.
PS: It seems you (like many others – it's really easy to misinterpret) are confused by the "Issue tags" field. As the guidelines state, they aren't meant for free text tags related to the issue, but only for specific categorization purposes, usually by module maintainers.
So, if you aren't sure your current usage is correct, please just leave the field empty.
Comment #5
pobtastic commentedYeah thank you, LGTM +1 :o)
Comment #7
drunken monkeyWhy the two accounts?
Anyways, thanks for reporting back, and good to hear it still works for you.
Committed.
Thanks again!