January 2006 - Koha-bugs - lists.koha-community.org

[Bug 1043] New: Patron Name does not show up Issue to template
by bugzilla-daemon＠wilbur.katipo.co.nz 30 Jan '06

30 Jan '06

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1043 Summary: Patron Name does not show up Issue to template Product: Koha Version: 2.2.0 Platform: PC URL: http://intranet/cgi-bin/koha/circ/circulation.pl OS/Version: Windows 2000 Status: NEW Severity: normal Priority: P2 Component: Circulation AssignedTo: chris(a)katipo.co.nz ReportedBy: pushparvind(a)yahoo.com QAContact: koha-bugs(a)nongnu.org Please note the OS in use is actually Windows XP SP2 I am using the npl template and have 2.2.4 installed. When in the Issue to: text entry field on the left hand side menu I enter a patron name and click submit on the right side the brief information about the patron shows up on the right hand side (main pane) with a text entry field for entering the item barcode to be checked out to that patron. However in the brief information at the top (or anywhere on the screen) the patron name does not show up which is not good. A librarian can be left a little confused sometimes and especially if he/she is interrupted right after entering the patron name (or patron barcode). ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 1042] circulation.pl loses items for display when they don't have itemtypes assigned
by bugzilla-daemon＠wilbur.katipo.co.nz 26 Jan '06

26 Jan '06

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1042 ------- Additional Comments From jmf(a)kados.org 2006-01-27 01:50 ------- Ignore my last comment, I am mistaken about the timestamp. I've been able to resolve all of my problems, but there are still some bugs when an item doesn't have an itemtype or when the timestamp is wrong. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 1042] circulation.pl loses items for display when they don't have itemtypes assigned
by bugzilla-daemon＠wilbur.katipo.co.nz 24 Jan '06

24 Jan '06

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1042 jmf(a)kados.org changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|chris(a)katipo.co.nz |paul.poulain(a)free.fr ------- Additional Comments From jmf(a)kados.org 2006-01-25 11:06 ------- OK ... it's a bit more complicated than I originally thought... it's true that without an itemtype the item isn't displayed, but the problem runs deeper that I thought. I also have a proposed solution that needs to be investigated before implemented. Currently, we have a new sub 'getissues' that seems to be the culprit. It finds the timestamp for the item and then circulation.pl uses that timestamp to determine the date the item was issues. This is problematic for at least one reason: when you're migrating data into Koha you don't have control over the timestamp: you just take what mysql gives you. A better solution is to use the lastreneweddate or some other field that we can control. Does this make sense? Is lastreneweddate updated on first issue? ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 1042] New: circulation.pl loses items for display when they don't have itemtypes assigned
by bugzilla-daemon＠wilbur.katipo.co.nz 24 Jan '06

24 Jan '06

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1042 Summary: circulation.pl loses items for display when they don't have itemtypes assigned Product: Koha Version: CVS Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: Circulation AssignedTo: chris(a)katipo.co.nz ReportedBy: jmf(a)kados.org QAContact: koha-bugs(a)nongnu.org In the display of items a patron has checked out, if one of the items doesn't have an itemtype that item is not displayed. This causes formatting of the page to be wonky as well (for instance, overdue items aren't highlighted, the 'renew' button is missing, etc.). The temporary solution is just to make sure all your items have itemtypes. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 1032] Please Ignore ... Testing New List Again
by bugzilla-daemon＠wilbur.katipo.co.nz 22 Jan '06

22 Jan '06

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1032 jmf(a)kados.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WORKSFORME ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 1041] New: Barcode fail to generate
by bugzilla-daemon＠wilbur.katipo.co.nz 20 Jan '06

20 Jan '06

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1041 Summary: Barcode fail to generate Product: Koha Version: 2.2.0 Platform: Other Status: NEW Severity: normal Priority: P2 Component: Parameters AssignedTo: paul.poulain(a)free.fr ReportedBy: sysadmin(a)handsworth.bham.sch.uk QAContact: koha-bugs(a)nongnu.org When attempting to print barcodes, the following error message is displayed in the koha-error_log file and the program falls over Can't locate object method "barcode" via package "PDF::API2" at /usr/local/koha/intranet/cgi-bin/barcodes/barcodesGenerator.pl line 238., referer: http://koha:8080/cgi-bin/koha/barcodes/barcodes.pl This url www.kohadocs.org/usersguide/ch01s04.html#d0e1528 states that version 0.3r77 of the PDF::API2 modules must be used. This version is not available for download; when we installed the software v1.86 was the only one available and now it is upto v2.00. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 1040] New: Inconsistancy with issuing rules and hints on issuing rules
by bugzilla-daemon＠wilbur.katipo.co.nz 13 Jan '06

13 Jan '06

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1040 Summary: Inconsistancy with issuing rules and hints on issuing rules Product: Koha Version: 2.2.0 Platform: PC Status: NEW Severity: enhancement Priority: P2 Component: Circulation AssignedTo: chris(a)katipo.co.nz ReportedBy: mhafen(a)i.washk12.org QAContact: koha-bugs(a)nongnu.org This relates to bug 1001. /admin/issuingrules.pl using the default template says "Default values If a cell is not filled, the 1st of the following value is searched : " This seems to indicate that the first matching rule will be the only one applied, which is not the case. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 1039] New: bulkmarcimport won't perform table locks
by bugzilla-daemon＠wilbur.katipo.co.nz 07 Jan '06

07 Jan '06

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1039 Summary: bulkmarcimport won't perform table locks Product: Koha Version: 2.2.0 Platform: PC Status: NEW Severity: normal Priority: P2 Component: Database AssignedTo: chris(a)katipo.co.nz ReportedBy: shedges(a)athenscounty.lib.oh.us QAContact: koha-bugs(a)nongnu.org Cindy Murdock said: > I get almost the same thing when running bulkmarcimport: > > DBD::mysql::db do failed: Access denied for user: 'kohaadmin@localhost' > to database 'Koha' at /usr/local/koha/intranet/modules/C4/Biblio.pm line > 333. > DBD::mysql::db do failed: Access denied for user: 'kohaadmin@localhost' > to database 'Koha' at /usr/local/koha/intranet/modules/C4/Biblio.pm line > 382. > > This is with 2.2.4. Well, I have a partial answer to this problem, but am not smart enough to figure it all out. The lines that are throwing the error perform a "lock" on the MySQL tables so bulkmarcimport can have exclusive access while loading the records. Apparently, the username that gets passed from the script to the module does not have lock priviliges. The result is that MySQL throws an error that get's reported (as above), the records get loaded anyway, and if you have exclusive access to the Koha server, there won't be any MySQL conflicts with other users. I'll submit this to kohabugs (possibly related to bug 1002). ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0