---- Reported by email@example.com 2010-03-09 10:18:58 ----
In cataloging, when cataloging a biblio.
When looking for an authority, entering data to select on Main Entry AND anywhere would lead to an ERROR 500.
This is owed to the fact that the Z3950 query produced is ill formed.
---- Additional Comments From firstname.lastname@example.org 2010-03-09 10:22:37 ----
Created an attachment
---- Additional Comments From email@example.com 2010-03-10 15:42:21 ----
*** http://bugs.koha.org/cgi-bin/bugzilla3/show_bug.cgi?id=4191 has been marked as a duplicate of this bug. ***
--- Bug imported by firstname.lastname@example.org 2010-05-21 01:25 UTC ---
This bug was previously known as _bug_ 4309 at http://bugs.koha.org/cgi-bin/bugzilla3/show_bug.cgi?id=4309
Imported an attachment (id=2000)
Actual time not defined. Setting to 0.0
Setting qa contact to the default for this product.
This bug either had no qa contact or an invalid one.
The original submitter of attachment 2000 [details] [review] is unknown.
Reassigning to the person who moved it here: email@example.com.
Created attachment 2957 [details] [review]
Earlier patch removed the error as reported in the attachment in bug 4191, but was generating errors when only 1 field searched. With this patch I can search
William and Shakespeare or just Shakespeare without errors.
Plenty of room for refactoring SearchAithorities however. Not sure the authority search options are well enough defined
Tested locally works well, pushed please test
*** Bug 5615 has been marked as a duplicate of this bug. ***
The patch works for UNIMARC DB.
Tested on my instance and it is working.
Since Bug 5615 was closed, I'd like to add one detail that the patch I attached with it also corrected :
In this same authority search window, if the value of "Sort by" is set to "No order", I get an error 500.
This happens because on line 267 of AuthoritiesMarc.pm, a "@or" is added to the query even when $orderstring is empty, which invalidates the query.
Could anyone look into that? I don't know if I should create another bug report for that similar problem.
> Could anyone look into that? I don't know if I should create another bug report
> for that similar problem.
Yes, you should open a separate bug.
This bug is mentioned in:
Bug 4309 Do not throw error on auth search of multiple fields http://lists.koha-community.org/pipermail/koha-patches/2011-January/013539.html
Bug 4309 Do not throw error on auth search of multiple fields http://lists.koha-community.org/pipermail/koha-patches/2011-January/013700.html