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

[Bug 40774] New: EBSCO Packages search box is missing
by bugzilla-daemon＠bugs.koha-community.org 03 Dec '25

03 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40774 Bug ID: 40774 Summary: EBSCO Packages search box is missing Change sponsored?: --- Product: Koha Version: 25.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: ERM Assignee: jonathan.druart(a)gmail.com Reporter: christian.nelson(a)uwasa.fi QA Contact: testopia(a)bugs.koha-community.org CC: jonathan.druart(a)gmail.com, jonathan.field(a)openfifth.co.uk, martin.renvoize(a)openfifth.co.uk, matt.blenkinsop(a)openfifth.co.uk, pedro.amorim(a)openfifth.co.uk In ERM module (/cgi-bin/koha/erm/eholdings/ebsco/packages) the EBSCO packages search box is missing. Instead of the search box an empty page is shown. Chrome Console says: runtime-core.esm-bundler.js:275 TypeError: Cannot read properties of undefined (reading 'authorised_values') at Proxy.<anonymous> (EHoldingsEBSCOPackagesList.vue:14:36) at a7 (runtime-core.esm-bundler.js:6502:16) at A.s [as fn] (runtime-core.esm-bundler.js:5319:46) at A.run (reactivity.esm-bundler.js:225:19) at U (runtime-core.esm-bundler.js:5454:5) at P (runtime-core.esm-bundler.js:5229:7) at I (runtime-core.esm-bundler.js:5182:9) at y (runtime-core.esm-bundler.js:4700:11) at A.s [as fn] (runtime-core.esm-bundler.js:5406:9) at A.run (reactivity.esm-bundler.js:225:19) The EBSCO titles search (/cgi-bin/koha/erm/eholdings/ebsco/titles) seems to be working normally. -- You are receiving this mail because: You are watching all bug changes.

1 25

[Bug 34428] New: update database create a wrong table transport_cost
by bugzilla-daemon＠bugs.koha-community.org 03 Dec '25

03 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34428 Bug ID: 34428 Summary: update database create a wrong table transport_cost Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Database Assignee: koha-bugs(a)lists.koha-community.org Reporter: didier.gautheron(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Hi, it's using the initial definition from the first patch with : CONSTRAINT `CONSTRAINT_1` CHECK (`frombranch` <> `tobranch`) which never works and doesn't import in Maria db 10.6 Regards Didier, -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 31422] New: Library limitations might cause data loss
by bugzilla-daemon＠bugs.koha-community.org 03 Dec '25

03 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31422 Bug ID: 31422 Summary: Library limitations might cause data loss Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, michaela.sieber(a)kit.edu The library limitations are used to limit down the selection in pull downs in several spots. If you are editing data from library B while logged in at library A, doing so might result in data loss as the value stored in the modified object might be missing from the drop downs your user sees. Example 1: Item values Itemtype: BK Books - limited to Centerville AV LOC: FIC Fiction - limited to Centerville Your user: logged in for Centerville * Edit an item and make sure it uses the itemtype Books and location Fiction. * Switch library to any but Centerville. * Edit item: Both item type and location drow downs will be empty. * Saving now will empty out itemtype (if not set mandatory) and location resulting in data loss. Example 2: Patron data Patron category: Patron PT - limited to Centerville Your user: logged in for Centerville * Find a patron with the limited patron category * Edit patron: Verify the patron category shows in pull down * Switch library to any but Centerville * Edit patron: the category pull down will show the first entry of the pull down visible for this library. Saving now, you will change the patron category unknowingly resulting in data loss. Additional bug: If you search for "all patrons", you will have an error in the console no patrons will display: Uncaught TypeError: categories_map[data] is undefined. Filed as bug 31421. I think we need to make sure that the pull downs show what the library can use, but also what the current setting of the object is in order to prevent data loss. IIRC the funds pull down on the receive page uses a mechanism for this. Otherwise library limitations are very dangerous to use and can only be recommended if we can make sure that objects from other libraries cannot be edited at all where library limitations have been applied. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 42

[Bug 20269] New: Allow selecting default collate rule
by bugzilla-daemon＠bugs.koha-community.org 03 Dec '25

03 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20269 Bug ID: 20269 Summary: Allow selecting default collate rule Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Database Assignee: koha-bugs(a)lists.koha-community.org Reporter: pasi.kallinen(a)joensuu.fi QA Contact: testopia(a)bugs.koha-community.org For some languages, the default collate rule set in kohastructure.sql, utf8_unicode_ci, doesn't work correctly. For example, Finnish alphabet expects the alphabet to sort abc...xyzåäö, but the unicode_ci rule doesn't handle the åäö right. Instead, we need to use the swedish_ci rule. It would be nice to be able to define the default collate rule during install. Problem can be seen for example when you go catalogue a new record and have frameworks starting with 'ä' or 'ö', those will sort incorrectly. On the database, you can test this with: insert into biblio_framework (frameworkcode, frameworktext) values ('TEST', 'Äänikirja'); -- Note where the 'Äänikirja' is located select * from biblio_framework order by frameworktext collate utf8_unicode_ci; -- And then the correct order, with 'Äänikirja' last: select * from biblio_framework order by frameworktext collate utf8_swedish_ci; -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 41109] New: Incorrect patron information when previously overdue and lost book is returned after item is marked lost when not checked out
by bugzilla-daemon＠bugs.koha-community.org 02 Dec '25

