July 2025 - Koha-bugs - lists.koha-community.org

[Bug 40464] New: Many parts of C4::Auth::checkauth() re-lookup the patron using userid/cardnumber unnecessarily
by bugzilla-daemon＠bugs.koha-community.org 22 Jul '25

22 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40464 Bug ID: 40464 Summary: Many parts of C4::Auth::checkauth() re-lookup the patron using userid/cardnumber unnecessarily Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org While bug 40275 introduces Koha::Patrons->find_by_identifier() into C4::Auth in one place in C4::Auth::checkpw(), C4::Auth::checkauth() needlessly looks up the borrower again (multiple times) even though we've already looked it up before. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 40457] New: Wherever possible we should lookup using borrowernumber instead of userid/cardnumber
by bugzilla-daemon＠bugs.koha-community.org 22 Jul '25

22 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40457 Bug ID: 40457 Summary: Wherever possible we should lookup using borrowernumber instead of userid/cardnumber Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org As we note on bug 40275, there are times where we lookup the patron using cardnumber or userid when we really should be using borrowernumber where possible. Not all Koha users will have a cardnumber plus we have on-going issues around uniqueness of cardnumber and userid whereas borrowernumber is an internal persistent and unique identifier. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 40461] New: Koha should return 403 when a feature is disabled
by bugzilla-daemon＠bugs.koha-community.org 22 Jul '25

22 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40461 Bug ID: 40461 Summary: Koha should return 403 when a feature is disabled Change sponsored?: --- Product: Koha Version: Main 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 This should be an umbrella bug, unless there are no conflicting cases and we can solve them all in this report. Picking `opac-export.pl` as an example, if there are no export formats enabled, the tool returns a 400. This status code means: ``` The HTTP 400 Bad Request client error response status code indicates that the server would not process the request due to something the server considered to be a client error. The reason for a 400 response is typically due to malformed request syntax, invalid request message framing, or deceptive request routing. ``` I propose we standardize on `403` [1] [1] https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/403 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 39129] New: Add a notification for staff when a new ILL request is made
by bugzilla-daemon＠bugs.koha-community.org 21 Jul '25

21 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39129 Bug ID: 39129 Summary: Add a notification for staff when a new ILL request is made Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: pedro.amorim(a)ptfs-europe.com, tomascohen(a)gmail.com We don't have a notification for staff when a new ill request is made. It could be useful, and we have that kind of notification when a suggestion is made -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 40462] New: Preferred_name values distinct from firstname should not be lost when preferred_name set in BorrowerUnwantedFields
by bugzilla-daemon＠bugs.koha-community.org 21 Jul '25

21 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40462 Bug ID: 40462 Summary: Preferred_name values distinct from firstname should not be lost when preferred_name set in BorrowerUnwantedFields Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com Current behavior: - set a patron to have a preferred_name distinct from their firstname - set BorrowerUnwantedField to hide preferred_name - refresh your patron, confirm their preferred_name has not changed - on your patron, click Edit and then Save without changing anything - confirm your patron's preferred_name has been updated to match their firstname In contrast, if you give a patron a fax number and then hide fax via borrowerunwantedfield, that fax number remains on the patron record and cannot be edited or removed by staff. In preferred_name is included in BorrowerUnwantedField, we should only update preferred_name to match firstname if preferred_name and firstname matched before we edited the patron. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 36596] New: Opening/closing hours should be forced to be set together
by bugzilla-daemon＠bugs.koha-community.org 21 Jul '25

21 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36596 Bug ID: 36596 Summary: Opening/closing hours should be forced to be set together Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal 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 only seems to make sense to set a closing hour if an opening hour has been set, otherwise it would be open 24 hs :-D A method needs to be added to Koha::Library: * set_hours( $dow, $opening, $closing ) * The method needs to throw an exception if one of them is not passed * If none is passed then it means the library would not be open, and then all hours for the * The code for setting the hours in branches.pl should be removed and this method used instead * The method MUST BE COVERED BY TESTS NOTE: I don't personally like the chosen column name 'day'. I would use either 'dow' or 'day_of_week'. And it should be clear which one is the first in the comments. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 40450] New: Add context for "To:" to allow for better translation
by bugzilla-daemon＠bugs.koha-community.org 21 Jul '25

21 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40450 Bug ID: 40450 Summary: Add context for "To:" to allow for better translation Change sponsored?: --- Product: Koha Version: 24.11 Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: f.demians(a)tamil.fr, jonathan.druart(a)gmail.com At least in German different translation is required for "To" in different context: * Sending an email "to" someone: "an" * Specifying a timeframe from - to: "bis" This problem is visible especially in this string, where notices.tt would require "An", but others would require "Bis": https://translate.koha-community.org/translate/koha/24-11/staff-prog/de/?ch… -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 39962] New: Recalled status does not show properly on staff interface record detail page
by bugzilla-daemon＠bugs.koha-community.org 21 Jul '25

21 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39962 Bug ID: 39962 Summary: Recalled status does not show properly on staff interface record detail page Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com To reproduce: 1. Enable the UseRecalls system preference and set the recalls-related circulation and fines rules. 2. Search for an item. 3. Check out an item to Patron B. 4. Log into the OPAC as Patron A. 5. Request a record-level recall on the record. 6. View the record on the staff interface and look at the holdings table. Notice that the checked out item shows no indication of being recalled, but the recall request does show on the Recalls tab. --> BUG 7. Go to the Recalls tab and cancel the recall. 8. Go back to the OPAC and request an item-level recall on the checked out item. 9. View the record on the staff interface and look at the holdings table. Notice that the checked out item now shows the recalled status, twice. "Recalled by koha (42) on DATE" --> BUG -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 20472] New: Working title
by bugzilla-daemon＠bugs.koha-community.org 21 Jul '25

21 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20472 Bug ID: 20472 Summary: Working title Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 90

[Bug 23771] New: CAS/Shib Authentication can fail when multiple users with no userid/cardnumber defined and one of them is locked
by bugzilla-daemon＠bugs.koha-community.org 21 Jul '25

21 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23771 Bug ID: 23771 Summary: CAS/Shib Authentication can fail when multiple users with no userid/cardnumber defined and one of them is locked Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Authentication Assignee: nick(a)bywatersolutions.com Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org When logging in via cas no userid is passed to checkpw, however, we still seek out users with a null userid/cardnumber. If one of those users has a locked account and it happens to be the one chosen, we won't continue to CAS/Shib login (or LDAP, but LDAP shouldn't get a blank userid) -- You are receiving this mail because: You are watching all bug changes.

1 13