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

[Bug 1657] New: viewlog.pl's date/calendar popup doesn't always work
by bugzilla-daemon＠pippin.metavore.com 17 Dec '07

17 Dec '07

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1657 Summary: viewlog.pl's date/calendar popup doesn't always work Product: Koha Version: HEAD Platform: All OS/Version: All Status: NEW Severity: major Priority: P3 Component: Templates AssignedTo: oleonard(a)myacpl.org ReportedBy: jmf(a)liblime.com QAContact: koha-bugs(a)nongnu.org Start here: /cgi-bin/koha/catalogue/detail.pl?biblionumber=12 or /cgi-bin/koha/circ/circulation.pl?findborrower=23529001223639 Click on 'Modification Log' Then try to enter a date with the calendar popup, when you select one it doesn't fill in the date imput ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 1648] Specifying a due date results in empty date due
by bugzilla-daemon＠pippin.metavore.com 17 Dec '07

17 Dec '07

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1648 chris.cormack(a)liblime.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Priority|P3 |PATCH-Sent Resolution| |FIXED ------- Comment #2 from chris.cormack(a)liblime.com 2007-12-16 17:05 ------- Fixed and 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 1648] Specifying a due date results in empty date due
by bugzilla-daemon＠pippin.metavore.com 16 Dec '07

16 Dec '07

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1648 chris.cormack(a)liblime.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Comment #1 from chris.cormack(a)liblime.com 2007-12-16 14:29 ------- Working on this now ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 1014] moremember.pl should show error message if borrowernumber was not found
by bugzilla-daemon＠pippin.metavore.com 16 Dec '07

16 Dec '07

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1014 chris.cormack(a)liblime.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|chris.cormack(a)liblime.com |joe.atzberger(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 1656] New: Internationalisation of Nomenclature
by bugzilla-daemon＠pippin.metavore.com 16 Dec '07

16 Dec '07

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1656 Summary: Internationalisation of Nomenclature Product: Koha Version: HEAD Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P3 Component: System Administration AssignedTo: paul.poulain(a)free.fr ReportedBy: russel.garlick(a)liblime.com QAContact: koha-bugs(a)nongnu.org Koha 3 has introduced some news names for core functionality in Koha. (e.g Charge In, Charge Out). It would be ideal if there was a feature where a library could change the names used to describe these features: E.g In Circ > Check Out (possible synonyms - Issue,Charge Out) Circ > Check In (Return, Charge In) In any addresses > State (possible synonyms Province, County, Region) There are no doubt many more examples of where a libraries in a given country, or even a specific library, give a feature one name, where other libraries give call it something else. Ideally, these could be then saved as a plugin and then selected from as part of the installation process (e.g I want to load the NZ Public Library Nomenclature Set, as opposed to the US Academic Library Nomenclature set). Then other libraries could possibly contribute their Nomenclature sets to something like contribs.koha for other libraries to use. The comment on this bug that refers to adding "State" to the "City" field description is a good example. http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1631 (sorry Paul I know this gets assigned to you by default :-) ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 1517] C4::Members AddMember and ModMember should pass back failure codes
by bugzilla-daemon＠pippin.metavore.com 16 Dec '07

16 Dec '07

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1517 ------- Comment #2 from mason.james(a)liblime.com 2007-12-15 22:49 ------- (In reply to comment #1) > fyi: modmember() seems busted on my koha > > this simple example code.... > > my $member = GetMember($borrowernumber); > ModMember($member); > > spits this to the errorlog. > > > UPDATE borrowers SET WHERE borrowernumber= at > /home/mtj/koha/production/intranet/modules/C4/Members.pm line 658. > DBD::mysql::st execute failed: You have an error in your SQL syntax; check the > manual that corresponds to your MySQL server version for the right syntax to > use near 'WHERE borrowernumber=' at line 1 at > /home/mtj/koha/production/intranet/modules/C4/Members.pm line 660. > > > anyone else have this problem? > oops, false alarm :) my $member = GetMember($borrowernumber); ModMember(%$member); <<< missed the % ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 1517] C4::Members AddMember and ModMember should pass back failure codes
by bugzilla-daemon＠pippin.metavore.com 16 Dec '07

16 Dec '07

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1517 ------- Comment #1 from mason.james(a)liblime.com 2007-12-15 22:33 ------- fyi: modmember() seems busted on my koha this simple example code.... my $member = GetMember($borrowernumber); ModMember($member); spits this to the errorlog. UPDATE borrowers SET WHERE borrowernumber= at /home/mtj/koha/production/intranet/modules/C4/Members.pm line 658. DBD::mysql::st execute failed: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'WHERE borrowernumber=' at line 1 at /home/mtj/koha/production/intranet/modules/C4/Members.pm line 660. anyone else have this problem? ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 1643] moredetail.pl allows item deletion with no warning and irrespective of independentbranches
by bugzilla-daemon＠pippin.metavore.com 15 Dec '07

15 Dec '07

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1643 ------- Comment #1 from rch(a)liblime.com 2007-12-15 13:25 ------- updated tmpl, removed DELETE option. script level check remains undone, so a properly crafted url would yet allow deletion . ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 1269] Able to delete "SuperLibrarian" Admin with normal Circ Delete Patron command--quick one!
by bugzilla-daemon＠pippin.metavore.com 15 Dec '07

15 Dec '07

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1269 rch(a)liblime.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Comment #4 from rch(a)liblime.com 2007-12-15 11:17 ------- Added 'Staff' category type. The following properties of A Member of type Staff require the permission 'staffaccess' : * change userid/password. * delete borrower. Note that it is up to you to set your staff to correct category type. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 1507] Possible Missing Foreign Key in Accountoffsets
by bugzilla-daemon＠pippin.metavore.com 15 Dec '07

15 Dec '07

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1507 jmf(a)liblime.com changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|PATCH-Sent |P1 ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0