Summary: | Keyword searches surrounded by double quotes fail on staff client and OPAC | ||
---|---|---|---|
Product: | Koha | Reporter: | Barton Chittenden <barton> |
Component: | Searching - Zebra | Assignee: | Galen Charlton <gmcharlt> |
Status: | RESOLVED DUPLICATE | QA Contact: | |
Severity: | normal | ||
Priority: | P5 - low | CC: | jhannert, magnus, nschermann, tomascohen, veron |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
See Also: | https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7518 | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: |
Description
Barton Chittenden
2017-03-17 12:58:03 UTC
Note that this issue is separate from the URL encoding issues in Bug 13301. (In reply to Barton Chittenden from comment #1) > Note that this issue is separate from the URL encoding issues in Bug 13301. Barton, have you tried enabling the QueryParser? I'm more inclined to fix the QueryParser if there are issues with it, and stop spending time on the legacy query parsing code. I had a customer complaining about this exact issue. Setting UseQueryParser = Try solves it. (In reply to Magnus Enger from comment #3) > I had a customer complaining about this exact issue. Setting UseQueryParser > = Try solves it. Not sure if that might cause other issues, though... This bug is a bit strange and still valid. I can not replicate it on my test instance with master and Zebra or on our 18.11 installation. But it still appears broken on Bywater's installation as linked here. I wonder if it's anything to do with configuration and where to start looking. Switching the QueryParser on is NOT a solution, as we just removed the QueryParser from the code. |