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

[Bug 31314] New: Remove GetItemsInfo from opac-reserve.pl
by bugzilla-daemon＠bugs.koha-community.org 29 Jun '26

29 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31314 Bug ID: 31314 Summary: Remove GetItemsInfo from opac-reserve.pl 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: 31306 Blocks: 27272 Bug 27272 is going to remove C4::Items::GetItemsInfo in favour of Koha::Items->search_ordered. Here we are going to deal with opac-reserve.pl Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27272 [Bug 27272] Move C4::Items::GetItemsInfo to Koha namespace https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31306 [Bug 31306] Add Koha::Items->search_ordered method -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 25

[Bug 36957] New: Item in transfer should start floating in its floating library without user clicking the "Cancel transfer"-button
by bugzilla-daemon＠bugs.koha-community.org 29 Jun '26

29 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36957 Bug ID: 36957 Summary: Item in transfer should start floating in its floating library without user clicking the "Cancel transfer"-button Change sponsored?: --- Product: Koha Version: 23.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: piia.semenoff(a)ouka.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When item is in transfer and it is checked in in a library where it could float, a notification/pop-up about transport will appear on the screen. User must end the transfer by clicking “Cancel transfer”-button. Only then will the item end the transport and start floating in the holding library. Even if the item is in transfer somewhere else (and there are no holds waiting) and it is checked in in a floating library, it should not give the pop-up: “Wrong transfer detected, please return item to…” . Instead it should just start floating without having to click the canceling-button. Koha asks for transfer cancelation even if we have saved in the AutomaticItemReturn-preference “Don’t automatically transfer items to their home library when they are checked in.” -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 10

[Bug 42869] New: Add REST API coding guideline for async job endpoints (202 Accepted)
by bugzilla-daemon＠bugs.koha-community.org 29 Jun '26

29 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42869 Bug ID: 42869 Summary: Add REST API coding guideline for async job endpoints (202 Accepted) Initiative type: --- Sponsorship --- status: 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: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com Target Milestone: --- Koha currently has several REST API endpoints that enqueue background jobs and return a job_id. These endpoints incorrectly use HTTP 201 Created, which implies a resource was durably created and is immediately addressable. Per HTTP semantics, endpoints that accept a request for asynchronous processing should return 202 Accepted with a Location header pointing to the job tracking endpoint (/api/v1/jobs/{job_id}). Affected endpoints: - POST /api/v1/erm/eholdings/local/titles/import_from_list (returns 201) - POST /api/v1/erm/eholdings/local/titles/import_from_kbart_file (returns 201) - POST /api/v1/cover_images/batch (fixed in bug 42404) This bug tracks: 1. Adding REST3.2.1.2 to the coding guidelines wiki 2. Updating existing endpoints to comply See also: Bug 42404 Wiki page: https://wiki.koha-community.org/wiki/Coding_Guidelines_-_API#REST3.4.1_POST -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 39058] New: Top and left menu should have a fixed position
by bugzilla-daemon＠bugs.koha-community.org 29 Jun '26

29 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39058 Bug ID: 39058 Summary: Top and left menu should have a fixed position Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com It would improve Koha usabilty - to always display the top elements (navbar, header_search, maybe sub-header) even if the user scroll down the page - to always display the left menu, and to make it collapsible if the user choose to -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21

[Bug 42087] New: Add dependency File::LibMagic for validating file using magic numbers
by bugzilla-daemon＠bugs.koha-community.org 29 Jun '26

29 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42087 Bug ID: 42087 Summary: Add dependency File::LibMagic for validating file using magic numbers Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: mtj(a)kohaaloha.com There are many cases in Koha where we're working with files and we want to know what type of file it is, but we can't trust the file extension or the Content-Type that it's uploaded with, because those are user-controlled data. A common method for testing file type is using magic numbers via the libmagic library. In Perl File::LibMagic provides Perl bindings to this C library, which makes it easy to check what kind of file we're working with (to a reasonable degree). libfile-libmagic-perl is available in Debian, so it should be an easy dependency to add. It will help improve our security and even just user experience. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22

[Bug 42925] New: Replace the 'clear' button with an icon inside the search box (global search for tables)
by bugzilla-daemon＠bugs.koha-community.org 28 Jun '26

