---- Reported by nahuel.angelinetti@biblibre.com 2008-10-17 00:37:04 ---- When you do a reserch via z39.50, the script does not warn the user it cannot connect to the z39.50 server. ---- Additional Comments From nahuel.angelinetti@biblibre.com 2008-10-17 00:42:32 ---- Created an attachment Patch for 3.0.x ---- Additional Comments From nahuel.angelinetti@biblibre.com 2008-10-17 00:43:23 ---- Created an attachment Patch for 3.0.x ---- Additional Comments From gmcharlt@gmail.com 2008-10-21 08:29:53 ---- Patch applied. However, it could use improvement; if one searches two Z39.50 servers, one of which fails and the other one works, the user is not informed about the failure. ---- Additional Comments From nahuel.angelinetti@biblibre.com 2009-10-07 12:31:12 ---- I didn't find this patch on HEAD, it wasn't applied. --- Bug imported by chris@bigballofwax.co.nz 2010-05-21 00:54 UTC --- This bug was previously known as _bug_ 2688 at http://bugs.koha.org/cgi-bin/bugzilla3/show_bug.cgi?id=2688 Imported an attachment (id=792) Imported an attachment (id=793) Actual time not defined. Setting to 0.0 The original submitter of attachment 792 [details] [review] is unknown. Reassigning to the person who moved it here: chris@bigballofwax.co.nz. The original submitter of attachment 793 [details] [review] is unknown. Reassigning to the person who moved it here: chris@bigballofwax.co.nz.
This patch has been applied to HEAD--I see the changes in the current code and single failure or multiple failures are reported correctly. Galen is correct that if one of your searches is successful the interface will report no errors. I'm re-wording the bug so that this specific issue can still be addressed.
Is this bug still valid? I tried a search with two invalid servers and a valid one. The results reported: Connection failed to fjköfasjfjksa Connection failed to sfdfsdfsd ...plus the results from the valid server.
I confirm, current versions of Koha report if one or more connections have failed.