Needs work
Project:
Search API Pages
Version:
8.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
24 Jan 2020 at 09:34 UTC
Updated:
21 May 2026 at 09:59 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
ash2303 commentedComment #3
ash2303 commentedResolved failing tests.
Comment #4
ash2303 commentedComment #5
ash2303 commentedComment #6
ash2303 commentedComment #7
weseze commentedIs there a reason why the keyword OR is not recognized in any of the parse modes? I would expect that keyword to just work since it is also indicated in the "no-results" text.
Is this an issue with search_api or search_api_page?
Comment #8
ash2303 commentedThe issue is related to
search_api_pageassearch_apialready has support. Just that there is no option insearch_api_pageform to add OR support with Parse Mode.Comment #9
ash2303 commentedCorrect config export miss.
Comment #11
crtlf commentedThanks a lot, @ash2303 !
I'm a bit surprised that this issue hasn't been tested in four years, as it seems like a pretty common feature.
I can confirm that the patch is still working on 8.x-1.38
Comment #12
anybody#11 sounds like RTBC. Still I think it would make sense to turn this into a MR.
It also adds a new test, so this is great! Would someone like to finish this?