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

[Bug 4850] New: CheckReserves does not respect holds circulation policies
by bugzilla-daemon＠bugs.koha-community.org 26 Jan '16

26 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4850 Summary: CheckReserves does not respect holds circulation policies Change sponsored?: --- Product: Koha Version: rel_3_2 Platform: All OS/Version: All Status: NEW Severity: major Priority: P5 Component: Hold requests AssignedTo: kyle.m.hall(a)gmail.com ReportedBy: ian.walls(a)bywatersolutions.com QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com Estimated Hours: 0.0 Scenario: A title has two items, one of an item type that allows holds, one of a type that does not. The rules defining this are entered into smart-rules.pl, and stored in the branch_item_rules, default_branch_item_rules and default_branch_circ_rules tables in the database. Patron A checks out the item that does not allow holds (Item A). Patron B then places a title-level (next available) hold on that title. Patron B must wait until Item B is available for their hold to be filled, as per our policy. When Patron A looks at their account in the OPAC, they'll see that Item A is on hold, and cannot be renewed. Similarly, when a staff member views their record in the staff client, they will see the item as unrenewal for the same reason (pending hold). When Patron A returns Item A, a message will come up to the staff member checking in that there is a hold on this item for Patron B. This is incorrect, since Item A cannot be held, and Patron B must continue to wait until Item B is available to have their hold filled. The three tables defined above (branch_item_rules, default_branch_item_rules and default_branch_circ_rules) are not consulted anywhere in the codebase except for GetBranchItemRule in C4/Circulation.pm, which in turn is only consulted in opac-reserve.pl and reserve/request.pl. -- 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 10

[Bug 6473] New: Test bug for Git-bz
by bugzilla-daemon＠bugs.koha-community.org 26 Jan '16

26 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6473 Bug #: 6473 Summary: Test bug for Git-bz Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Test Suite AssignedTo: wizzyrea(a)gmail.com ReportedBy: wizzyrea(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Use this bug when testing your git-bz. :) DO YOUR WORST!! (yes, that's a challenge) -- 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 278

[Bug 6420] New: in house use checkouts should check for circ statuses
by bugzilla-daemon＠bugs.koha-community.org 25 Jan '16

25 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6420 Bug #: 6420 Summary: in house use checkouts should check for circ statuses Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Circulation AssignedTo: kyle.m.hall(a)gmail.com ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com When recording in house use it appears that Koha does not check to see if the item is checked out or has a hold. That would be very useful. Regular checkout is aware of the status of the item, why not in house use? -- 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 6934] New: New report Cash Register Statistics
by bugzilla-daemon＠bugs.koha-community.org 25 Jan '16

25 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6934 Bug #: 6934 Summary: New report Cash Register Statistics Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Reports AssignedTo: gmcharlt(a)gmail.com ReportedBy: pelletiermaxime(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Created attachment 5634 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=5634 new report Report that ouputs cash register stats by selecting everything paid in accountlines for a specific period. -- 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 64

[Bug 5161] New: patron attributes clearing if error
by bugzilla-daemon＠bugs.koha-community.org 25 Jan '16

25 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5161 Summary: patron attributes clearing if error Change sponsored?: --- Product: Koha Version: HEAD Platform: All OS/Version: All Status: NEW Severity: major Priority: P5 Component: Patrons AssignedTo: kyle.m.hall(a)gmail.com ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com Estimated Hours: 0.0 When adding a patron record if you enter data in the additional attributes and you get an error about a field not being filled in the additional attributes get emptied out and you have to type them in again. they should stay filled in like the rest of the form. -- 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 4

[Bug 6679] New: Fixing code so it passes basic Perl::Critic tests
by bugzilla-daemon＠bugs.koha-community.org 22 Jan '16

22 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6679 Bug #: 6679 Summary: Fixing code so it passes basic Perl::Critic tests Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Architecture, internals, and plumbing AssignedTo: gmcharlt(a)gmail.com ReportedBy: chris(a)bigballofwax.co.nz QAContact: koha-bugs(a)lists.koha-community.org This bug will be an ongoing one, until all our code passes perl critic tests -- 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 285

[Bug 4941] New: Can't set branch in staff client when singleBranchMode is enabled
by bugzilla-daemon＠bugs.koha-community.org 22 Jan '16

22 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4941 Summary: Can't set branch in staff client when singleBranchMode is enabled Change sponsored?: --- Product: Koha Version: unspecified Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Staff Client AssignedTo: paul.poulain(a)biblibre.com ReportedBy: camins(a)numismatics.org QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com Estimated Hours: 0.0 Although the description of the syspref singleBranchMode implies that singleBranchMode is only relevant to the OPAC, in fact superlibrarians cannot change their branch on the staff client when it is set. Either the description of the syspref should be modified, or the syspref should be split into two, one that only impacts the OPAC, and one that only impacts the staff client. -- 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 29

[Bug 7034] New: De-nesting C4::Branch
by bugzilla-daemon＠bugs.koha-community.org 20 Jan '16

20 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7034 Bug #: 7034 Summary: De-nesting C4::Branch Classification: Unclassified Change sponsored?: --- Product: Koha Version: unspecified Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Architecture, internals, and plumbing AssignedTo: paul.poulain(a)biblibre.com ReportedBy: ian.walls(a)bywatersolutions.com QAContact: koha-bugs(a)lists.koha-community.org Blocks: 6875 Creating a specific bug report for this particular bit of cleanup. -- 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 4

[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