[Koha-bugs] [Bug 2535] New: crashes in OPAC authorities search

[bugzilla-daemon at pippin.metavore.com]

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2535

           Summary: crashes in OPAC authorities search
           Product: Koha
           Version: rel_3_2
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: major
          Priority: P3
         Component: OPAC
        AssignedTo: galen.charlton at liblime.com
        ReportedBy: galen.charlton at liblime.com
         QAContact: koha-bugs at lists.koha.org


It is a bit too easy to make the OPAC authorities search ("browse by subject"
AKA opac-authorities-home.pl) crash.  A crash can be induced in at least two
different ways:

[1] Do any search with the order set to "none".  Associated error in log is:

[Tue Aug 19 09:25:41 2008] [error] [client 68.79.9.21] ZOOM error 20003 "can't
set prefix query" (addinfo: "@or @attr 1=_ALLRECORDS @attr 2=103 ''  ") from
diag-set 'ZOOM', referer:
http://gmc.dev.kohalibrary.com/cgi-bin/koha/opac-authorities-home.pl
[Tue Aug 19 09:25:41 2008] [error] [client 68.79.9.21] Premature end of script
headers: opac-authorities-home.pl, referer:
http://gmc.dev.kohalibrary.com/cgi-bin/koha/opac-authorities-home.pl

[2] Do a search where the search type is "Default" and more than one of the
search boxes is filled in:

[Tue Aug 19 09:26:35 2008] [error] [client 68.79.9.21] ZOOM error 20003 "can't
set prefix query" (addinfo: "@or @attr 7=1 @attr 1=Heading 0  @attr 1=Heading 
@attr 5=1 @attr 4=6 "rere" @attr 1=Any  @attr 5=1 @attr 4=6 "rere"") from
diag-set 'ZOOM', referer:
http://gmc.dev.kohalibrary.com/cgi-bin/koha/opac-authorities-home.pl
[Tue Aug 19 09:26:35 2008] [error] [client 68.79.9.21] Premature end of script
headers: opac-authorities-home.pl, referer:
http://gmc.dev.kohalibrary.com/cgi-bin/koha/opac-authorities-home.pl

These crashes may also affect the staff authorities search.

C4::AuthoritiesMarc::SearchAuthorities() needs to catch all ZOOM exceptions.




------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.