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

[Bug 34090] New: Add context for AV category vs. patron category
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34090 Bug ID: 34090 Summary: Add context for AV category vs. patron category Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr Sometimes only the word category appears for patron category or AV category. As we have translated patron category differently to authorised value category, this creates some issues with translations. It would be nice to add some context here. Another solution could be to add "patron" and "authorised value" in front. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 34508] New: MARC modification templates have poor results when working with multiple of a field
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34508 Bug ID: 34508 Summary: MARC modification templates have poor results when working with multiple of a field Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: ephetteplace(a)cca.edu QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Created attachment 154334 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=154334&action=e… minimal example record MARC modification templates "copy and replace" actions struggle to modify records in an expected manner when there are multiple of the field being modified. There are at least two unexpected results: - a "copy and replace" on the "1st" of two fields results in the first field's modified subfield being copied to the second - using an "if" condition with either the "1st" or "all" fields also causes the first field's modified subfield to overwrite the second's subfield, even if the second does not meet the if condition I've attached a minimal MARC record with two 856 fields. The goal of a modification template should be to modify only the first "example.com" ‡u subfield while leaving the second untouched. However, both of these modification templates result in the second 856‡u being a copy of the first. 1) Copy and replace 1st field 856$u to 856$u using RegEx s/^http?s://example\.com/https://proxy.cca.edu/?url=https://example.com/ 2) Copy and replace field 856$u to 856$u using RegEx s/^http?s://example\.com/https://proxy.cca.edu/?url=https://example.com/ if 856$u matches RegEx m/https?://example\.com.*/ Original record: 245 _ _ ‡aTest record for MARC modification 856 4 0 ‡uhttps://example.com‡yProxy link 856 4 0 ‡uhttps://cca.edu‡yRetain link Expected outcome: 245 _ _ ‡aTest record for MARC modification 856 4 0 ‡uhttps://proxy.cca.edu/?url=https://example.com‡yProxy link 856 4 0 ‡uhttps://cca.edu‡yRetain link Actual outcome: 245 _ _ ‡aTest record for MARC modification 856 4 0 ‡uhttps://proxy.cca.edu/?url=https://example.com‡yProxy link 856 4 0 ‡uhttps://proxy.cca.edu/?url=https://example.com‡yRetain link Note that the second field's ‡y subfield is untouched. For template #1, I expect the second field not to be modified because it specifies only the "1st" MARC field. For template #2, I expect the second field not to be modified because it does not match the if condition. In BOTH templates, the regex substitution should not affect the second field, because it does not match the pattern. There was a thread on the Koha listserv between myself and Caroline Cyr La Rose from August 4th to August 9th, 2023 that may provide helpful details. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 35005] New: Add subscription and order count to new batch record deletion tool
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35005 Bug ID: 35005 Summary: Add subscription and order count to new batch record deletion tool Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org The batch record deletion tool checks for items, holds and checkouts. It would be a nice enhancement to also show linked subscriptions and orders. This would then match the checks done in acquisitions in order to be able to delete the record when cancelling an order line. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 35390] New: Display all types of sites associated with orders in acqui/lateorders.pl and acqui/histsearch.pl
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35390 Bug ID: 35390 Summary: Display all types of sites associated with orders in acqui/lateorders.pl and acqui/histsearch.pl Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org In acqui/lateorders.pl and acqui/histsearch.pl we should be able to display (or hide if not needed...) : - BASKET Delivery place - BASKET Billing place - BASKET GROUP Delivery place - BASKET GROUP Billing place - BASKET Managing library and - BASKET Managed by I cannot test on master, but this is not the case in 22.11 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 40967] New: Editing circulation and fine rules causes the Hard Due Date to be removed
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40967 Bug ID: 40967 Summary: Editing circulation and fine rules causes the Hard Due Date to be removed Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: drigney(a)esilibrary.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com When editing a Circulation rule that contains a hard due date, the hard due date is removed upon saving unless the user re-enters or re-selects the Hard Due Date field before clicking the Save button. Steps to Reproduce: 1) Go to Administration > Circulation and Fine Rules 2) Locate an existing circulation rule that has a Hard Due Date configured 3) Click "Edit" on that rule 4) Modify any field in the rule (e.g., loan period, renewals allowed, fine amount) WITHOUT touching the Hard Due Date field 5) Click "Save" 6) Observe the saved rule The Hard Due Date should remain intact and unchanged when editing other fields in the circulation rule. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 34965] New: Authority match failing due to possible encoding conflicts
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34965 Bug ID: 34965 Summary: Authority match failing due to possible encoding conflicts Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: esther.melander(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Created attachment 156415 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=156415&action=e… Example authority In this scenario, the authority record was prepared by Marcive with MARC 8, however the record itself shows that it is UTF-8 in the leader. To recreate: 1. Ensure there is a record match rule: Authority 010$a Match threshold: 1000 Record Type: Authority Add Match Point Search index: LC-cardnumber Score: 1000 Tag: 010 Subfields: a Offset: 0 Length: 0 Normalization rule: None Add Match Check Incoming record check Tag: blank Subfields: blank Offset: 0 Length: 0 Normalization rule: None 2. Stage and import the authority. Record type: Authority Encoding: UTF-8 (Default) Do not look for matching records The record will import correctly. Check the leader and see that the encoding is UTF-8 (UCS/Unicode). 3. Stage and import the authority again, but look for matching records. Record type: Authority Encoding: UTF-8 (Default) Record matching rule Authority 010$a Replace the existing record with incoming Notice the file will not stage, or in other words fail. 4. Delete the example authority from the system. 5. Stage and Import the authority but select MARC 8 for the encoding, no matching. See that it successfully imports. The encoding in the leader still says UTF-8 (UCS/Unicode). 6. Stage and Import the authority using MARC 8 encoding, Authority 010$a matching rule to replace existing. See that the authority successfully stages, matches, and overlays the existing authority. It is possible there is something unique in the way the authority was prepared as a MARC 8. In other words, if it was prepared as a MARC 8, it should be imported as a MARC 8, regardless of the encoding in the leader. However, the authority did successfully import as a UTF-8 encoded file minus the matching rule. It should be possible to import and overlay the same authority as a UTF-8 encoded authority with a match rule. Other than the encoding statement in the leader, I can't see anything else unique about the authority. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 35456] New: The fine will not be displayed. And even if the expired book is not handed over, it will show as a checked out book.
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35456 Bug ID: 35456 Summary: The fine will not be displayed. And even if the expired book is not handed over, it will show as a checked out book. Change sponsored?: --- Product: Koha Version: 22.11 Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: csuranjith64(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When a patron takes a book and it is overdue, the fine will not be displayed. And even if the expired book is not handed over, it will show as a checked out book. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 33232] New: report on item types
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33232 Bug ID: 33232 Summary: report on item types Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: library(a)princeofpeaceabbey.org QA Contact: testopia(a)bugs.koha-community.org The report on item types seems to be stuck. The numbers do not change even though I have added more items. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 36011] New: 2FA authentication failure is incorrectly logged
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36011 Bug ID: 36011 Summary: 2FA authentication failure is incorrectly logged Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: ola.andersson(a)ltu.se QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org A user failing to sign in four times with a correct username/password but incorrect 2FA passcode will incorrectly yield four records in action_logs with AUTH SUCCESS -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 33073] New: sip_cli_emulator doesn't work and documentation is in error
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33073 Bug ID: 33073 Summary: sip_cli_emulator doesn't work and documentation is in error Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: bob-ewart(a)bobsown.com QA Contact: testopia(a)bugs.koha-community.org The documentation on SIP2 server setup gives an example of running the sip_cli_emulator: ./misc/sip_cli_emulator.pl -a 127.0.0.1 -p 6001 -su term1 -sp term1 \ -l CPL --patron 23529001000463 -m checkout --item 39999000001259 it responds with No such file or directory running: /usr/share/koha/bin/sip_cli_emulator.pl -a 127.0.0.1 -p 6001 -l SLA -su <loginID> -sp <login password> --patron <myID> --password <my password> -m patron_information it responds with Can't locate C4/SIP/Sip/Constants.pm running: perl -I /usr/share/koha/lib /usr/share/koha/bin//sip_cli_emulator.pl -a localhost ... it responds with: Attempting socket connection to localhost:6001...connected! Use of uninitialized value $hold_mode in string eq at /usr/share/koha/bin//sip_cli_emulator.pl line 122. SEND: 9300CNSLAAdmin_sip2|COst0newall1972|CPSLA| READ: 940 Login Failed! That user/password is in SIPconfiguration.xml. It's category is Staff and has permissions: Check out and check in items Staff access Place and modify holds for patrons Manage patrons fines and fees Manage the electronic resources module I can log in with that ID and password -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6