March 2014 - 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 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 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

[Bug 10177] New: Koha Accepts Seven "Space" Characters as a Valid Password
by bugzilla-daemon＠bugs.koha-community.org 19 Jan '16

19 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10177 Bug ID: 10177 Summary: Koha Accepts Seven "Space" Characters as a Valid Password Classification: Unclassified Change sponsored?: --- Product: Koha Version: 3.10 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: gmcharlt(a)gmail.com Reporter: glawson(a)rhcl.org CC: dpavlin(a)rot13.org Koha 3.10.03 and presumably earlier versions accept seven "space" characters as a valid password. Concerns: 1. Some third party software using SIP to check the Koha database to authenticate users may interpret all blank characters, or even a single terminal blank character, as an invalid password. 2. gmcharlt suggests that patches submitted in the future may strip trailing whitespace characters in form input, causing pernicious perturbations. -- You are receiving this mail because: You are watching all bug changes.

1 36

[Bug 10943] New: impossible to check and make fines when borrowers flag is desactivate
by bugzilla-daemon＠bugs.koha-community.org 19 Jan '16

19 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10943 Bug ID: 10943 Summary: impossible to check and make fines when borrowers flag is desactivate Change sponsored?: --- Product: Koha Version: 3.12 Hardware: PC OS: Windows Status: NEW Severity: normal Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: marjorie.barry-vila(a)ccsr.qc.ca QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com When a borrower has those flags: -circulate -catalog -reserveforothers -borrow -updatecharges He can not make and check fines on a other borrower. He can make check in and check out but he has not a access to the fines tab. See video. http://communaute.koha.ccsr.qc.ca/wp-content/uploads/2013/09/flags.swf Thanks Marjorie -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 10887] New: Batch item deletion -- doesn't need Use default values section
by bugzilla-daemon＠bugs.koha-community.org 19 Jan '16

19 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10887 Bug ID: 10887 Summary: Batch item deletion -- doesn't need Use default values section Change sponsored?: --- Product: Koha Version: 3.12 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: gmcharlt(a)gmail.com Reporter: hbraum(a)nekls.org QA Contact: testopia(a)bugs.koha-community.org The batch item deletion tool doesn't need to have the option for "use default values section" to "Populate fields with default values from default framework." The option is applicable to the batch item modification tool, but not to batch item deletion -- because all the user is doing with the batch deletion is deleting items. Should this option be removed, as a result? -- You are receiving this mail because: You are watching all bug changes.

1 16

[Bug 10241] New: Easy analyticals creates two 773 fields. Search/link from host to children is broken
by bugzilla-daemon＠bugs.koha-community.org 19 Jan '16

19 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10241 Bug ID: 10241 Summary: Easy analyticals creates two 773 fields. Search/link from host to children is broken Classification: Unclassified Change sponsored?: --- Product: Koha Version: 3.10 Hardware: All OS: All Status: NEW Severity: normal Priority: P4 Component: MARC Bibliographic data support Assignee: gmcharlt(a)gmail.com Reporter: eb(a)efdss.org UseControlNumber preference is set to "Don't use" and the EasyAnalyticalRecords preference is set to 'Display.' I created a record, and then selected New child record and created an analytic. Then, following the instructions in the manual Chapter 5 http://es.koha-community.org/manual/3.10/en/cataloging.html#cataloganalytics I linked the analytic to the host item. This resulted in two 773 fields. The first (created when adding a new child record contains: w Host Record control number 005037189 d Place, publisher, and date of publication Milwaukee : Hal Leonard, [2002?] z International Standard Book Number 0634038788 t Title Selections from O brother, where art thou? : The second 773, created when I linked the child to the parent contains the above, plus 0 Host Biblionumber 19017 9 Host Itemnumber 20551 The search for analytics is driven by the host item number, which is not included in the 773 that is created with a new child record. So you must link the child to the parent. But why create an additional 773? It looks messy. Second part possibly not related at all to the above: When I go to the host item in the staff interface and click on Analytics it says Used in 4 analytics ('4 analytics' is a link: http://kohaadmin-test.efdss.org/cgi-bin/koha/catalogue/search.pl?idx=hi&q=2… If I click on the link: No results found. No results match your search for 'hi,wrdl: 20551' in VWML Test Catalog. But if I put the host item number 20551 into the search field, it returns the children and the parent record. Something about the search from analytics is not functioning correctly. -- You are receiving this mail because: You are watching all bug changes.

1 27

[Bug 7497] New: "kw, wrdl" and variants should be replaced by something more explicit in search history
by bugzilla-daemon＠bugs.koha-community.org 18 Jan '16

18 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7497 Bug #: 7497 Summary: "kw,wrdl" and variants should be replaced by something more explicit in search history Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching AssignedTo: gmcharlt(a)gmail.com ReportedBy: gaetan.boisson(a)biblibre.com QAContact: koha.sekjal(a)gmail.com A patron search history typically reads like this : Date Search Results 03/02/2012 15:49:18 au,wrdl: test2 0 03/02/2012 15:49:04 se,wrdl: test 0 03/02/2012 15:48:51 nb: test 0 03/02/2012 15:47:09 kw,wrdl: tsfdfs 0 03/02/2012 15:47:01 kw,wrdl: tsfdfs 0 A more explicit list would be a nice improvement : au,wrdl : author se,wrdl : series nb : isbn kw,wrdl : (all) ti,wrdl : title su,wrdl : subject callnum,wrdl : callnumber Am i missing any ? -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 13