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

[Bug 38873] New: Update MARC21 default framework to Update 39 (December 2024)
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38873 Bug ID: 38873 Summary: Update MARC21 default framework to Update 39 (December 2024) Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org https://www.loc.gov/marc/bibliographic/bdapndxg.html UPDATE 39 CHANGES ■ New content designators: Subfields $0 Authority record control number or standard number (R) in 506 (Restrictions on Access Note) $0 Authority record control number or standard number (R) in 540 (Terms Governing Use and Reproduction Note) $1 Real World Object URI (R) in 506 (Restrictions on Access Note) $1 Real World Object URI (R) in 540 (Terms Governing Use and Reproduction Note) ■ Changes in content designator names and definitions: Fields $f Use and reproduction rights renamed Standardized terminology for use and reproduction rights in 540 (Terms Governing Use and Reproduction Note) ■ Fast-track changes: New subfields $3 Materials specified (NR) in 508 (Creation/Production Credits Note) $3 Materials specified (NR) in 511 (Participant or Performer Note) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 38760] New: koha-mysql doesn't work with encrypted database connection
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38760 Bug ID: 38760 Summary: koha-mysql doesn't work with encrypted database connection Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: cornelius.amzar(a)bsz-bw.de, markus.john(a)bsz-bw.de, robin(a)catalyst.net.nz We noticed that the koha-mysql command doesn't send the right parameters when using an encrypted database connection. We are using the solution as outlined in bug 36026. If you add a warn to see the connection command as created by koha-mysql, you will see something like: mysql --host=<host> --user=XXX --password=XXX koha_XXX The parameters required for the encrypted connection (--ssl and --ssl-ca) are missing/unsupported. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 26

[Bug 39543] New: Error modal when trying to add two controlling licences to an agreement duplicates error message
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39543 Bug ID: 39543 Summary: Error modal when trying to add two controlling licences to an agreement duplicates error message Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ERM Assignee: jonathan.druart(a)gmail.com Reporter: andrew.auld(a)openfifth.co.uk 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 Created attachment 180488 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=180488&action=e… Screenshot of error modal If you try to add two licences with the status 'controlling' to an agreement record, the error modal duplicates the error message 'Only one controlling license is allowed'. -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 39717] New: Stock rotation stages cannot be moved
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39717 Bug ID: 39717 Summary: Stock rotation stages cannot be moved Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org In the routine Koha::StockRotationStage->move_to we are doing a stringwise comparison of the position to move to, versus the count of stages This works when we have a limited number of stages, but fails when we have many: perl -e 'warn "Yes" if "3" le "26"' It's not. Changing to <= seems to fix this -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 39447] New: Update mailmap for company name change
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39447 Bug ID: 39447 Summary: Update mailmap for company name change Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Developer documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org A well known company operating in the Koha space is changing their name ;) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 39226] New: [WARN] DBIx::Class::Storage::DBI::insert(): Missing value for primary key column 'borrowernumber' on BorrowerModification
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39226 Bug ID: 39226 Summary: [WARN] DBIx::Class::Storage::DBI::insert(): Missing value for primary key column 'borrowernumber' on BorrowerModification Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Seeing this one in 23.11. Not seen before in 22.11. [2025/02/28 10:20:09] [WARN] DBIx::Class::Storage::DBI::insert(): Missing value for primary key column 'borrowernumber' on BorrowerModification - perhaps you forgot to set its 'is_auto_increment' attribute during add_columns()? Treating 'borrowernumber' implicitly as an autoinc, and attempting value retrieval at /usr/share/koha/Koha/Object.pm line 172 Coming from opac-memberentry.pl when storing Koha::Patron::Modification in the create step. Probably adding a borrowernumber 0 in the hash should be enough to get rid of this probably innocent warning? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 27

[Bug 33284] New: checkout_renewals table retains checkout history in violation of patron privacy
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33284 Bug ID: 33284 Summary: checkout_renewals table retains checkout history in violation of patron privacy Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrewfh(a)dubcolib.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Depends on: 30275 The checkout_renewals table introduced in bug 30275 can retain a link between a patron and an issue_id when the patron's privacy is set to Never. That data should be anonymized. To recreate: - have a patron with their privacy set to Never retain reading history - check an item out to the patron, renew it via the OPAC - confirm your patron's borrowernumber can be found in checkout_renewals.renewer_id and the issue_id for your checkout can be found in checkout_renewals.checkout_id - check your item in - confirm your patron's borrowernumber has been removed from old_issues.borrowernumber - confirm your patron's borrowernumber and the issue_id for your checkout can still be found in checkout_renewals.checkout_id (along with a note that the renewal happened via the OPAC, thereby making it perfectly clear that this was a patron renewing the item they had checked out themselves). Should we not replace checkout_renewals.renewer_id with the anonymous patron's borrowernumber when the item is returned, if the patron is set to not retain reading history? Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30275 [Bug 30275] Checkout renewals should be stored in their own table -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 56

[Bug 39525] New: Relabel "Hold pickup library match" as "Hold and booking pickup library match"
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39525 Bug ID: 39525 Summary: Relabel "Hold pickup library match" as "Hold and booking pickup library match" Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: System Administration 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 This circ rule value covers both holds and bookings, but the label change got missed. I know "Booking and hold" would be alphabetical order, but I feel like keeping Holds first in the label makes sense as it's the more widely used function. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 39604] New: Remember for the session for this patron doesn't remember to cancel a hold
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39604 Bug ID: 39604 Summary: Remember for the session for this patron doesn't remember to cancel a hold Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com TO recreate: 1. Put a few items on hold and make note of the barcodes. 2. Check out one of the items to a patron who doesn't have the hold 3. Check the cancel hold radio button 4. Also check the Remember for the session for this patron 5. Click 'Yes, check out' 6. Notice the item is checked out and the hold is cancelled 7. No checkout another on hold item to the same patron 8. No confirm screen ( good ) 9. The item is checked out ( good ) 10. The hold is not cancelled. ( bad ) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 18

[Bug 39500] New: Subfield 111 $n is badly displayed in OPAC
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39500 Bug ID: 39500 Summary: Subfield 111 $n is badly displayed in OPAC Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: OPAC Assignee: januszop(a)gmail.com Reporter: januszop(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 180048 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=180048&action=e… A screenshot illustrating the problem If the main heading is 111 and id contains subfield $n, the content of this subfield is badly displayed in OPAC: at the beginning of the heading text (right after "By:"), and then correctly, as the part of the link. -- You are receiving this mail because: You are watching all bug changes.

1 12