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

[Bug 8676] Show vendor name in source of acquisition
by bugzilla-daemon＠bugs.koha-community.org 02 Sep '26

02 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8676 koha-US bug tracker <bugzilla(a)koha-us.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bugzilla(a)koha-us.org -- You are receiving this mail because: You are watching all bug changes.

1 0

[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 43137] New: Add system health monitoring with status indicators in the staff interface header
by bugzilla-daemon＠bugs.koha-community.org 02 Sep '26

02 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43137 Bug ID: 43137 Summary: Add system health monitoring with status indicators in the staff interface header Initiative type: --- Sponsorship --- status: 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 Target Milestone: --- Koha depends on several services (search engine, background job workers, SFTP endpoints) but provides no at-a-glance visibility into their health. Staff discover problems only when operations fail -- a patron search returns nothing, a batch job silently stops, or EDI transfers accumulate. Proposed solution: A system health framework that checks services, collects warnings and critical messages, and surfaces a summary indicator in the staff interface header. API response structure: GET /api/v1/health { "core": [ { "id": "search_engine", "label": "Search engine", "warnings": [ "Index koha_biblios last reindexed 3 days ago" ], "critical": [ "Elasticsearch cluster is red: 2 shards unassigned" ] }, { "id": "background_jobs", "label": "Background jobs", "warnings": [], "critical": [] }, { "id": "sftp", "label": "SFTP connections", "warnings": [ "EDI vendor X: connection timeout on last attempt" ], "critical": [] } ], "plugins": {} } - 'core' is an array of check results from Koha's own service checks - 'plugins' is a hash keyed by plugin class -- populated by companion bug (plugin hook) - Each check has 'warnings' and 'critical' arrays of human-readable messages - Empty arrays = healthy Header indicator logic: - Red: any 'critical' list is non-empty (core or plugins) - Yellow: any 'warnings' list is non-empty, no criticals - Green: all lists empty - Click navigates to detail view (new tab in about.pl System information, or standalone page) Core health checks to implement initially: - Search engine (Elasticsearch/Zebra): cluster/daemon reachability, index staleness - Background jobs: oldest pending job exceeds threshold (workers not picking up), failed jobs accumulating - SFTP connections: configured EDI/acquisition targets failing to connect Architecture: 1. Health check classes (Koha::Health::SearchEngine, Koha::Health::BackgroundJobs, Koha::Health::SFTP): - Each implements check() returning { id, label, warnings => [...], critical => [...] } - Checks must be cheap -- query local state only 2. API endpoint GET /api/v1/health: - Runs all core checks - Calls health_check plugin hook (see companion bug) - Caches the full assembled response (core + plugins) in Memcached with 30s TTL - A single cache key serves all users since health status is global - 60 terminals polling every 60s = ~1 req/s; with 30s cache only 2 actual check runs per minute - Permission-gated 3. Staff interface: - JS poller in header.inc, hits endpoint every 60s - Renders summary dot with tooltip showing count of warnings/criticals - Detail view groups checks by source (core section, then per-plugin sections) Display considerations: - Detail view could be a new tab on about.pl alongside existing system information - Or a standalone page -- either way, should render core and plugin sections grouped - Healthy checks still appear (as OK) so staff can see what is being monitored Caching: The endpoint caches the full assembled response in Memcached with a 30s TTL. A single cache key (koha:health) serves all users since health status is global -- not per-user or per-branch. 60 staff terminals polling every 60s means roughly 1 request per second on average. With a 30s cache, at most 2 actual health check runs happen per minute regardless of terminal count. Cache is TTL-based only -- no explicit invalidation needed since 30s staleness is acceptable for a status dot. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 45

[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 43072] New: Hold policies display incorrectly in circ rules page
by bugzilla-daemon＠bugs.koha-community.org 02 Sep '26

02 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43072 Bug ID: 43072 Summary: Hold policies display incorrectly in circ rules page Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Hold requests 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, lisette(a)bywatersolutions.com, tomascohen(a)gmail.com Depends on: 41267 Target Milestone: --- Bug 41267 added a new hold policy type to the "Default holds and bookings policies by item type" section at the bottom of the page, "Fill other record level holds on record at checkout." If this policy is set to Yes or undefined, an item of the given itemtype can fill a bib-level hold even if the itemtype doesn't otherwise allow holds. If the policy is set to No, then the itemtype will not fill record-level holds. On upgrade, Bug 41267 does not set anything in the circulation_rules for this policy. After upgrade, any itemtype that has a value set for something else in this section will show a value of "No" for "Fill other record level holds on record at checkout" even though this policy isn't actually set. So the upgrade doesn't actually change any circ behavior, but it shows an erroneous change in the circ rules. To recreate: - be on a version of Koha without this code (25.11.04 or older) - set Hold Policy = "No holds allowed" for an itemtype - upgrade Koha to a version with this code - reload the circ rules page, confirm the Default holds and bookings policies by item type section still shows your Hold Policy value and *also* shows "Fill other record level holds on record at checkout" set to "No" for your itemtype - query "select * from circulation_rules where rule_name='fill_other_biblio_holds_policy'" and confirm no rule exists in the database - confirm a record-level hold can still be filled with an item of your itemtype - update your circ rules to actually save a No for "fill other record level holds" - confirm this now shows in your circ rules query - confirm a hold no longer fills It seems simplest to make this table show "Yes" when no policy exists. But on the other hand in current main I cannot set any rule in this table without also setting a "Fill other record level holds" value, so maybe it would be more consisten to actually save a "Yes" rule for 'fill_other_biblio_holds_policy' on any itemtype that already has something set for any other rule here. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41267 [Bug 41267] It should be possible to prevent some itemtypes from filling other biblio level holds -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 33

[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 43029] New: Guard maintenance scripts against biblios with corrupt metadata
by bugzilla-daemon＠bugs.koha-community.org 02 Sep '26

02 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43029 Bug ID: 43029 Summary: Guard maintenance scripts against biblios with corrupt metadata 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: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org Depends on: 35104 Target Milestone: --- Bug 35104 makes Koha::Biblio::Metadata->record()/store() throw Koha::Exceptions::Metadata::Invalid for a record whose MARCXML cannot be decoded. misc/maintenance/sanitize_records.pl and misc/maintenance/touch_all_biblios.pl both read a biblio's metadata record and unconditionally re-save it across every biblio in the database, so a single already-corrupt record (which could exist from before bug 35104, or from a source outside Koha's own validation) would abort the whole run. This patch wraps the read (and, for touch_all_biblios.pl, the resulting ModBiblio) so one such biblio is skipped and reported rather than aborting the whole maintenance run. Depends on bug 35104. Test plan: 1. Apply this patch on top of bug 35104. 2. Create a biblio with metadata that is already corrupt, bypassing Koha::Biblio::Metadata's validation (e.g. write invalid MARCXML directly to the biblio_metadata row via the DBIC schema result, not through ->store()), alongside several normal biblios. 3. Run misc/maintenance/sanitize_records.pl --verbose across all biblios. Confirm the corrupt one is skipped with a clear "ERROR: Invalid record" message and the script completes for every other biblio without dying. 4. Run misc/maintenance/touch_all_biblios.pl similarly. Confirm the corrupt record is counted/logged as an error and the other records are still touched successfully. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35104 [Bug 35104] We should warn when attempting to save MARC records that contain characters invalid in XML -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 11