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

[Bug 1101] Renew All for the OPAC
by bugzilla-daemon＠pippin.metavore.com 25 Sep '08

25 Sep '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1101 oleonard(a)myacpl.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED ------- Comment #3 from oleonard(a)myacpl.org 2008-09-25 05:51 ------- Looks like a patch for this has been approved. Seems to be working well. Thanks Jesse! ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2637] New: test & confirm new loan for patrons with overdue items
by bugzilla-daemon＠pippin.metavore.com 25 Sep '08

25 Sep '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2637 Summary: test & confirm new loan for patrons with overdue items Product: Koha Version: rel_3_0 Platform: PC OS/Version: All Status: NEW Severity: normal Priority: P3 Component: Circulation AssignedTo: henridamien(a)koha-fr.org ReportedBy: nicolas.morin(a)biblibre.com QAContact: koha-bugs(a)lists.koha.org When the librarian checks out a book to a patron which already has overdue items, but is not debarred yet, Koha doesn't complain and the librarian doesn't notice that there's something slightly wrong with this praton's account. Koha should test that there are overdue items on this account and, if applicable, output a message: "this patron has overdue items: do you want to proceed with the loan? Y / N" ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2636] New: message on checkin: item x days overdue
by bugzilla-daemon＠pippin.metavore.com 25 Sep '08

25 Sep '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2636 Summary: message on checkin: item x days overdue Product: Koha Version: rel_3_0 Platform: PC OS/Version: All Status: NEW Severity: normal Priority: P3 Component: Circulation AssignedTo: henridamien(a)koha-fr.org ReportedBy: nicolas.morin(a)biblibre.com QAContact: koha-bugs(a)lists.koha.org When the librarian checks in a book that's overdue, Koha does not provide any message (unless the patron already has fines above the max amount allowed, or is debarred). Koha should accept the checkin (as it does today), but check on the due date and, if applicable, output a message: "This item is X days overdue". ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2003] Circulation page offers no information on why checkouts are blocked
by bugzilla-daemon＠pippin.metavore.com 25 Sep '08

25 Sep '08

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

1 0

[Bug 2632] Withdrawn Fines Need Improvements
by bugzilla-daemon＠pippin.metavore.com 24 Sep '08

24 Sep '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2632 ------- Comment #3 from joe.atzberger(a)liblime.com 2008-09-24 12:59 ------- The internal code for "Writeoff" or "W" type is NOT supported by the Koha 3.0 internals precisely because the previous implementation is so problematic. Unfortunately we allowed "W" code to persist in pay.pl where it directly manipulates the database in ways that are unaccounted for and inconsistent with the rest of Koha. For now Writeoff should NOT be used, and it should be removed. Later a similar functionality should be added back in. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2603] updateitem.pl : item statuses can be changed irrespective of Independent branches setting.
by bugzilla-daemon＠pippin.metavore.com 24 Sep '08

24 Sep '08

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

1 0

[Bug 2241] Amazon No image available image isn't translatable
by bugzilla-daemon＠pippin.metavore.com 24 Sep '08

24 Sep '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2241 nicolas.morin(a)biblibre.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nicolas.morin(a)biblibre.com ------- Comment #1 from nicolas.morin(a)biblibre.com 2008-09-24 01:42 ------- but amazon does provide for localized images. See http://g-ecx.images-amazon.com/images/G/08/x-site/icons/no-img-lg._V4569080… for the french-speaking image for "no image available" ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2635] New: Adding non-digit chars to cost fields in items causes data corruption
by bugzilla-daemon＠pippin.metavore.com 23 Sep '08

23 Sep '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2635 Summary: Adding non-digit chars to cost fields in items causes data corruption Product: Koha Version: unspecified Platform: PC URL: cgi-bin/koha/cataloguing/additem.pl OS/Version: All Status: NEW Severity: normal Priority: PATCH-Sent Component: Cataloging AssignedTo: cnighswonger(a)foundations.edu ReportedBy: cnighswonger(a)foundations.edu QAContact: koha-bugs(a)lists.koha.org Adding a non-digit char to either cost field on the add/edit item form causes data corruption due to storing the item cost info in biblioitems.marcxml (longtext) as well as items.cost and items.replacementcost (both integer). Thus if we enter '$10.00' the items fields end up NULL while '$10.00' is stored in the marcxml field. This causes problems when item data is retrieved from the items table rather than the biblioitems.marcxml record. One fix is to check the data submitted for that field for chars other than digits and return an error to the user if such chars exist. I am submitting a patch to do this. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2634] New: details pages cause inefficient items query
by bugzilla-daemon＠pippin.metavore.com 23 Sep '08

23 Sep '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2634 Summary: details pages cause inefficient items query Product: Koha Version: HEAD Platform: PC OS/Version: All Status: NEW Severity: critical Priority: P3 Component: Architecture, internals, and plumbing AssignedTo: galen.charlton(a)liblime.com ReportedBy: rch(a)liblime.com QAContact: koha-bugs(a)lists.koha.org Items::GetItemsInfo is called by details pages on both staff and opac interfaces, generating a query like SELECT * FROM items LEFT JOIN biblioitems. This causes marc and marcxml data to be fetched once per item, and therefore the item's marcxml actually is returned numitems^2 times. In one case, with 320 item records, we get a 92M result set. I'd like GetItemsInfo to not return marcxml or marc columns, but need a code audit to make sure this won't break anything. This bug is related to bug 2453 . Suggest that fix be included in 3.0 maintenance release. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 2444] break up long lines in templates
by bugzilla-daemon＠pippin.metavore.com 23 Sep '08

23 Sep '08

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2444 ------- Comment #4 from rch(a)liblime.com 2008-09-23 11:44 ------- I'd also suggest settling on a length for coding guidelines. shorter lines also make merging and branching simpler with git. Maintaining local modifications to templates is much easier with line breaks. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0