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

[Bug 10190] Overdue notice triggers based on item type
by bugzilla-daemon＠bugs.koha-community.org 02 Sep '26

02 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10190 Pedro Amorim (ammopt) <pedro.amorim(a)openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Passed QA |Failed QA --- Comment #872 from Pedro Amorim (ammopt) <pedro.amorim(a)openfifth.co.uk> --- Hi guys, a few issues here: 1 - TalkingTech_itiva_outbound.pl A) In KTD, set 'TalkingTechItivaPhoneNotification' to 'On'. B) Run perl misc/cronjobs/thirdparty/TalkingTech_itiva_outbound.pl --type=OVERDUE -o /tmp/out.txt -v C) It dies: DBI Exception: DBD::mysql::st execute failed: Unknown column 'items.itemtype' in 'field list' - confirmed the items table only has itype, never had itemtype. 2 - Circulation triggers gated on the wrong permission (menu + router guard) A) Go to a patron's 'More' > 'Set permissions' tab. Check 'catalogue' (needed for basic staff login), and under circulation-rules sub-permissions, check only 'Manage overdue notice triggers' - leave 'Manage circulation rules' unchecked. B) Log in as that patron, go to 'Administration' - no 'Circulation triggers' link (admin-home.tt only checks CAN_user_parameters_manage_circ_rules). C) Visit http://localhost:8081/cgi-bin/koha/admin/circulation_triggers directly - loads briefly, then redirects to admin-home.pl (the Vue router guard also only checks CAN_user_parameters_manage_circ_rules, never manage_circ_triggers). 3 - It appears the migration scenario I pointed out in comment 192 is still a problem, if you apply patches and: updatedatabase yarn api:bundle yarn js:build restart_all And then access http://localhost:8081/cgi-bin/koha/admin/circulation_triggers - you get a 404. 4 - Clearing 'delay' input using 'X' vs keyboard clear A) 'Administration' > 'Circulation triggers' > 'Add new trigger' for any library/category. Set a Delay, a Notice, and a transport type. B) Select the Delay field's value and clear it via the 'X' clear button. C) Click 'Submit', notice the Delay value was kept the previous one. D) Select the Delay field's value and clear it via the keyboard (Backspace/Delete). Click 'Submit'. E) Confirm the trigger saved with no Delay value, despite Delay being effectively required for the trigger to ever function. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 43449] New: Restore multi-value export formatting for additional fields in datatables
by bugzilla-daemon＠bugs.koha-community.org 02 Sep '26

02 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43449 Bug ID: 43449 Summary: Restore multi-value export formatting for additional fields in datatables Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Target Milestone: --- When exporting a searchable, repeatable additional field to CSV/Excel from a Vue-rendered datatable, all values are concatenated into one cell with no separator (e.g. "Test 1Test2" instead of "Test 1, Test2"). Bug 41151 tried to fix this by rendering multi-value cells as newline-separated text for export, but that conflicted with the DataTables Buttons export sanitisation added for the CSV formula-injection fix (bug 37727), which strips newlines. That patch was reverted there - see comment 33 on bug 41151. At the time, correct handling of embedded newlines on export required datatables.net-buttons >= 3.2.0 (which introduced escapeExcelFormula) and a compatible datatables.net-vue3 >= 3.x (for DataTables 2.x/3.x support), while Koha's package.json was pinned to datatables.net-buttons ^2.3.4 and datatables.net-vue3 ^2.0.0. As of now, upstream npm has moved well past those thresholds: datatables.net-buttons is at 4.0.2, datatables.net-vue3 is at 3.0.8, and datatables.net core is at 3.0.3. Koha's package.json still pins the old versions, so the version blocker no longer applies, but the upgrade itself has not been attempted. This bug covers: 1. Upgrading datatables.net, datatables.net-buttons and datatables.net-vue3 to current major versions compatible with each other. 2. Auditing KohaTable.vue and any other Vue call sites for breaking changes introduced by those majors. 3. Re-implementing the export formatting half of the multi-value additional fields display (reverted in bug 41151) using the newer Buttons' native newline/escapeExcelFormula handling instead of the ad-hoc newline detection that was reverted. This is expected to be a substantial, standalone piece of work given how widely the Vue datatable component is used across the app (ERM, ILL, vendors, etc.), not a small follow-up patch. Test plan: N/A - no patch attached yet, this bug tracks the deferred scope described in bug 41151 comment 33/34/53. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 24807] New: Add "year" type to improve sorting by publication date
by bugzilla-daemon＠bugs.koha-community.org 02 Sep '26

