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

[Bug 43093] New: Allow biblioitems.totalissues to keep correct numbers on merged records
by bugzilla-daemon＠bugs.koha-community.org 02 Sep '26

02 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43093 Bug ID: 43093 Summary: Allow biblioitems.totalissues to keep correct numbers on merged records Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: michael.adamyk(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Target Milestone: --- Currently, the 942$0 is used to store biblioitems.totalissues. When merging bibliographic records, Koha allows merging holds and items, but not this field, which means any totals on the non-primary bib records are lost during the merge. Due to bug 42504, it appears that biblioitems.totalissues will be moved out of the MARC record and directly into the database. If that bug passes, would it be possible to add together the totals of all merged records' totalissues for a new total on the merged record? -- 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 Michelle Spinney <mspinney(a)clamsnet.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mspinney(a)clamsnet.org -- You are receiving this mail because: You are watching all bug changes.

1 0

[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 Michelle Spinney <mspinney(a)clamsnet.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mspinney(a)clamsnet.org -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 34488] New: Import default framework
by bugzilla-daemon＠bugs.koha-community.org 02 Sep '26

02 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34488 Bug ID: 34488 Summary: Import default framework Change sponsored?: --- Product: Koha Version: 23.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: viliam.polonec(a)snk.sk QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com I am testing 23.05.01 version, so we can update our production ILS. I found that I can't import default framework for bibliographic records. I tried export it and import. But with no success. KOHA shows MARC Framework for default MARC framework Create framework for () using selector with frameworks After that nothings changed I test it on two different instalations. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[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 Chip Halvorsen <Chip.Halvorsen(a)WestlakeLibrary.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Chip.Halvorsen@WestlakeLibr | |ary.org -- You are receiving this mail because: You are watching all bug changes.

1 0

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