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

[Bug 19060] New: Patrons should not get a max fines block auto-renewal notification for items due in the future.
by bugzilla-daemon＠bugs.koha-community.org 13 Feb '26

13 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19060 Bug ID: 19060 Summary: Patrons should not get a max fines block auto-renewal notification for items due in the future. Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: r.delahunty(a)arts.ac.uk QA Contact: testopia(a)bugs.koha-community.org This appears related to 19014. Current functionality in 17.05: Auto-renewal is enabled for specific user and item type combinations. This user has fines in excess of that specified in OPACFineNoRenewalBlockAutoRenewal This user has an item due today, and others due at various times in the future, some many weeks ahead. When the auto-renewal job runs today, Koha is sending an AUTO_RENEWAL email to this user for each of the items on loan, warning that each has failed automatic renewal. Desired functionality in 17.05: When the auto-renewal job runs, Koha should only send an AUTO_RENEWAL failure email to the user for item(s) due for automatic renewal today. Other items are still validly on loan and are not due for renewal. The user is being contacted multiple times unnecessarily and this can be confusing. Ray Delahunty University of the Arts London -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 37097] New: koha is not responding due to lack of free disk space (zebra tmp suddenly grows)
by bugzilla-daemon＠bugs.koha-community.org 13 Feb '26

13 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37097 Bug ID: 37097 Summary: koha is not responding due to lack of free disk space (zebra tmp suddenly grows) Change sponsored?: --- Product: Koha Version: 23.05 Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Searching - Zebra Assignee: koha-bugs(a)lists.koha-community.org Reporter: yuriy.kotsyuk(a)oa.edu.ua Periodically we have a problem with free space on our koha server on Ubuntu 20.04.6. The total disk capacity is 210 GB (koha usually takes 105 GB), but sometimes the number of files in /var/lib/koha/library/biblios/tmp suddenly grows and takes up all the free disk space. As a result, koha server starts working with errors and stops completely. I have come to the conclusion that this folder holds temporary zebra files. I just clear the tmp folder each time. After that, the koha wakes up. Is that an issue with a small disk, or is that an issue with periodical cleaning tmp folder? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 36724] New: Add cartographic mathematical data to Elasticsearch index mappings
by bugzilla-daemon＠bugs.koha-community.org 13 Feb '26

13 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36724 Bug ID: 36724 Summary: Add cartographic mathematical data to Elasticsearch index mappings Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz Search whole 255 field https://www.loc.gov/marc/bibliographic/bd255.html Test with values like * Scale 1:22,000,000 * Conic proj. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 22

[Bug 25193] New: Prevent renewal from other branches
by bugzilla-daemon＠bugs.koha-community.org 13 Feb '26

13 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25193 Bug ID: 25193 Summary: Prevent renewal from other branches Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Add a CanRenewFromOtherBranches system preference to manage borrowers renewing items at other branches. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 57

[Bug 24194] New: Add system preference to hide expiration date options for reserves
by bugzilla-daemon＠bugs.koha-community.org 13 Feb '26

13 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24194 Bug ID: 24194 Summary: Add system preference to hide expiration date options for reserves Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Some libraries do not need to set expiration dates for reserves (this functionality is used). Add the ability to hide these options when placing reserves in staff client and OPAC. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 141

[Bug 39296] New: Provide a template plugin to return MARC::Record for MARCXML metadata
by bugzilla-daemon＠bugs.koha-community.org 13 Feb '26

13 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39296 Bug ID: 39296 Summary: Provide a template plugin to return MARC::Record for MARCXML metadata Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org ExtractValue() is a useful MySQL function but it's limited in what it can do. Sometimes, you want to do reporting off a more nuanced understanding of MARC. I had thought about exposing XML::LibXML::Document and XML::LibXML::XPathContext objects, but they're too powerful/vulnerable to abuse. Instead, I decided that MARC::Record should give all the power we need while not upsetting the status quo or security (after all, we already allow access to MARC::Record objects via $biblio objects in Templates). In this case, you fetch the whole "metadata" blob from the database in your report, and you transform it using a template using Koha::Template::Plugin::KohaMarcRecord It lets you perform more advanced reporting using the full MARC record. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 19

[Bug 40791] New: Allow choice of which Overdue messages can be patron preferences
by bugzilla-daemon＠bugs.koha-community.org 13 Feb '26

13 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40791 Bug ID: 40791 Summary: Allow choice of which Overdue messages can be patron preferences Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: philip.orr(a)lmscloud.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com In Bug 30515, we are discussing adding a new system preference UsePatronPreferencesForOverdueNotices to let patrons control which overdue messages are sent by mail in their messaging preferences. For many libraries it would still be necessary to set a certain overdue notice (say the third overdue notice) as "mandatory for print message". Jonathan suggested to reuse the aforementioned pref and make it multivaluated with 3 values possible: ODUE, ODUE2, ODUE3. Then: - if at least one is selected then patrons can edit it/them - if none selected, we don't allow the patrons to modify any This would be the simplest way to extend the functionality of Bug 30515. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 30131] New: Centralize "marc preview" buttons and links
by bugzilla-daemon＠bugs.koha-community.org 13 Feb '26

13 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30131 Bug ID: 30131 Summary: Centralize "marc preview" buttons and links Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 29965 The code to display the "MARC preview" modal is copy/pasted all over our templates, we should centralize them to prevent to see more occurrences coming. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29965 [Bug 29965] MARC preview for authority search results -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 38983] New: Foreign key constraints are case insensitive so can lead to erroneous data input via the API
by bugzilla-daemon＠bugs.koha-community.org 13 Feb '26

13 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38983 Bug ID: 38983 Summary: Foreign key constraints are case insensitive so can lead to erroneous data input via the API Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com This one is fun... You can input randomly cases branchcodes via the API for patrons without receiving an error. This appears to be because sql's foreign key constraints aren't being triggered. This is fine in the database, but as soon as we start returning the data via API javascript is case sensitive in the UI and can crash To replicate, try adding a library with the code `CAPITALS` and then add a user via the API with a library_id of `Capitals`. If you then search for that user, the patron search table will fail to load and you'll get errors in the console. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 35471] New: Automatically select child MARC framework when adding child records
by bugzilla-daemon＠bugs.koha-community.org 13 Feb '26

13 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35471 Bug ID: 35471 Summary: Automatically select child MARC framework when adding child records Change sponsored?: --- 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: lari.taskula(a)hypernova.fi QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Some libraries create their own MARC frameworks for component/child records. When adding a child record through host record, Koha currently selects the default MARC framework and a librarian must manually change to the child record framework. This Bug adds a parent-child relationship to MARC frameworks and aims to skip the manual step of selecting child record framework. The goal is to automatically select child MARC framework when adding child record through the host record. To reproduce problem: Administration -> MARC bibliographic framework 1. Create framework with frameworkcode "A" 2. Create framework with frameworkcode "A-child" Record view 1. Save record with framework "A" 2. Navigate to a record 3. Click "+ New", a drop-down opens 4. Click "New child record" 5. After add biblio form opens, click "Settings" 6. Observe default framework selected 7. You must manually select "A-child framework" After this change, To test: Administration -> MARC bibliographic framework 1. Create framework with frameworkcode "A" 2. Create framework with frameworkcode "A-child" 3. Set "A" as "A-child" 's parent framework Record view 1. Save record with framework "A" 2. Navigate to a record 3. Click "+ New", a drop-down opens 4. Click "New child record" 5. After add biblio form opens, click "Settings" 6. Observe "A-child" framework automatically selected -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 54