28 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42925 Bug ID: 42925 Summary: Replace the 'clear' button with an icon inside the search box (global search for tables) Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: jonathan.druart(a)gmail.com Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Target Milestone: --- On Chrome there is a builtin 'x' in the search box. The "Clear filter" button is then not needed. However it does not exist for Firefox. We could disable the builtin feature in Chrome add our own, so all browsers have it. Then the "Clear filter" button will no longer be needed. -- You are receiving this mail because: You are watching all bug changes.

1 9

[Bug 30614] New: check-url-quick gives false error 404
by bugzilla-daemon＠bugs.koha-community.org 28 Jun '26

28 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30614 Bug ID: 30614 Summary: check-url-quick gives false error 404 Change sponsored?: --- Product: Koha Version: 20.05 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: marjorie.barry-vila(a)collecto.ca QA Contact: testopia(a)bugs.koha-community.org Hi, Many 404 errors come out after running the check-quick-url script while the urls are correct when checked manually. Apparently this is because the script uses HTTP HEAD instead of HTTP GET. HTTP HEAD returns only the headers of the urls and the header can return an error but the url is accessible when you do a GET. Is there a reason for this? My fellow analyst was pointing to line 104 of https://github.com/Koha-Community/Koha/blob/master/misc/cronjobs/check-url-… Thank you Marjorie -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 25

[Bug 40911] New: SIP Patron->new() generates ORM warnings with undefined/empty patron_id
by bugzilla-daemon＠bugs.koha-community.org 28 Jun '26

28 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40911 Bug ID: 40911 Summary: SIP Patron->new() generates ORM warnings with undefined/empty patron_id Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Noticed in production, when C4::SIP::ILS::Patron->new is passed a $patron_id that is not defined or empty -or any processing makes it like that- (e.g. faulty plugins, malformed SIP requests) logs get flooded with DBIx::Class errors and Perl warnings when it should never reach the ORM with a query because there's nothing to search for. Similar to bug 40910 for Item->new(), the Patron constructor should validate input early and return gracefully without generating warnings for undefined/empty patron identifiers. Expected behavior: Silent return for invalid input, proper debug logging for troubleshooting Actual behavior: Warning spam in SIP server logs, potential DBIx::Class constraint errors This affects SIP server stability and makes log analysis difficult due to noise from invalid requests. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 41707] New: The DIE handler in C4::SIP::Trapper is logging non-SIP errors, causing log flooding.
by bugzilla-daemon＠bugs.koha-community.org 28 Jun '26

28 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41707 Bug ID: 41707 Summary: The DIE handler in C4::SIP::Trapper is logging non-SIP errors, causing log flooding. Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: johanna.raisa(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org The DIE handler should be more restrictive and only log errors where the call stack clearly originates from SIP modules (e.g., C4::SIP::*). The current implementation is not strict enough or may have edge cases. Found this kind of errors from our logs: [2026/01/23 13:42:47] [493898] [ERROR] [undef]@[undef]: commandline was not set during initialization at /usr/share/perl5/Net/Server.pm line 100. C4::SIP::Trapper::__ANON__ /home/koha/Koha/C4/SIP/Trapper.pm (70) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 32092] New: Improve circulation rules cache utilization
by bugzilla-daemon＠bugs.koha-community.org 28 Jun '26

28 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32092 Bug ID: 32092 Summary: Improve circulation rules cache utilization 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: glasklas(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Currently the cache is bypassed when fetching of circulation rules in a lot of places, calling get_effective_rule instead of get_effective_rule_value which makes use of in-memory cached. Additionally the case where the rule value is an empty string or undefined or no rule is found are not currently cached which results in the database is being queried repeatedly for cases where no results are found (which usually are the majority of calls). For example on the page where items are listed when placing a hold the current hit ratio for the cache in get_effective_rule_value is about 6%, with this patch we instead get a hit ratio of 99.8%, resulting in a whooping 340x less time spent performing the database lookup in get_effective_rule_value. With 150 items (we have serials with up to 1400 items), about 50% of the execution time is spent looking up rules which is practically reduced to zero when also caching empty results (and replacing the uncached direct calls to get_effective_rule with get_effective_rule_value). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 52