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

[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

[Bug 28911] New: Bcrypt settings are required for pseudonymization but are not set on upgrade
by bugzilla-daemon＠bugs.koha-community.org 02 Dec '25

02 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28911 Bug ID: 28911 Summary: Bcrypt settings are required for pseudonymization but are not set on upgrade Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Bug 24151 added a way to pseudonymize patron transactions. It added a new config to koha-conf <bcrypt_settings> This is added for new installs, but not for upgraded sites, and there are no instructions on the syspref or elsewhere for adding To recreate: 1 - Spin up a 20.05 (checkout 20.05.x and reset_all in kohadevbox) 2 - Upgrade to master (checkout master, updatedatabase) 3 - Enable pseudonymization 4 - Attempt a checkout 5 - boom you can manually add the settings by running the command below: htpasswd -bnBC 10 "" password | tr -d ':\n' | sed 's/$2y/$2a/' And pasting the results into <bcrypt_settings> in the config -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 41356] New: Remove cover image source information by default
by bugzilla-daemon＠bugs.koha-community.org 02 Dec '25

02 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41356 Bug ID: 41356 Summary: Remove cover image source information by default Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org There might be reasons for this, which I'm not aware of. I'm posting this so we have a specific place to discuss it. I never understood why we say 'Coce cover image' or 'Amazon cover image'. Both the end user just want to see a cover image, and not have the screen cluttered with useless texts. -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 9762] Log circulation overrides
by bugzilla-daemon＠bugs.koha-community.org 02 Dec '25

02 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9762 Lucas Gass (lukeg) <lucas(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |41358 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41358 [Bug 41358] action logs info column should always store JSON -- You are receiving this mail because: You are watching all bug changes.

1 0