February 2014 - Koha-bugs - lists.koha-community.org

[Bug 8491] New: Warning of Modern::Perl raised by koha_perl_deps script
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '14

27 Feb '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8491 Priority: P5 - low Change sponsored?: --- Bug ID: 8491 Assignee: gmcharlt(a)gmail.com Summary: Warning of Modern::Perl raised by koha_perl_deps script Severity: enhancement Classification: Unclassified OS: All Reporter: m.de.rooy(a)rijksmuseum.nl Hardware: All Status: NEW Version: master Component: Command-line Utilities Product: Koha The actual error is (with perl 5.14.2 and Modern::Perl==1.20120130): [Fri Jul 20 16:37:07 2012] koha_perl_deps.pl: Use of uninitialized value $version in numeric lt (<) at /usr/local/share/perl5/Modern/Perl.pm line 25. [Fri Jul 20 16:37:07 2012] koha_perl_deps.pl: Use of uninitialized value $version in numeric lt (<) at /usr/local/share/perl5/Modern/Perl.pm line 25. As Jonathan Druart pointed out in bug 7368, it is caused by the way this module handles version numbers. So it seems like an error in Modern::Perl although its docs state that it is not necessary to pass a version or a year to Modern::Perl. AFAIK we are not passing numbers to Modern::Perl in our Koha use statements. But when I test that in a simple script, I do not even raise this warning. What makes koha_perl_deps do raise that warning? -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 11702] New: Can't specify date for automatic resumption of suspended hold
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '14

27 Feb '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11702 Bug ID: 11702 Summary: Can't specify date for automatic resumption of suspended hold Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: Hold requests Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com If you suspend an individual hold in either the OPAC or staff client and specify a date for automatic resumption the date is not saved correctly. To reproduce in the OPAC: 1. Turn on RequestOnOpac, AutoResumeSuspendedHolds, and SuspendHoldsOpac 2. Log in to the OPAC and place a hold 3. View the list of your existing holds (opac-user.pl) 4. Choose an individual hold to suspend, specify a suspend-until date, and submit 5. When the page reloads the hold will say "Suspended until 02/00/0" To reproduce in the staff client: 1. Turn on AutoResumeSuspendedHolds and SuspendHoldsIntranet 2. Place a hold for a patron, or find an existing hold 3. View the hold details page for that hold (/cgi-bin/koha/reserve/request.pl?biblionumber=XX) 4. Specify a suspend-until date for the hold and submit 5. When the page reloads the hold will say "Unsuspend on" and show no date -- You are receiving this mail because: You are watching all bug changes.

1 8

[Bug 11835] New: Warnings from DBIx about Moo::_Utils and Class::XSAccessor in Koha::Schema
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '14

27 Feb '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11835 Bug ID: 11835 Summary: Warnings from DBIx about Moo::_Utils and Class::XSAccessor in Koha::Schema Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org It started with the following warnings in my staff logfile: member.pl: Class::XSAccessor exists but failed to load with error: Attempt to reload Class/XSAccessor.pm aborted. member.pl: Compilation failed in require at /usr/local/share/perl5/Moo/_Utils.pm line 54. You could try to reproduce them by entering a partial name in the Patron search box on members-home or member. (I entered a name that returned some hits.) Some debugging brought me via Koha/List/Patron and Koha/Database (_new_schema) to Koha::Schema (which goes to DBIx::Class::Schema. Problem somehow is the Koha::Schema->connect call in _new_schema. I do appreciate any feedback whether you have the same error/warning in your log.. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 11863] New: Allow showing author names in consistent format in search results
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '14

27 Feb '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11863 Bug ID: 11863 Summary: Allow showing author names in consistent format in search results Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic data support Assignee: gmcharlt(a)gmail.com Reporter: pasi.kallinen(a)pttk.fi QA Contact: testopia(a)bugs.koha-community.org Using MARC21, the author names come from 100a. The first indicator tells whether the name is in "Lastname, Firstname" or "Firstname Lastname" format. Allow showing the names in eg. search results in consistent format. Perhaps a syspref that has three settings: "Always show Lastname first", "Always show Firstname first", "Always show in format saved in MARC record", the last of which would be default, as that is the current way. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 5439] New: 3M RFID sensitization
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '14

27 Feb '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5439 Summary: 3M RFID sensitization Change sponsored?: Sponsored Product: Koha Version: rel_3_4 Platform: All URL: http://wiki.koha-community.org/wiki/Hook-up_with_3M_se nsitization_solution OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Circulation AssignedTo: henridamien(a)koha-fr.org ReportedBy: paul.poulain(a)biblibre.com QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com Estimated Hours: 0.0 Hook-up with 3M sensitivity solutions so that when you checkout an item in Koha it sends a code (LL) to the 3M system to switch it to Sensitize OFF, and when you checkin an item in Koha it sends a code (RR) to switch the 3M hardware to Sensitize ON. Note : some other sensitivity tools seems underway. Need some clarification ! -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.

1 2

[Bug 1047] Punctuation in site names breaks Edit/Delete z39.50 server administration
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '14

26 Feb '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=1047 --- Comment #6 from Isaac <isaacbrodsky(a)live.com> --- Replacing |url with |uri fixes this issue. I will submit a patch shortly. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 2310] Delete grayed out w/out explanation
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '14

26 Feb '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2310 --- Comment #14 from Fridolin SOMERS <fridolyn.somers(a)biblibre.com> --- (In reply to Galen Charlton from comment #13) > See comment 9. Ok, omnibus. Thanks. -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 2310] Delete grayed out w/out explanation
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '14

26 Feb '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2310 --- Comment #13 from Galen Charlton <gmcharlt(a)gmail.com> --- (In reply to Fridolin SOMERS from comment #12) > Why is this bug assigned again ? See comment 9. -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 2310] Delete grayed out w/out explanation
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '14

26 Feb '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2310 --- Comment #12 from Fridolin SOMERS <fridolyn.somers(a)biblibre.com> --- Why is this bug assigned again ? -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 11853] New: cannot clear date of birth via OPAC patron update
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '14

26 Feb '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11853 Bug ID: 11853 Summary: cannot clear date of birth via OPAC patron update Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: gmcharlt(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org If the date of birth is not mandatory, if a patron tries to submit a modification request that clears their birth date, it shows up in the patron update queue as an entry that changes no fields. Attempt to approve the change does not affect the patron record, and does not remove the modification from the queue. Expected behavior: - that patrons be able to clear the date of birth if it's not mandatory - that the patron modification system be able to recognize and correctly process such an update -- You are receiving this mail because: You are watching all bug changes.

1 0