https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27088
--- Comment #5 from Joonas Kylmälä <[email protected]> --- (In reply to Jonathan Druart from comment #4) > IMO we should keep this behaviour. The query has not a correct syntax and so > it makes more sense to tell the user that there was an error than no results > were found. In that case we should treat this as invalid query and notify the user along the lines "The search cannot be processed because of invalid usage of OR/AND." and don't don't even send the query to Elasticsearch. Now there is unhandled error coming from Elasticsearch which makes it then impossible to spot real system errors. This bug can also be triggered with "something OR". With this "something OR" case it might be more desirable to just search for "something" or then convert OR to lower case and search for "something or" ? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
