November 2022 - Koha-bugs - lists.koha-community.org

[Bug 25508] New: Confusing renewal message when paying accruing fine
by bugzilla-daemon＠bugs.koha-community.org 02 Feb '23

02 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25508 Bug ID: 25508 Summary: Confusing renewal message when paying accruing fine Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To recreate: 1 - Make sure FinesMode is on, RenewAccruingItemWhenPaid is off 2 - Checkout an item to a patron and make it overdue (can backdate the checkout) 3 - Make sure the itemtype has fines that will be charged 4 - Charge the fines: Set finesMode = production perl misc/cronjobs/fines.pl -v 5 - Check the fine appears on the patrons account 6 - Pay off the fine 7 - Receive alert after payment that reads: "The fines on the following items were paid off, renewal results are displayed below: No title ( ): Not renewed - Unknown error" Looks like we're not properly hiding that alert when RenewAccruingItemWhenPaid is off? So it's reporting that nothing was renewed? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 46

[Bug 23380] New: GuessAuthTypeCode should check authority type exists
by bugzilla-daemon＠bugs.koha-community.org 02 Feb '23

02 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23380 Bug ID: 23380 Summary: GuessAuthTypeCode should check authority type exists Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl The method GuessAuthTypeCode is used when importing from batch or z3950/SRU to find the local authority type depending on MARC flavour and authority record fields. This method should check that found type is configured. Otherwise it can generate software errors when type code is used to fetch Koha::Authority::Type. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 20632] New: Staff users without superlibrarian can't log into OPAC
by bugzilla-daemon＠bugs.koha-community.org 02 Feb '23

02 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20632 Bug ID: 20632 Summary: Staff users without superlibrarian can't log into OPAC Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org Ok, I hope it's not me, but in case it isn't, this is a bad bug: - Create or change your staff user to have all available permissions BUT superlibrarian - Log out - Log into staff - it works. Log out. - Log into OPAC - it won't work. Not good at all. This is bad for at least 2 reasons: - Often staff accounts are used like normal patron accounts by staff. - Because of permissions, sometimes the OPAC is the only place a staff user can change their password. Tested on master after a reset_all. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 22842] New: Add an option to prevent local logins on the staff or opac
by bugzilla-daemon＠bugs.koha-community.org 01 Feb '23

01 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22842 Bug ID: 22842 Summary: Add an option to prevent local logins on the staff or opac Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org Target Milestone: --- When using SSO in various forms it would be nice to have the option of forcing patrons to use the external auth and removing the ability to sign in to koha directly. It would be nice to have separate switches for the staff client and OPAC so that staff could be allowed to access directly while patrons are directed to SSO -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 18506] New: Shibboleth SSO Only Mode
by bugzilla-daemon＠bugs.koha-community.org 01 Feb '23

01 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18506 Bug ID: 18506 Summary: Shibboleth SSO Only Mode Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: gmcharlt(a)gmail.com Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org Shibboleth works at it's best when it is the ONLY form of authentication allowed on the system. That way, if you disable opacPublic you can have a system that automatically redirects the user to the IdP for authentication immediately and skips any other forms of authentication leading to a more seamless SSO solution. -- You are receiving this mail because: You are watching all bug changes.

1 79

[Bug 32204] New: in-page anchor to edititem on additem.pl not working
by bugzilla-daemon＠bugs.koha-community.org 01 Feb '23

01 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32204 Bug ID: 32204 Summary: in-page anchor to edititem on additem.pl not working Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl To recreate: 1. Search the catalog and view a record detail page of a record with items 2. Click 'Edit items' 3. Choose one item from the list and click 'Edit' 4. The URL fragment or in-page anchor (#edititem) is appended to the end of the URL but you are not placed on it. Instead you are placed at the top of the page and must scroll down to edit the particular item. Note: This issue is present in master and 22.05.x, as far as I can tell. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21

[Bug 32229] New: Typo: Items missing from bundle at checking for %s
by bugzilla-daemon＠bugs.koha-community.org 01 Feb '23

01 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32229 Bug ID: 32229 Summary: Typo: Items missing from bundle at checking for %s Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Keywords: Academy Severity: trivial 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 CC: martin.renvoize(a)ptfs-europe.com Should this have been checkin? Items missing from bundle at checking for %s koha-tmpl/intranet-tmpl/prog/en/modules/circ/returns.tt:1336 -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 32376] New: selenium/authentication_2fa.t produces artefact
by bugzilla-daemon＠bugs.koha-community.org 01 Feb '23

01 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32376 Bug ID: 32376 Summary: selenium/authentication_2fa.t produces artefact Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 30588 There is a selenium_failure_2.png screenshot that is created, even if the tests succeed. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30588 [Bug 30588] Add the option to require 2FA setup on first staff login -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 25032] New: Generic unhandled exception handling
by bugzilla-daemon＠bugs.koha-community.org 01 Feb '23

01 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25032 Bug ID: 25032 Summary: Generic unhandled exception handling Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com The idea is to clean things in the controllers and provide a reliable way to control the logging of unhandled exceptions for debugging. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 59

[Bug 29595] New: missing Content-Type / HTTP 415 check for POST requests to /api/v1/patrons
by bugzilla-daemon＠bugs.koha-community.org 01 Feb '23

01 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29595 Bug ID: 29595 Summary: missing Content-Type / HTTP 415 check for POST requests to /api/v1/patrons Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: divinity76(a)gmail.com if you send a POST request to /api/v1/patrons with the header Content-Type: application/x-www-form-urlencoded which is a default header for curl and libcurl with POST requests, by the way, then Koha will try to parse it as a JSON, which leads to questions like this https://stackoverflow.com/questions/68106741/post-koha-patrons-to-koha-lms-… and responses like this ``` { //Here is missing some code. "errors": [{ "message": "Missing property.", "path": "/body/address" }, { "message": "Missing property.", "path": "/body/category_id" }, { "message": "Missing property.", "path": "/body/city" }, { "message": "Missing property.", "path": "/body/library_id" }, { "message": "Missing property.", "path": "/body/surname" }], "status": 400 } ``` while HTTP 400 is a pretty good response, the correct response for unsupported Content-Type is actually >HTTP/1.1 415 Unsupported Media Type and the error message could be something like { "errors": [{ "message": "request body must be application/json" }], ] -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7