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

[Bug 6837] New: When AllowOnShelfHolds is OFF then holds on records with available items should not be possible
by bugzilla-daemon＠bugs.koha-community.org 19 Jan '16

19 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6837 Bug #: 6837 Summary: When AllowOnShelfHolds is OFF then holds on records with available items should not be possible Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All URL: /cgi-bin/koha/opac-detail.pl?biblionumber=38132 OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Hold requests AssignedTo: ian.walls(a)bywatersolutions.com ReportedBy: axel.jacquin(a)bsz-bw.de QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com Depends on: 2339 Created attachment 5285 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=5285 Screenshot The error occurs in OPAC even though the following parameters are set: AllowOnShelfHolds is OFF OpacItemHolds is OFF RequestOnOPAC is ON When a title has two items, one is checked out, the other is available, then Koha allows the borrower to place a hold, which is then stored in Koha. This should not be possible, because one of the two items is still available on the shelf. -- 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 32

[Bug 6979] New: LDAP authentication fails during password comparison
by bugzilla-daemon＠bugs.koha-community.org 19 Jan '16

19 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6979 Bug #: 6979 Summary: LDAP authentication fails during password comparison Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: Other OS/Version: Linux Status: NEW Severity: major Priority: P5 Component: Architecture, internals, and plumbing AssignedTo: gmcharlt(a)gmail.com ReportedBy: rfox2(a)nd.edu QAContact: koha-bugs(a)lists.koha-community.org Password is failing during comparison in Auth_with_ldap.pm in code (between lines 140 and 165) in this call: my $cmpmesg = $db->compare( $userldapentry, attr=>'userpassword', value => $password ); This was failing 100% of the time, even if a correct password was submitted with: "LDAP Auth rejected : invalid password for user ..." The attribute comparison is not always a valid way to check the password validity because not all LDAP databases support the userpassword attribute. Also, many LDAP databases require a valid DN string from the user as opposed to the uid for authentication purposes. I have a fix for this that does a recursive lookup of the user's DN in the LDAP database, and then uses that DN to perform a bind in a similar manner to the auth_by_bind method. The auth_by_bind method should also be changed so that it uses the retrieved DN of the user to perform a bind against the LDAP server. I plan on submitting a code revision for this and soliciting feedback. -- 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 18

[Bug 9754] New: koha-remove does not remove the stuff in /var/lib/koha/
by bugzilla-daemon＠bugs.koha-community.org 19 Jan '16

19 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9754 Bug ID: 9754 Summary: koha-remove does not remove the stuff in /var/lib/koha/ Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)enger.priv.no CC: robin(a)catalyst.net.nz While testing something else, I have created and removed quite a number of instances on the same server. By chance I discovered that removing instances has not removed the instance-specific direcories below /var/lib/koha/, and the permissions on these directories are completely off: $ ls -l /var/lib/koha/ total 44 drwxr-xr-x 4 test-koha test-koha 4096 2012-11-21 15:59 buskfylk drwxr-xr-x 4 norge-koha norge-koha 4096 2012-12-09 21:14 esme drwxr-xr-x 4 test1-koha test1-koha 4096 2012-11-09 14:15 marc21 drwxr-xr-x 4 1005 1005 4096 2012-12-28 13:00 munka21 drwxr-xr-x 4 norge-koha norge-koha 4096 2013-03-05 17:54 mytest drwxr-xr-x 4 usa-koha usa-koha 4096 2013-03-06 11:12 norge drwxr-xr-x 4 usa-koha usa-koha 4096 2012-12-10 18:47 normarc drwxr-xr-x 4 norge-koha norge-koha 4096 2011-12-03 18:13 sksk drwxr-xr-x 4 test-koha test-koha 4096 2012-12-10 08:36 test drwxr-xr-x 4 test1-koha test1-koha 4096 2013-03-05 17:54 test1 drwxr-xr-x 4 usa-koha usa-koha 4096 2013-03-06 13:17 usa The prmissions for test and test1 are OK, the others are not. I created an instance called "norge", then removed it and created it again. As a result of the situation above I now get a permission error when I try to re-index Zebra for this instance, but I still get hits from the previous incarnation of the instance, presumably because the indexes etc are still there. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 13501] New: Allow autocompletion on drop-down lists
by bugzilla-daemon＠bugs.koha-community.org 19 Jan '16