02 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41109 Bug ID: 41109 Summary: Incorrect patron information when previously overdue and lost book is returned after item is marked lost when not checked out Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The issue is that when charging a new overdue fine, the previous fine is left as 'OVERDUE' / 'LOST' which triggers a message of 'lost_charge' which pulls the info for the latest patron to return the item. Even if the info doesn't match a lost charge, we display it To recreate: 1 - Set the Default lost item fee refund on return policy - to 'charge' (Refund lost item charge and charge new overdue fee) 2 - Ensure circulation rule for item has fine amount and interval 3 - Set system preference WhenLostChargeReplacementFee to charge 4 - Checkout an item with a replacement fee set, backdating a month 5 - Have syspref DefaultLongOverdueChargeValue and DefaultLongOverdueLostValue set to same value and DefaultLongOverdueDays to 10 6 - perl misc/cronjobs/fines.pl 7 - View patron account, confirm overdue charged 8 - perl misc/cronjobs/longoverdue.pl --confirm 9 - View patron account, confirm item lost and lost fine charged 10 - Checkin the item 11 - Check the patron's accountlines SELECT * FROM accountlines WHERE borrowernumber=### AND debit_type_code='OVERDUE' 12 - Note that there are two, the original with status 'LOST' and a new one with status 'FOUND' 13 - Ensure syspref ShowAllCheckins is set to 'Show' 14 - Check out the item to another patron, and return it 15 - Mark the item lost 16 - Check it in again 17 - You see the name of the patron from step 14 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 9750] Bring routing lists into notices & slips
by bugzilla-daemon＠bugs.koha-community.org 02 Dec '25

02 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9750 Jessie Zairo <jzairo(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jzairo(a)bywatersolutions.com -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 30298] New: Ability to print labels from Serial Collection
by bugzilla-daemon＠bugs.koha-community.org 02 Dec '25

02 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30298 Bug ID: 30298 Summary: Ability to print labels from Serial Collection Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: jzairo(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 131758 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=131758&action=e… add-button-option It would be great to have a print label button from the serial collection information in the serials module. cgi-bin/koha/serials/serials-collection.pl?subscriptionid=1 After a user saves or updates the latest issue they are taken to the serial collection page where they have buttons for editing generating the next serial and deleting selected issues. It would be helpful to have a button to print the labels for the items a user just created from this screen. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 12104] Add print label to serials receive
by bugzilla-daemon＠bugs.koha-community.org 02 Dec '25

02 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12104 --- Comment #3 from Lucas Gass (lukeg) <lucas(a)bywatersolutions.com> --- *** Bug 30298 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 41301] New: Custom fields can not be deleted in ill requests
by bugzilla-daemon＠bugs.koha-community.org 02 Dec '25

02 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41301 Bug ID: 41301 Summary: Custom fields can not be deleted in ill requests Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: bibliothek(a)th-wildau.de QA Contact: testopia(a)bugs.koha-community.org CC: lisette(a)bywatersolutions.com, pedro.amorim(a)openfifth.co.uk, tomascohen(a)gmail.com When removing custom fields in ill request, they get removed in the UI but remain saved in the database. 1) Enable ILLModule 2) Create an ILL request: <staff_url>/cgi-bin/koha/ill/ill-requests.pl?method=create&backend=Standard 3) Pick any type, add '42' for cardnumber and any library 4) Edit item metadata (assuming ID 1): <staff_url>/cgi-bin/koha/ill/ill-requests.pl?op=edititem&illrequest_id=1 5) Click 'Add new field' under 'Custom fields' 6) Add any key value pair but avoid 0 for the value to not run into #41281 7) Click 'Update'. Notice the custom field does show. 8) Edit the item again and remove the created key/value pair. 9) Update the request and you will find the key/value pair still remaining -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 41302] New: Migration de koha 24.05 à 24.11
by bugzilla-daemon＠bugs.koha-community.org 02 Dec '25

02 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41302 Bug ID: 41302 Summary: Migration de koha 24.05 à 24.11 Initiative type: --- Sponsorship --- status: Product: Koha Version: 24.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Database Assignee: koha-bugs(a)lists.koha-community.org Reporter: rachidayssi(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Bonjour, Lors de la migration de Koha 24.05 à koha 24.11 je reçois l'erreur suivante : ERROR: {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Can't DROP FOREIGN KEY `afv_fk`; check that it exists at /usr/share/koha/lib/C4/Installer.pm line 743 Je vous remercie pour toute suggestion de l'origine du problème. Cdt. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1