November 2004 - Koha-bugs - lists.koha-community.org

[Bug 851] circulation patron search fails for valid search
by bugzilla-daemon＠wilbur.katipo.co.nz 26 Nov '04

26 Nov '04

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=851 oleonard(a)athenscounty.lib.oh.us changed: What |Removed |Added ---------------------------------------------------------------------------- Version|CVS |2.2.0 ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 848] moremember.pl no longer outputs item type for issues
by bugzilla-daemon＠wilbur.katipo.co.nz 26 Nov '04

26 Nov '04

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=848 oleonard(a)athenscounty.lib.oh.us changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Additional Comments From oleonard(a)athenscounty.lib.oh.us 2004-11-27 09:08 ------- It looks like there was an extra parameter being passed by moremeber.pl to the subroutine, so changing this: my ($charge,$itemtype)=calc_charges(undef,$dbh,$issue->[$i]{'itemnumber'},$bornum); to this: my ($charge,$itemtype)=calc_charges($dbh,$issue->[$i]{'itemnumber'},$bornum); fixed the problem. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 865] New: Submitting with no barcode in issues should clear for next patron
by bugzilla-daemon＠wilbur.katipo.co.nz 26 Nov '04

26 Nov '04

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=865 Summary: Submitting with no barcode in issues should clear for next patron Product: Koha Version: 2.2.0 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: Circulation AssignedTo: chris(a)katipo.co.nz ReportedBy: oleonard(a)athenscounty.lib.oh.us QAContact: koha-bugs(a)lists.sourceforge.net In previous versions of Koha, if you had been issuing books to a patron and were finished, you could switch to the blank issues screen by hitting enter from the issues form field. Submitting no data would tell the script you were ready to enter the next patron barcode. This allowed librarians to check out to multiple patrons without having to pick up a mouse. This seems to have been removed from circulation.pl or Circ2.pm and should be restored. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 858] Reserve cancellation-on-checkout feature removed
by bugzilla-daemon＠wilbur.katipo.co.nz 26 Nov '04

26 Nov '04

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=858 oleonard(a)athenscounty.lib.oh.us changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | ------- Additional Comments From oleonard(a)athenscounty.lib.oh.us 2004-11-27 05:11 ------- Better, but not quite fixed. Now the message says "I need confirmation before issuing Reserved by 2004-11-26 : Tia Smith Cooper (0055592)" and the button says 'confirm issue.' We used to have buttons saying 'Yes' and 'No,' which was a little more clear (the 'No' button is redundant since librarians can simply go on to the next issue, but it's nice to have the 'No' option for clarity). The real problem is that if you choose to confirm the issue you're not asked if the reserve should be cancelled. This step is necessary because often a husband (for example) will come to the library to check out a reserved item for his spouse. This fulfills the reservation even though the item isn't getting checked out on the account with the reserve. We need the opportunity in these cases to be able to cancel the reserve upon check-out. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 864] Subject search results not limited, show all results
by bugzilla-daemon＠wilbur.katipo.co.nz 26 Nov '04

26 Nov '04

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=864 ------- Additional Comments From oleonard(a)athenscounty.lib.oh.us 2004-11-27 03:40 ------- Should have specified: this concerns NON-MARC searches ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 864] New: Subject search results not limited, show all results
by bugzilla-daemon＠wilbur.katipo.co.nz 26 Nov '04

26 Nov '04

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=864 Summary: Subject search results not limited, show all results Product: Koha Version: 2.2.0 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: Catalogue AssignedTo: chris(a)katipo.co.nz ReportedBy: oleonard(a)athenscounty.lib.oh.us QAContact: koha-bugs(a)lists.sourceforge.net If you do a subject search and click on a subject heading with lots of results, the results page ("/cgi-bin/koha/search.pl?type=intra&subjectitems=Dogs") is not limited to 10 items, as the page says. It shows ALL results (in this example the number for us was 1068). Also: The number links at the top of the page are broken, and Item Count and Location do not show up in the results table. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 863] New: Subject search navigation links are broken
by bugzilla-daemon＠wilbur.katipo.co.nz 26 Nov '04

