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

[Bug 637] New: issuingbranch is NULL in issues and statistics
by bugzilla-daemon＠wilbur.katipo.co.nz 26 Oct '03

26 Oct '03

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=637 Summary: issuingbranch is NULL in issues and statistics Product: Koha Version: CVS Platform: PC Status: NEW Severity: major Priority: P2 Component: Circulation AssignedTo: chris(a)katipo.co.nz ReportedBy: shedges(a)athenscounty.lib.oh.us QAContact: koha-bugs(a)lists.sourceforge.net No value is getting saved in the issuingbranch column in the issues table or the statistics table ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 487] Installer upgrade problems
by bugzilla-daemon＠wilbur.katipo.co.nz 26 Oct '03

26 Oct '03

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=487 mjr(a)ttllp.co.uk changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 487] Installer upgrade problems
by bugzilla-daemon＠wilbur.katipo.co.nz 26 Oct '03

26 Oct '03

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=487 mjr(a)ttllp.co.uk changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|paul.poulain(a)free.fr |mjr(a)ttllp.co.uk ------- Additional Comments From mjr(a)ttllp.co.uk 2003-10-27 01:23 ------- OK, I think there are two things still to do: 1. remove hardcoded paths; 2. use Install.pm routines; I've just realised that the other Install.pm change made a lot of private variables into globals. I'm reverting that, which will break this for now, but I will work on it. Now that I can see what tasks have to be done as part of the upgrade, I can merge them into Install.pm. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 487] Installer upgrade problems
by bugzilla-daemon＠wilbur.katipo.co.nz 26 Oct '03

26 Oct '03

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=487 ------- Additional Comments From mjr(a)ttllp.co.uk 2003-10-27 01:10 ------- I am now making changes for non-root installs. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 589] Too many tags omitted from MARC searches and edits
by bugzilla-daemon＠wilbur.katipo.co.nz 24 Oct '03

24 Oct '03

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=589 ------- Additional Comments From shedges(a)athenscounty.lib.oh.us 2003-10-25 04:44 ------- As worded, yes, this bug has been fixed. A second problem arose, however. As Paul and I discussed, the MARC editor for items would display all information, but would not save changes to all of the subfields (for example, 'homebranch'). Has this been fixed? ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 591] Call to missing acquisitions.pm module
by bugzilla-daemon＠wilbur.katipo.co.nz 24 Oct '03

24 Oct '03

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=591 robweir(a)alum.drexel.edu changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |VERIFIED ------- Additional Comments From robweir(a)alum.drexel.edu 2003-10-24 12:31 ------- Verified as fixed in CVS. Thanks a bunch! Rob ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 631] issues getting posted to the wrong patron when two are added simultaneously
by bugzilla-daemon＠wilbur.katipo.co.nz 23 Oct '03

23 Oct '03

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=631 chris(a)katipo.co.nz changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED ------- Additional Comments From chris(a)katipo.co.nz 2003-10-24 09:35 ------- Have updated insertdata and memberentry.pl, for the fix to work updatedatabase must be run to make the borrowernumber an auto_increment field ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 597] addbiblio.pl does not warn of duplicate barcodes
by bugzilla-daemon＠wilbur.katipo.co.nz 23 Oct '03

23 Oct '03

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=597 ------- Additional Comments From shedges(a)athenscounty.lib.oh.us 2003-10-24 04:47 ------- Yep, we just double-checked: it's fixed. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 631] issues getting posted to the wrong patron when two are added simultaneously
by bugzilla-daemon＠wilbur.katipo.co.nz 22 Oct '03

22 Oct '03

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=631 ------- Additional Comments From chris(a)katipo.co.nz 2003-10-23 10:16 ------- Yep, its a race condition problem, if two ppl are adding a borrower at the same time, its possible for them to be both assigned the same borrowernumber, and the second insert instead ends up updating the first. IE the second borrower essentially overwrites the first. I think the best fix, is to let the database create the borrowernumber by having the borrowernumber column set to unique and auto_increment. And then it will get the next available borrowernumber on insert. Ill work on getting this working ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 476] MARCdetail.pl contains HTML code
by bugzilla-daemon＠wilbur.katipo.co.nz 22 Oct '03

22 Oct '03

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=476 ------- Additional Comments From oleonard(a)athenscounty.lib.oh.us 2003-10-23 10:15 ------- I disagree that this is a template bug: the problem is that the perl script generates HTML, which means that the problem *cannot* be fixed in the template. I also agree that the problem is a tricky one. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0