March 2026 - Koha-bugs - lists.koha-community.org

[Bug 42147] New: Action logs for hold creation contain less data
by bugzilla-daemon＠bugs.koha-community.org 24 May '26

24 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42147 Bug ID: 42147 Summary: Action logs for hold creation contain less data Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: emily.lamancusa(a)montgomerycountymd.gov QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, lisette(a)bywatersolutions.com, tomascohen(a)gmail.com In 24.11, the "info" column in the action logs for a hold creation action contained the full hold data. As of 25.05 and onward, this is no longer the case. Holds created through the staff interface show only the reserve_id in the "info" column, and holds created by API show the API arguments, which is a bit more helpful, but still not as much data as the "info" column used to contain. This makes it harder to search for the logs of a specific hold, and in some cases harder to determine whether an unexpected hold option/status was user error on the part of whoever placed the hold, or whether that unexpected state occurred later. It would be very helpful to restore the behavior of logging the full hold object data in the "info" column. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 24

[Bug 42142] New: The gear icon to toggle panel for login settings needs accessibility updates
by bugzilla-daemon＠bugs.koha-community.org 24 May '26

24 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42142 Bug ID: 42142 Summary: The gear icon to toggle panel for login settings needs accessibility updates Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Accessibility Assignee: koha-bugs(a)lists.koha-community.org Reporter: blawlor(a)clamsnet.org QA Contact: testopia(a)bugs.koha-community.org CC: martin.renvoize(a)openfifth.co.uk, matt.blenkinsop(a)openfifth.co.uk, oleonard(a)myacpl.org View source on any Koha page and paste into the W3C Markup Validation Service. https://validator.w3.org/#validate_by_input Notice the error: The aria-label attribute must not be specified on any i element unless the element has a role value... This violates WCAG 1. 4.1.2 Name, Role, Value (Level A) I think the <a> element should have the role button and aria-label Toggle panel for login settings and the <i> element should have aria-hidden="true" The Toggle panel for login settings also needs some work to announce its state as collapsed and expanded to be more accessible for screen readers. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 42020] New: (Bug 39482 follow-up) Library info link shown in OPAC without OpacLibraryInfo and library URL
by bugzilla-daemon＠bugs.koha-community.org 24 May '26

24 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42020 Bug ID: 42020 Summary: (Bug 39482 follow-up) Library info link shown in OPAC without OpacLibraryInfo and library URL Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: januszop(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Prior to Bug 39482 a link to library info modal (with (i) icon) was generated only if OpacLibraryInfo was defined. Now it is there even if there is no OpacLibraryInfo at all and no URL defined for the library. It is generated in any circumstances. (BTW this makes the following snippet from opac-detail.tt dead: [% ELSIF holding_library_url %] <a href="[% holding_library_url | url %]"> [% holding_library_name | html %] </a> [% ELSE %] <span>[% holding_library_name | html %]</span> [% END %] ) This is because Koha::Library::opac_info returns a RS now, and not an object, as it was before. So a test on $item->holding_branch->opac_info( { lang => $lang } ) in opac-detail.pl returns always true. To reproduce: 1) Have a standard ktd installation. 2) Make sure there is no OpacLibraryInfo defined in HTML customizations. 3) Make sure there is no URL for any library. 4) In OPAC, perform any search. On a detail page you would see a link to an empty modal from the Current library items column. -- You are receiving this mail because: You are watching all bug changes.

1 20

[Bug 41944] New: Error 500 on non-existent ILL request (op=illview)
by bugzilla-daemon＠bugs.koha-community.org 24 May '26