02 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24807 Bug ID: 24807 Summary: Add "year" type to improve sorting by publication date Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: glasklas(a)gmail.com When sorting on date-of-publication (a year, field 008, positions 7-10), the current behavior when the field contains an invalid year (containing word characters like "uuuu" or just whitespace), these results appear first when sorting in descending order. Invalid values like these should really not be indexed at all. If so (having null values instead) they will always appear last when sorting, regardless of sort order. This fix adds a "year" search field type, that will reject any non-year values, resulting in a more user friendly sorting behavior. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 70

[Bug 43036] New: Prevent GetItemsForInventory from over-taxing resources
by bugzilla-daemon＠bugs.koha-community.org 02 Sep '26

02 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43036 Bug ID: 43036 Summary: Prevent GetItemsForInventory from over-taxing resources Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Blocks: 43016 Target Milestone: 26.11 GetItemsForInventory can eat up a lot of resources when called against a large collection. We should improve how we fetch and display this data. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43016 [Bug 43016] [OMNIBUS] Server resource protection -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 23333] New: Course Reserves: Instuctor search box positioning
by bugzilla-daemon＠bugs.koha-community.org 02 Sep '26

02 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23333 Bug ID: 23333 Summary: Course Reserves: Instuctor search box positioning Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: claire_gravely(a)hotmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Created attachment 91567 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=91567&action=ed… Screenshot When creating a new course in the course reserves module the "Instructor search" box is oddly positioned. Perhaps it could be moved more in line with 'Instructors'. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 8214] Create a bound with function
by bugzilla-daemon＠bugs.koha-community.org 02 Sep '26

02 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8214 Michaela Sieber <michaela.sieber(a)kit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |clemens.tubach(a)kit.edu, | |katrin.fischer(a)bsz-bw.de, | |michaela.sieber(a)kit.edu -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 42945] New: When a waiting hold is filled by another item it should have a status that can be seen in the interface
by bugzilla-daemon＠bugs.koha-community.org 02 Sep '26

02 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42945 Bug ID: 42945 Summary: When a waiting hold is filled by another item it should have a status that can be seen in the interface Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement 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 Target Milestone: --- When a hold is filled by a different item, it can leave another item waiting on the hold shelf, with no way for staff to check. We should add a status to these holds/items that cleared on checkin, and offer a way for staff to view these - on the holds over tab, or somewhere obvious -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 41282] New: We should alert staff when a checked out item fills a different hold for a patron
by bugzilla-daemon＠bugs.koha-community.org 02 Sep '26

02 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41282 Bug ID: 41282 Summary: We should alert staff when a checked out item fills a different hold for a patron 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 When an item is checked out and the patron has a hold on the biblio we will fill thart hold with the item in hand Sometimes the hold this item fills has another copy that is already in transit or waiting on the shelf. We need to alert staff when this happens -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 32

[Bug 6921] Alert librarian that a waiting reserve has been filled by another item
by bugzilla-daemon＠bugs.koha-community.org 02 Sep '26

02 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6921 Andrii Nugged <nugged(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=41809 -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 36024] New: Cancellation requests for waiting holds - errors caused by duplicate requests
by bugzilla-daemon＠bugs.koha-community.org 02 Sep '26

02 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36024 Bug ID: 36024 Summary: Cancellation requests for waiting holds - errors caused by duplicate requests Change sponsored?: --- Product: Koha Version: master 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 The Koha OPAC prevents duplicate waiting hold cancellation requests at the interface level, but if a duplicate request is sent through the API (e.g. from a discovery layer), it is not prevented. This causes the cancellation request to display twice on the Holds With Cancellation Requests table on the staff interface. When the item is checked in, the cancellation request and checkin logic are (at least partially) processed, but the page displays a 500 error, which is confusing to staff and prevents any modals from displaying. To reproduce on KTD: 1. Circulation Rules: add a Default waiting hold cancellation policy of all / all / yes (i.e. cancellation allowed for all patron categories and item types) 2. System preferences: Enable RESTBasicAuth 3. Place a hold and check the item in to set the hold to Waiting 4. In a kshell, send an API hold cancellation request from the command line: curl -u koha:koha --request DELETE 'http://127.0.0.1:8081/api/v1/holds/1' --header "Content-type: application/json" --header "x-koha-override: cancellation-request-flow" (if the hold ID is not 1, change the hold ID at the end of the request path accordingly) 5. Repeat step 4 6. Go to the Holds Waiting page and view the Holds With Cancellation Requests tab --> Note that two identical cancellation requests appear for that hold 7. Check in the item --> Note the error message 8. Confirm that the item state has been modified: --> Hold is gone from the Holds Waiting page --> Hold is gone from the bib record --> Item shows as available on the bib record and last seen date has been updated --> If RecordLocalUseOnReturn is enabled, a local use entry has been added to the statistics table -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8