26 Nov '04

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=863 Summary: Subject search navigation links are broken Product: Koha Version: 2.2.0 Platform: All OS/Version: All Status: NEW Severity: major Priority: P2 Component: Catalogue AssignedTo: chris(a)katipo.co.nz ReportedBy: oleonard(a)athenscounty.lib.oh.us QAContact: koha-bugs(a)lists.sourceforge.net If you do a non-MARC subject search, the first screen to appear is a list of subjects to choose from. On this page are links to 'Previous Records' 'Next Records'. These links are broken--if followed the resulting screen shows 0 results and "you did not specify any search criteria" ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 862] Upgrade does not work (from 2.2RC1 to 2.2RC2) Errors were:
by bugzilla-daemon＠wilbur.katipo.co.nz 23 Nov '04

23 Nov '04

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=862 paul.poulain(a)free.fr changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Additional Comments From paul.poulain(a)free.fr 2004-11-24 01:29 ------- fixed in CVS. Could you test joshua ? ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 862] Upgrade does not work (from 2.2RC1 to 2.2RC2) Errors were:
by bugzilla-daemon＠wilbur.katipo.co.nz 23 Nov '04

23 Nov '04

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=862 paul.poulain(a)free.fr changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|mjr(a)ttllp.co.uk |paul.poulain(a)free.fr OS/Version| |All ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 862] New: Upgrade does not work (from 2.2RC1 to 2.2RC2) Errors were:
by bugzilla-daemon＠wilbur.katipo.co.nz 20 Nov '04

20 Nov '04

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=862 Summary: Upgrade does not work (from 2.2RC1 to 2.2RC2) Errors were: Product: Koha Version: 2.2.0 Platform: PC Status: NEW Severity: normal Priority: P2 Component: Installation AssignedTo: mjr(a)ttllp.co.uk ReportedBy: jferraro(a)athenscounty.lib.oh.us QAContact: koha-bugs(a)lists.sourceforge.net The following upgrade errors occured when I tried to upgrade from 2.2RC1 to 2.2RC2 [root@frodo koha-2.2.0RC2]# ./koha.upgrade Use of uninitialized value in sprintf at Install.pm line 530, <KC> line 12. Use of uninitialized value in sprintf at Install.pm line 530, <KC> line 12. Copying old OPAC interface to /usr/local/koha/opac/cgi-bin200411192000. Copying OPAC interface to /usr/local/koha/opac/cgi-bin. cp: `/usr/local/koha/opac/cgi-bin': specified destination directory does not exist Try `cp --help' for more information. touch: cannot touch `/usr/local/koha/opac/cgi-bin/opac': No such file or directory print() on closed filehandle FILE at Install.pm line 1678. can't chown /usr/local/koha/intranet/scripts/z3950daemon/z3950-daemon-shell.sh: No such file or directory at Install.pm line 1683. can't chown /usr/local/koha/intranet/scripts/z3950daemon/processz3950queue: No such file or directory at Install.pm line 1684. Can't locate C4/Context.pm in @INC (@INC contains: /usr/local/koha/intranet/modules/5.8.3/i386-linux-thread-multi /usr/local/koha/intranet/modules/5.8.3 /usr/local/koha/intranet/modules/i386-linux-thread-multi /usr/local/koha/intranet/modules/5.8.2 /usr/local/koha/intranet/modules/5.8.1 /usr/local/koha/intranet/modules/5.8.0 /usr/local/koha/intranet/modules /usr/lib/perl5/5.8.3/i386-linux-thread-multi /usr/lib/perl5/5.8.3 /usr/lib/perl5/site_perl/5.8.3/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.2/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.1/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.3 /usr/lib/perl5/site_perl/5.8.2 /usr/lib/perl5/site_perl/5.8.1 /usr/lib/perl5/site_perl/5.8.0 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.3/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.2/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.1/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.3 /usr/lib/perl5/vendor_perl/5.8.2 /usr/lib/perl5/vendor_perl/5.8.1 /usr/lib/perl5/vendor_perl/5.8.0 /usr/lib/perl5/vendor_perl .) at scripts/updater/updatedatabase line 22. BEGIN failed--compilation aborted at scripts/updater/updatedatabase line 22. Problem updating database... sent back a prompt at this point. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0