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

[Bug 2578] JS error in z3950 and addbiblio
by bugzilla-daemon＠pippin.metavore.com 29 Dec '08

29 Dec '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2578 ------- Comment #4 from Andrew.moore(a)liblime.com 2008-12-29 11:39 ------- I resubmitted this patch with database revision v3.01.00.010 http://markmail.org/message/kvi7kto3fobho6br Then, I saw that there was a patch already sent in with that number. I updated the wiki to reflect the fact that the previous patch was already sent in. Then, I sent in another with v3.01.00.011 on it. http://markmail.org/message/4neqki2ea6g7jkcq ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2883] longoverdue cronjob misleading and buggy, output mangled
by bugzilla-daemon＠pippin.metavore.com 29 Dec '08

29 Dec '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2883 ------- Comment #1 from joe.atzberger(a)liblime.com 2008-12-29 10:11 ------- Partial fix 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 2887] Cart is not translated
by bugzilla-daemon＠pippin.metavore.com 29 Dec '08

29 Dec '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2887 nahuel.angelinetti(a)biblibre.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Comment #1 from nahuel.angelinetti(a)biblibre.com 2008-12-29 03:35 ------- But, tmpl_process should parse .js files ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2887] New: Cart is not translated
by bugzilla-daemon＠pippin.metavore.com 29 Dec '08

29 Dec '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2887 Summary: Cart is not translated Product: Koha Version: unspecified Platform: PC OS/Version: All Status: NEW Severity: normal Priority: P3 Component: Templates AssignedTo: nahuel.angelinetti(a)biblibre.com ReportedBy: nahuel.angelinetti(a)biblibre.com QAContact: koha-bugs(a)lists.koha.org in Opac "Cart" (right of searchbox) is not translated and isn't in the po files because the string is in javascript and not in tmpl. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2885] New: Adding new branch group w/ existing group code fails silently
by bugzilla-daemon＠pippin.metavore.com 27 Dec '08

27 Dec '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2885 Summary: Adding new branch group w/ existing group code fails silently Product: Koha Version: HEAD Platform: PC URL: http://my.koha.server:8080/cgi- bin/koha/admin/branches.pl OS/Version: Linux - Other Status: NEW Severity: minor Priority: P3 Component: System Administration AssignedTo: paul.poulain(a)free.fr ReportedBy: koha(a)brinkerhoff.org QAContact: koha-bugs(a)lists.koha.org +++ This bug was initially created as a clone of Bug #2884 +++ While trying to add a new Group (http://192.168.1.125:8080/cgi-bin/koha/admin/branches.pl) with an existing Groups code, the UI says "Library category modified" instead of something such as "Please select a unique group code". Steps to repeat: http://my.koha.server:8080/cgi-bin/koha/admin/branches.pl Add group, Name 'Test 1', code 'tst'. Add group, Name 'Test 2', code 'tst'. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2884] New: Adding new branch w/ existing branch code fails silently
by bugzilla-daemon＠pippin.metavore.com 27 Dec '08

27 Dec '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2884 Summary: Adding new branch w/ existing branch code fails silently Product: Koha Version: HEAD Platform: PC URL: http://my.koha.server:8080/cgi- bin/koha/admin/branches.pl OS/Version: Linux - Other Status: NEW Severity: minor Priority: P3 Component: System Administration AssignedTo: paul.poulain(a)free.fr ReportedBy: koha(a)brinkerhoff.org QAContact: koha-bugs(a)lists.koha.org While trying to add a new Branch (http://192.168.1.125:8080/cgi-bin/koha/admin/branches.pl) with an existing Branches code, the UI says "Library saved" instead of something such as "Please select a unique branch code". [Wed Dec 24 07:29:59 2008] [error] [client 192.168.1.139] [Wed Dec 24 07:29:59 2008] branches.pl: Use of uninitialized value in string eq at /home/stan/kohaclone/admin/branches.pl line 90., referer: http://192.168.1.125:8080/cgi-bin/koha/admin/authorised_values.pl Steps to repeat: http://my.koha.server:8080/cgi-bin/koha/admin/branches.pl Add branch, Name 'Test 1', code 'tst'. Add branch, Name 'Test 2', code 'tst'. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2870] Adding a guarantor using 'Add Child' tab is buggy.
by bugzilla-daemon＠pippin.metavore.com 24 Dec '08

24 Dec '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2870 koha(a)brinkerhoff.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |koha(a)brinkerhoff.org ------- Comment #1 from koha(a)brinkerhoff.org 2008-12-24 09:19 ------- I submitted a patch to patches(a)koha.org that fixes this bug (hopefully!) as well as cleans up the script to allow use warnings to operate without spamming the error log. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2046] Suggestions: Title Field too small
by bugzilla-daemon＠pippin.metavore.com 24 Dec '08

