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

[Bug 26853] New: "Data too long for column" errors during MARC import
by bugzilla-daemon＠bugs.koha-community.org 21 May '26

21 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26853 Bug ID: 26853 Summary: "Data too long for column" errors during MARC import Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: MARC Bibliographic record staging/import Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org I'm noticing "Data too long for column 'title'" and "Data too long for column 'issn'" database errors in the logs. These are preventing import_biblios rows from being added to the system, although import_records rows are still being added. On koha-testing-docker, these errors are being silently ignored, which is not good. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 27

[Bug 28411] New: Investigate memory footprint of the different dependencies
by bugzilla-daemon＠bugs.koha-community.org 21 May '26

21 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28411 Bug ID: 28411 Summary: Investigate memory footprint of the different dependencies Change sponsored?: --- Product: Koha Version: master 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 Blocks: 28410 In order to know which modules is costing lot of RAM it would be great to have a list the modules with their memory impact. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28410 [Bug 28410] Reduce memory footprint -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 18

[Bug 35250] New: Eliminate circular dependencies caused by C4::Context
by bugzilla-daemon＠bugs.koha-community.org 21 May '26

21 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35250 Bug ID: 35250 Summary: Eliminate circular dependencies caused by C4::Context Change sponsored?: --- Product: Koha Version: master 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: philippe.blouin(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org Any script using C4::Context is bound to have a huge memory footprint because of the dependencies. And even script that would do without C4::Context (somehow) are bound for the same as soon as they include one Koha:: module, because those will use C4::Context. A graph from v23.05 will summarize it better than any explanation: BackgroundJobs | v BackgroundJob (Net::Stomp : 5M) | | | v | Koha::Object (Mojo::JSON : 16M) v C4::Context (DateTime::TimeZone : 7M) | | (ZOOM : 8M) v | Koha::Config::Syspref | | v | C4::Log (calling back on C4::Context) | | v | Koha::ActionLogs | | v | Koha::ActionLog (calling back on C4::Context) | | v | Koha::Object | | v Koha::Caches (calling back on C4::Context) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 23

[Bug 40873] New: AV dropdowns in OPAC don't use lib_opac values
by bugzilla-daemon＠bugs.koha-community.org 21 May '26

21 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40873 Bug ID: 40873 Summary: AV dropdowns in OPAC don't use lib_opac values Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: ephetteplace(a)cca.edu QA Contact: testopia(a)bugs.koha-community.org The OPAC version of av-build-dropbox.inc uses av.lib instead of av.lib_opac so even if your AV category has OPAC-friendly text it is not used. I discovered this specifically when using the SUGGEST_FORMAT item types for purchase suggestions. I created the category, added several values, gave them all a concise "lib" value and some a more explanatory "lib_opac" value. When I visited the OPAC's suggestions page /cgi-bin/koha/opac-suggestions.pl?op=add_form I saw the form only used the "lib" values. The code is in koha-tmpl/opac-tmpl/bootstrap/en/includes/av-build-dropbox.inc I suspect many patron-facing AVs don't have lib_opac values because they're not used anywhere, so changing the dropbox code to use lib_opac could have negative side effects for many existing instances. Would it make sense to check if an AV has lib_opac, use that, and default to lib if not available? This should make the transition seamless, unless libraries put inaccurate values in their lib_opac which they wouldn't notice until now. -- You are receiving this mail because: You are watching all bug changes.

1 19

[Bug 25952] New: Github search for plugin throwing errors for % and koha-plugin search terms
by bugzilla-daemon＠bugs.koha-community.org 21 May '26

21 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25952 Bug ID: 25952 Summary: Github search for plugin throwing errors for % and koha-plugin search terms Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Plugin architecture Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org I was trying to get a full list of the available plugins so I tried '%' and 'koha-plugin' as search terms, but they created errors in Koha. Note that the 'koha-plugin' query works directly: https://api.github.com/search/repositories?q=koha-plugin+user:thekesolution… -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 41

[Bug 40220] New: API Incorrectly Requires Mandatory Extended Attributes Not Visible in OPAC
by bugzilla-daemon＠bugs.koha-community.org 21 May '26

21 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40220 Bug ID: 40220 Summary: API Incorrectly Requires Mandatory Extended Attributes Not Visible in OPAC Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: REST API Assignee: leo.stoyanov(a)bywatersolutions.com Reporter: leo.stoyanov(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com When registering patrons via /api/v1/patrons, the endpoint requires ALL mandatory extended attributes, including those not set to "Editable in OPAC". This is inconsistent with OPAC behavior, where only attributes that are both mandatory and visible/editable in OPAC are required. For external systems acting as OPAC replacements, such as Aspen Discovery, this creates unnecessary validation failures. -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 40219] New: Welcome Email Sent on Failed Patron Registration via API
by bugzilla-daemon＠bugs.koha-community.org 21 May '26

21 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40219 Bug ID: 40219 Summary: Welcome Email Sent on Failed Patron Registration via API Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: REST API Assignee: leo.stoyanov(a)bywatersolutions.com Reporter: leo.stoyanov(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com When registering a new patron via the /api/v1/patrons API endpoint, a welcome email notice is sent even if the endpoint returns a 400 error due to validation failures. This occurs because the welcome email logic executes before extended attribute validation is complete, within the database transaction. -- You are receiving this mail because: You are watching all bug changes.

1 27

[Bug 40803] New: Users cannot renew overdue items from 'Overdue' tab in account
by bugzilla-daemon＠bugs.koha-community.org 21 May '26

21 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40803 Bug ID: 40803 Summary: Users cannot renew overdue items from 'Overdue' tab in account Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Looks like this was missed in the CSRF update -- You are receiving this mail because: You are watching all bug changes.

1 21

[Bug 39468] New: EDI message status should be case insensitive
by bugzilla-daemon＠bugs.koha-community.org 21 May '26

21 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39468 Bug ID: 39468 Summary: EDI message status should be case insensitive Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: glasklas(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org There already was a bug (Bug 32676) that should have addressed this. The initial commit looks ok, but the final one, which seems be the one that have been pushed is missing the .lower on edi_order.status. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 39985] New: items.onloan field is not updated when an item is recalled
by bugzilla-daemon＠bugs.koha-community.org 21 May '26

21 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39985 Bug ID: 39985 Summary: items.onloan field is not updated when an item is recalled Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: emily.lamancusa(a)montgomerycountymd.gov QA Contact: testopia(a)bugs.koha-community.org Depends on: 19532 When an item is recalled, if the due date on the item should be updated due to the recall, only the issues.date_due field gets updated. The due date stored in items.onloan remains unchanged. To replicate: 1. Enable UseRecalls syspref and set corresponding circulation rules: - Recalls allowed - Recalls per record - On shelf recalls allowed - set to "If any unavailable" - Recall due date interval - set to 1 - Recall pickup period 2. Check out an item to a patron 3. Log into the OPAC as another patron 4. Search for the item checked out in step 2 5. Place a recall on that item 6. Search for that item in the staff interface => Note that the item status says, "Checked out to <patron>: due <tomorrow>" 7. Create the following SQL report in the reports module, using the barcode of the item that was recalled: SELECT onloan FROM items WHERE barcode='xxxxxxxxx' 8. Run the report => The onloan value is still set to the item's original due date, not the update due date of tomorrow Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19532 [Bug 19532] Recalls for Koha -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15