October 2008 - Koha-bugs - lists.koha-community.org

[Bug 2649] minPasswordLength Sys Pref does nothing
by bugzilla-daemon＠pippin.metavore.com 17 Oct '08

17 Oct '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2649 nicole.engard(a)liblime.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED ------- Comment #5 from nicole.engard(a)liblime.com 2008-10-17 06:28 ------- Works! ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2689] Error with empty "Next issue publication date" and cannot edit manually the history
by bugzilla-daemon＠pippin.metavore.com 17 Oct '08

17 Oct '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2689 nahuel.angelinetti(a)biblibre.com changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |major Status|NEW |ASSIGNED Priority|P3 |PATCH-Sent ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2689] Error with empty "Next issue publication date" and cannot edit manually the history
by bugzilla-daemon＠pippin.metavore.com 17 Oct '08

17 Oct '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2689 ------- Comment #1 from nahuel.angelinetti(a)biblibre.com 2008-10-17 06:04 ------- Created an attachment (id=477) --> (http://bugs.koha.org/cgi-bin/bugzilla/attachment.cgi?id=477&action=view) Patch for 3.0.x and HEAD ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2689] New: Error with empty "Next issue publication date" and cannot edit manually the history
by bugzilla-daemon＠pippin.metavore.com 17 Oct '08

17 Oct '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2689 Summary: Error with empty "Next issue publication date" and cannot edit manually the history Product: Koha Version: unspecified Platform: PC OS/Version: All Status: NEW Severity: normal Priority: P3 Component: Serials AssignedTo: nahuel.angelinetti(a)biblibre.com ReportedBy: nahuel.angelinetti(a)biblibre.com QAContact: koha-bugs(a)lists.koha.org When you enter an empty "Next issue publication date", a NULL value is put in the database, so when you want to receive new issues, a "koha error" is expected : Date::Calc::Delta_Days(): not a valid date at /home/nahuel/Workspace/koha/C4/Serials.pm line 1799. And then, if you check the box "Manual history", firstly, when you come back in the form there is no more checked, but the "Subscription history" part is not shown. The bug exists in HEAD and 3.0 ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2688] z3950_search.pl does not reports connection failure
by bugzilla-daemon＠pippin.metavore.com 17 Oct '08

17 Oct '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2688 nahuel.angelinetti(a)biblibre.com changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P3 |PATCH-Sent ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2688] z3950_search.pl does not reports connection failure
by bugzilla-daemon＠pippin.metavore.com 17 Oct '08

17 Oct '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2688 ------- Comment #2 from nahuel.angelinetti(a)biblibre.com 2008-10-17 00:43 ------- Created an attachment (id=476) --> (http://bugs.koha.org/cgi-bin/bugzilla/attachment.cgi?id=476&action=view) Patch for 3.0.x ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2688] z3950_search.pl does not reports connection failure
by bugzilla-daemon＠pippin.metavore.com 17 Oct '08

17 Oct '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2688 nahuel.angelinetti(a)biblibre.com changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #475|Patch for 3.0.x |Patch for HEAD description| | ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2688] z3950_search.pl does not reports connection failure
by bugzilla-daemon＠pippin.metavore.com 17 Oct '08

17 Oct '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2688 ------- Comment #1 from nahuel.angelinetti(a)biblibre.com 2008-10-17 00:42 ------- Created an attachment (id=475) --> (http://bugs.koha.org/cgi-bin/bugzilla/attachment.cgi?id=475&action=view) Patch for 3.0.x ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2688] New: z3950_search.pl does not reports connection failure
by bugzilla-daemon＠pippin.metavore.com 17 Oct '08

17 Oct '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2688 Summary: z3950_search.pl does not reports connection failure Product: Koha Version: unspecified Platform: PC OS/Version: All Status: NEW Severity: normal Priority: P3 Component: Cataloging AssignedTo: nahuel.angelinetti(a)biblibre.com ReportedBy: nahuel.angelinetti(a)biblibre.com QAContact: koha-bugs(a)lists.koha.org When you do a reserch via z39.50, the script does not warn the user it cannot connect to the z39.50 server. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2660] Duplicate overdue notices generated when only one notice is defined.
by bugzilla-daemon＠pippin.metavore.com 17 Oct '08

17 Oct '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2660 ------- Comment #3 from rch(a)liblime.com 2008-10-16 23:11 ------- Submitted new patch allowing either of two behaviors: * default mode : when overdue_notices.pl runs, a notice is generated for each patron with an overdue item in one of the three defined notice periods. Up to three notices may be generated per patron. Example use : conditions: delay1 = 10 days delay2 = 20 days delay3 = 40 days cron script scheduled to run at 10 day intervals results: The patron will receive notice 1 sometime between 10 and 19 days after her item becomes overdue, depending on how the due date aligns with the cron schedule (for purposes of this example, let's assume the due date is off the cron schedule by 3 days, so the first notice is sent 13 days after the due date). The patron receives two copies of notice 2, since the cron script will run twice in the period between delay2 and delay3, at 23 days and 33 days. At 43 days, she receives her first copy of notice 3, and receives another copy every ten days thereafter until MAX (defaults to 90). Proper alignment of cron scheduling with delay settings can generate only one notice per period. The second mode of operation is triggered mode. This option is intended for a system running the cron script nightly, and so only generates a notice on those days when an overdue item reaches one of the delay triggers. This option removes the need to sync cron and delays, but carries a greater risk of missing notices. If the server fails in default mode, you can probably just run the script the next day without missing notices. In triggered mode, if the script fails to run, the notices that would have been generated will never be generated. In this mode, a patron should never receive more than three notices per item. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0