24 Dec '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2046 ------- Comment #4 from koha(a)brinkerhoff.org 2008-12-23 17:27 ------- diff --git a/installer/data/mysql/kohastructure.sql b/installer/data/mysql/kohastructure.sql index fe924e6..595def6 100644 --- a/installer/data/mysql/kohastructure.sql +++ b/installer/data/mysql/kohastructure.sql @@ -1915,7 +1915,7 @@ CREATE TABLE `suggestions` ( `STATUS` varchar(10) NOT NULL default '', `note` mediumtext, `author` varchar(80) default NULL, - `title` varchar(80) default NULL, + `title` varchar(255) default NULL, `copyrightdate` smallint(6) default NULL, `publishercode` varchar(255) default NULL, `date` timestamp NOT NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP, This allows for title lengths up to 255 characters. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2169] Paying only partial fines
by bugzilla-daemon＠pippin.metavore.com 23 Dec '08

23 Dec '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2169 adrea(a)moablibrary.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |adrea(a)moablibrary.org ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2883] New: longoverdue cronjob misleading and buggy, output mangled
by bugzilla-daemon＠pippin.metavore.com 23 Dec '08

23 Dec '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2883 Summary: longoverdue cronjob misleading and buggy, output mangled Product: Koha Version: HEAD Platform: PC OS/Version: All Status: NEW Severity: major Priority: P3 Component: System Administration AssignedTo: paul.poulain(a)free.fr ReportedBy: joe.atzberger(a)liblime.com QAContact: koha-bugs(a)lists.koha.org There are many problems with the longoverdue report. First the example on how to run it is wrong: $PERL5LIB/misc/cronjobs/longoverdue.pl --lost 30=2 --lost 60=1 --charge 1 It claims it will set LOST=1 after 30 days, LOST=2 after 60 days, and charge the account when setting LOST=2 (i.e., 60 days). But the second set of --lost options will always be an empty set. It may be hard to tell, because it produces cluttered output like: atz@arwen:~/koha/production/koha$ misc/cronjobs/longoverdue.pl --verbose --lost 30=2 --lost 60=1 starting range: 30 - 366 with lost value 2 at misc/cronjobs/longoverdue.pl line 104. updating 916 for borrower 51 to lost: 2 at misc/cronjobs/longoverdue.pl line 108. updating 1452 for borrower 53 to lost: 2 at misc/cronjobs/longoverdue.pl line 108. updating 900 for borrower 33 to lost: 2 at misc/cronjobs/longoverdue.pl line 108. updating 901 for borrower 33 to lost: 2 at misc/cronjobs/longoverdue.pl line 108. updating 921 for borrower 33 to lost: 2 at misc/cronjobs/longoverdue.pl line 108. updating 888 for borrower 33 to lost: 2 at misc/cronjobs/longoverdue.pl line 108. updating 889 for borrower 34 to lost: 2 at misc/cronjobs/longoverdue.pl line 108. updating 890 for borrower 36 to lost: 2 at misc/cronjobs/longoverdue.pl line 108. updating 2213 for borrower 5 to lost: 2 at misc/cronjobs/longoverdue.pl line 108. updating 238 for borrower 39 to lost: 2 at misc/cronjobs/longoverdue.pl line 108. updating 196 for borrower 747 to lost: 2 at misc/cronjobs/longoverdue.pl line 108. starting range: 60 - 30 with lost value 1 at misc/cronjobs/longoverdue.pl line 104. count : 11 at misc/cronjobs/longoverdue.pl line 124. range : 30 - 366 at misc/cronjobs/longoverdue.pl line 124. lostvalue : 2 at misc/cronjobs/longoverdue.pl line 124. count : 0 at misc/cronjobs/longoverdue.pl line 124. range : 60 - 30 at misc/cronjobs/longoverdue.pl line 124. lostvalue : 1 at misc/cronjobs/longoverdue.pl line 124. ======================================================== The use of warn statements instead of print for regular output is not helpful. Notice, however, the first range is 30-366 and the second range is 60-30. Those values get plugged into the query: SELECT items.itemnumber,borrowernumber FROM issues,items WHERE items.itemnumber=issues.itemnumber AND DATE_SUB(CURDATE(), INTERVAL ? DAY) > date_due AND DATE_SUB(CURDATE(), INTERVAL ? DAY) <= date_due AND itemlost <> ? To clarify: mysql> SELECT DATE_SUB(CURDATE(), INTERVAL 30 DAY) as "30", DATE_SUB(CURDATE(), INTERVAL 366 DAY) as "366", DATE_SUB(CURDATE(), INTERVAL 60 DAY) as "60"; +------------+------------+------------+ | 30 | 366 | 60 | +------------+------------+------------+ | 2008-11-23 | 2007-12-23 | 2008-10-24 | +------------+------------+------------+ 1 row in set (0.00 sec) So what date_due is ever going to match these criteria: 2008-11-23 <= date_due < 2008-10-24 None! ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0