24 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41944 Bug ID: 41944 Summary: Error 500 on non-existent ILL request (op=illview) Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: lisette(a)bywatersolutions.com, pedro.amorim(a)openfifth.co.uk, tomascohen(a)gmail.com It should be returning the usual 404, but is no checking it and throwing template errors instead. To reproduce: 1. Have KTD launched with an ILL backend loaded: $ ktd --proxy --name rapido --single-plugin ~/git/koha-plugins/rapido-ill up -d $ ktd --shell k$ cd /kohadevbox/plugins/rapido-ill/scripts k$ perl bootstrap_rapido_testing.pl k$ restart_all 2. Log into the instance at `http://rapido-admin.localhost` 3. Point your browser to a [non-existent ILL request](http://rapido-intra.localhost/cgi-bin/koha/ill/ill-requests.pl?op=illview&illrequest_id=1000) => FAIL: Boo, template errors and stacktrace Note: In production, the you get a 500 error and the template errors show up in the logs. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 26

[Bug 41883] New: Modifications using batch hold modification tool aren't logged
by bugzilla-daemon＠bugs.koha-community.org 24 May '26

24 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41883 Bug ID: 41883 Summary: Modifications using batch hold modification tool aren't logged Initiative type: --- Sponsorship --- status: Product: Koha Version: 25.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: sbrown(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Changes made via the batch hold modification tool that are logged when made to holds individually from the bib are not logged when using the tool. To replicate: -Place a hold -Run the Holds log using the hold's reserve_id. There will be a single entry for the hold's creation. -Find the hold using the batch hold modification tool, and update its pickup location -Run the Holds log for that hold, and note that no entry has been generated for the changed pickup location -From the bib's Holds tab, update the same hold's pickup location -Run the Holds log again for that hold, and note that an entry was generated for the pickup location change when it was updated from the bib The same issue applies for updating expiration dates and for suspending/unsuspending, all of which do generate log entries when performed on individual holds from the bib. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 41882] New: Batch hold modification tool updates pickup locations to disallowed libraries
by bugzilla-daemon＠bugs.koha-community.org 24 May '26

24 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41882 Bug ID: 41882 Summary: Batch hold modification tool updates pickup locations to disallowed libraries Initiative type: --- Sponsorship --- status: Product: Koha Version: 25.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: sbrown(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org If a library's 'Holds and bookings policies by item type' is set to only allow pickup at an item's home library, the batch hold modification tool can still be used to update a hold's pickup location to other libraries such that the hold will never trigger to fill. To replicate: -Set ReservesControlBranch to 'item's home library' -Set Main library's 'Holds and bookings policies by item type' so that PASS items can only be picked up at Main -Place a hold on a bib whose only item is a PASS belonging to Main -Use the Batch hold modification tool to identify the hold you just placed -Update the pickup location to North. Note that the update is successful, and there's no indication that the pickup location is now a problem. -Check in Main's PASS, and note that the hold doesn't trigger to fill The batch update shouldn't process for holds where the change will make the hold unfillable per a library's 'Holds and bookings policies by item type'. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 29

[Bug 41880] New: Logs for moved holds don't indicate original bib number/item number
by bugzilla-daemon＠bugs.koha-community.org 24 May '26

24 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41880 Bug ID: 41880 Summary: Logs for moved holds don't indicate original bib number/item number Initiative type: --- Sponsorship --- status: Product: Koha Version: 25.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: sbrown(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, lisette(a)bywatersolutions.com, tomascohen(a)gmail.com If a hold is moved from bib A to bib B (or from item A to item B), and no change was made to the hold before the move, there is no way to identify the bib or item number of the original hold. To replicate: -Place a hold on bib A (or item A) -View it in Tools > Logs using the reserve_id. As is standard, no details other than the reserve_id show in the Info column. -Move the hold to bib B (or item B) -Run the holds log again for the reserve_id. Note that an entry is generated for the move, but only the bib number (or item number) it was *moved to* shows. There is no way to know what bib or item the hold was moved *from*. If a change is made to a hold before it's moved, staff will be able to see the original bib number/item number in logs. But there are likely to be many cases where the first change made to a hold is moving it to a new bib/item, which means that the original bib number/item number will be untraceable. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 32

[Bug 41843] New: Koha::Authorities->move
by bugzilla-daemon＠bugs.koha-community.org 24 May '26

24 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41843 Bug ID: 41843 Summary: Koha::Authorities->move Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 41801] New: FixPriority recursive calls for lowestPriority holds can be removed
by bugzilla-daemon＠bugs.koha-community.org 24 May '26

24 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41801 Bug ID: 41801 Summary: FixPriority recursive calls for lowestPriority holds can be removed Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests 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, lisette(a)bywatersolutions.com, tomascohen(a)gmail.com Currently, C4::Reserves->FixPriority adjusts the holds not marked for lowestPriority, then recursively calls itself for each lowestPriority hold, touching all the non-found holds on the record each time. This can be removed as we can simply sort the lowestPriority holds to the bottom when getting the list of holds to adjust -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 31

[Bug 41795] New: UNIMARC: a Zebra search for Corporate Body Name authorities will also return Collective Titles
by bugzilla-daemon＠bugs.koha-community.org 24 May '26

24 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41795 Bug ID: 41795 Summary: UNIMARC: a Zebra search for Corporate Body Name authorities will also return Collective Titles Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Zebra Assignee: koha-bugs(a)lists.koha-community.org Reporter: a.roussos(a)dataly.gr QA Contact: testopia(a)bugs.koha-community.org As per the Bug Summary, when you search for Corporate Body Name authorities (authtypecode 'CO') in the OPAC or in the Staff interface, the results will also include Collective Titles (authtypecode 'CO_UNI_TI'). The problem manifests in UNIMARC instances that use the default authority type codes and a Zebra search backend. AIUI, it has to do with 'Corporate Body Name' authorities using an authtypecode ('CO') that just so happens to be the prefix of another authtypecode ('CO_UNI_TI') used by 'Collective Title' authorities. Out of the box, MARC21 instances aren't affected by this. However, in the (unlikely?) scenario that you've decided to catalog authorities under different authtypes than the built-in ones and somehow managed to add new authority types that share the same prefix ('AUTH', 'AUTH_CORP', 'AUTH_PERS', etc.), then you will run into problems when searching as there will be no guarantee that filtering for the specific authority type 'AUTH' will return only the results you will be expecting. Elasticsearch is not affected -- it's a Zebra-only thing. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 31