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

[Bug 30360] New: Add helper methods to Koha::BackgroundJobs
by bugzilla-daemon＠bugs.koha-community.org 02 Feb '23

02 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30360 Bug ID: 30360 Summary: Add helper methods to Koha::BackgroundJobs Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org It would be handy to have background jobs just call a simple method for: * Setting the job as started * Updating the progress * Setting as finished -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 40

[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 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

[Bug 27064] New: Transferring an item with a hold allows the user to set a hold waiting without transferring to the correct branch
by bugzilla-daemon＠bugs.koha-community.org 31 Jan '23

31 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27064 Bug ID: 27064 Summary: Transferring an item with a hold allows the user to set a hold waiting without transferring to the correct branch 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com To recreate: 1 - Place a hold for delivery at Library B 2 - Sign in at Library A 3 - Browse to Circulation->Transfers 4 - Attempt to transfer an item on the title with the hold to Library B 5 - You get a notice that hold was found (missing patron/branch info) 6 - You have the option to set the hold waiting - click it 7 - The transfer is generated and marked completed 8 - The hold is marked as waiting, but the item is still at Library A and no transfer is active 9 - The patron is notified that the hold is waiting -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 80

[Bug 25854] New: Ability to add multiple guarantors affected ability to make guarantor fields mandatory
by bugzilla-daemon＠bugs.koha-community.org 31 Jan '23

31 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25854 Bug ID: 25854 Summary: Ability to add multiple guarantors affected ability to make guarantor fields mandatory Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com bug 14570 made the non-member guarantor fields visible on all patrons prior to this adding fields like 'contactname' to the BorrowerMandatoryFields system preference had the effect of making guarantors mandatory for child accounts only. Now adding those fields makes them required for all patron types, but does not make adding an actual guarantor mandatory. We need to restore a method of making guarantors mandatory for some patron types. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2