19 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13501 Bug ID: 13501 Summary: Allow autocompletion on drop-down lists Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Some users have very long lists of authorised values. It could be painful to pick a value in such lists with a simple drop-down list. Following patches will allow to type some text in order to filter these values and pick the good one easily. -- You are receiving this mail because: You are watching all bug changes.

1 36

[Bug 11280] New: Change Withdrawn toggle to drop down selection of authorized values
by bugzilla-daemon＠bugs.koha-community.org 19 Jan '16

19 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11280 Bug ID: 11280 Summary: Change Withdrawn toggle to drop down selection of authorized values Change sponsored?: --- Product: Koha Version: 3.12 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: mcoalwell(a)nekls.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com In Item view moredetail.pl, one is given the choice of selecting authorized values for Lost and Damaged statuses through a drop down. However, Withdrawn is a toggle, even though Withdrawn can be assigned various values in the same way as Lost and Damaged. I am proposing that the Withdrawn status have the same selection menu and "set status" formulation as Lost and Damaged. Statuses ( Lost ) Current location: Checkout status: Current renewals: Lost status: Damaged status: Withdrawn?:No -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 13526] New: Email can be mandatory and hidden in borrower self-registration
by bugzilla-daemon＠bugs.koha-community.org 19 Jan '16

19 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13526 Bug ID: 13526 Summary: Email can be mandatory and hidden in borrower self-registration Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When using the self-registration, "email" is a mandatory field no matter what, if the "PatronSelfRegistrationVerifyByEmail" system preference is true. However, you can still hide the "email" field, which means the form will refuse to submit (saying that you haven't filled in all mandatory fields) even though you've filled out every mandatory field on the screen. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 20

[Bug 12702] New: Suggestions still accessible in OPAC when deactivated
by bugzilla-daemon＠bugs.koha-community.org 19 Jan '16

19 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12702 Bug ID: 12702 Summary: Suggestions still accessible in OPAC when deactivated Change sponsored?: --- Product: Koha Version: master Hardware: All URL: /cgi-bin/koha/opac-suggestions.pl OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org To reproduce: - Turn off suggestion and AnonSuggestions. - Verify there are no longer links visible in navigation and patron account to visit the OPAC suggestion page. - Try to access the page directly: .../cgi-bin/koha/opac-suggestions.pl - Verify that the page is still shown. -- You are receiving this mail because: You are watching all bug changes.

1 26

[Bug 13564] New: Items search: rename Stock number to Inventory number
by bugzilla-daemon＠bugs.koha-community.org 19 Jan '16

19 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13564 Bug ID: 13564 Summary: Items search: rename Stock number to Inventory number Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org In the English UNIMARC and MARC21 frameworks the subfield for items.stocknumber has the description "Inventory number". It would be good to use the same term on the items search form and results table. -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 13683] New: Display library name on holds queue page
by bugzilla-daemon＠bugs.koha-community.org 19 Jan '16

19 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13683 Bug ID: 13683 Summary: Display library name on holds queue page Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org On the holds queue report page if holds are found for a library, it displays: x items found for MPL above the table. Instead of showing 'MPL' it should show the library's name using the TT plugin. -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 9351] New: item type not recorded correctly in statistics for returns and some local use
by bugzilla-daemon＠bugs.koha-community.org 19 Jan '16

19 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9351 Bug ID: 9351 Summary: item type not recorded correctly in statistics for returns and some local use Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: gmcharlt(a)gmail.com CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When returning a loan, or when returning an item for local use when the RecordLocalUseOnReturn syspref is on, the corresponding entry in the statistics table takes the item type from the bib level. This is incorrect when item-level item types is enabled, and among other consequences can lead to problematic local use reports from the circ statistics wizard. In particular, if the library is also doing checkouts to a stats-only borrower to record local use, a circ statistics report on local uses that includes the item type as a row or column can have nonsensical totals because of the NULL statistics.itemtype value. The converse problem affects sites that use biblio-level item types, since local uses recorded from stats-only patrons use the item-level item type regardless of the setting of item-level_itypes. The desired behavior is that when recording a local use, the recorded item type should respect the item-level_itypes system preference. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 83