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

[Bug 37392] New: Edit item permission by library group is broken
by bugzilla-daemon＠bugs.koha-community.org 16 Jan '26

16 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37392 Bug ID: 37392 Summary: Edit item permission by library group is broken Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: kyle(a)bywatersolutions.com, m.de.rooy(a)rijksmuseum.nl, martin.renvoize(a)ptfs-europe.com, tomascohen(a)gmail.com Depends on: 29523 The library groups allow to set up library groups within the staff users can edit each others items. This was introduced in 23.05, but is now broken in 23.11. It's not possible for a staff user to edit another libraries items now in some circumstances. Test plan: Set up library group: * Create a library group for library A + B * Action: Limit item editing by group Set up test user: * Create a staff patron with these permissions: * catalogue * fast_cataloguing * edit_items * view_borrower_infos_from_any_libraries * edit borrowers * Home library: library A Set up test items: * Create a record with 3 items with different home libraries: * A * B * C We expect the user will be allowed to edit A and B, but not C. Test: * Test editing the items with the test user, only A is allowed to be edited. * Remove the view_borrower_infos_from_any_libraries permission from test user. * Test editing items now behaves as expected: A + B are allowed, C is not. ----- After some digging to understand the change of behavior noticed between 23.05 and 23.11: I believe commit 2c502d32 to be the culprit. item.can_be_edit uses Patron::can_edit_item_from which calls can_see_things_from. The commit removed the library group specific code and introduced a call to libraries_where_can_see_patrons instead, probably assuming the thing was always a patron record. But here it is an item record. Thinking we should not use "thing" in method names without at least explaining what thing can be... Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29523 [Bug 29523] Add a way to prevent embedding objects that should not be allowed -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 99

[Bug 39095] New: Clicking Cancel on opac-user for article requests does not respond
by bugzilla-daemon＠bugs.koha-community.org 16 Jan '26

16 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39095 Bug ID: 39095 Summary: Clicking Cancel on opac-user for article requests does not respond Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org Seeing this under 22.11 and 23.11. Master looks the same btw. The last column is dtr controlled. You must expand. At that moment the button Cancel appears under the table. Clicking Cancel does not trigger the click event? -- You are receiving this mail because: You are watching all bug changes.

1 20

[Bug 39462] New: (bug 37870 follow-up) Default values from framework are inserted into existing record while editing
by bugzilla-daemon＠bugs.koha-community.org 16 Jan '26

16 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39462 Bug ID: 39462 Summary: (bug 37870 follow-up) Default values from framework are inserted into existing record while editing Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: januszop(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: jonathan.druart(a)gmail.com, m.de.rooy(a)rijksmuseum.nl Depends on: 37870 Due to changes made by the commit 0472b56a671, when editing an existing bibliographic record a default value is inserted while it should not, according to ApplyFrameworkDefaults systempreference. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37870 [Bug 37870] UI/Form/Builder/Item.t and Biblio.t are still failing randomly (cn_source sort) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 39304] New: Jenkins not failing when git command fails
by bugzilla-daemon＠bugs.koha-community.org 16 Jan '26

16 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39304 Bug ID: 39304 Summary: Jenkins not failing when git command fails Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Test Suite Assignee: jonathan.druart(a)gmail.com Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org We edited the config and it broke the git repo: 13:32:35 koha_1 | error: unable to normalize alternate object path: /srv/jenkins/workspace/Koha_Source/.git/objects 13:32:35 koha_1 | fatal: not a tree object 13:32:35 koha_1 | [12:29:31] xt/check_makefile.t So tests were not running correctly -- You are receiving this mail because: You are watching all bug changes.

1 16

[Bug 39750] New: Wrong transfer breaking check in when using branch transfer limits
by bugzilla-daemon＠bugs.koha-community.org 16 Jan '26

16 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39750 Bug ID: 39750 Summary: Wrong transfer breaking check in when using branch transfer limits Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(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 - Enable UseBranchTransferLimits based on 'Collection code' 2 - Disable transfers for FIC from: CPL -> FFL CPL -> IPT FFL -> CPL FFL -> IPT IPT -> CPL IPT -> FFL 3 - Set library to IPT 4 - Checkin an FFL item 5 - It generates a transfer home 6 - Set library to CPL 7 - Check the item in 8 - 500 error, and in logs: ==> /var/log/koha/kohadev/plack-error.log <== Exception 'Koha::Exceptions::Item::Transfer::Limit' thrown 'Transfer not allowed' -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 40057] New: Database update 24.12.00.017 fails if old ILL data points to non-existent borrowernumber
by bugzilla-daemon＠bugs.koha-community.org 16 Jan '26

16 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40057 Bug ID: 40057 Summary: Database update 24.12.00.017 fails if old ILL data points to non-existent borrowernumber Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: pedro.amorim(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: pedro.amorim(a)openfifth.co.uk, tomascohen(a)gmail.com -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 29

[Bug 38203] New: Split the purpose of RENEWAL and AUTO_RENEWALS_DGST notices.
by bugzilla-daemon＠bugs.koha-community.org 16 Jan '26

16 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38203 Bug ID: 38203 Summary: Split the purpose of RENEWAL and AUTO_RENEWALS_DGST notices. Change sponsored?: --- Product: Koha Version: Main 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 As bug 29382 points out RENEWAL is sent in parallel with AUTO_RENEWALS_DGST when the autorenewals script runs providing message preferences are set (and RenewalSendNotice is enabled… not mentioned in that bug). We recently enabled AllowRenewalLimitOverride and I configured RENEWAL to use TT code to send appropriately worded notices for renewals of interlibrary loans, notforloan items issued, and for other loan items manually renewed. My (wrong) expectation was that the DGST notice would go out from 01:30 when our autorenewals script runs, and the RENEWAL would go out only and whenever an item was manually renewed. If auto-renewal is enabled then we are wasting useful functionality that could use RENEWAL to notify of (perhaps special cases of) manual renewal if the purpose of the two notices were separated. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 39014] New: Storing a guarantee fails due to TrackLastPatronActivityTriggers "creating a patron"
by bugzilla-daemon＠bugs.koha-community.org 16 Jan '26

16 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39014 Bug ID: 39014 Summary: Storing a guarantee fails due to TrackLastPatronActivityTriggers "creating a patron" Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: lmstrand(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Adding a new guarantee and storing it fails with "Creating a patron" selected in TrackLastPatronActivityTriggers when guarantors are set to be mandatory. Feature was added in ticket 23486. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 73

[Bug 40980] New: Clicking a search facet without logging in may trigger a cud-login error
by bugzilla-daemon＠bugs.koha-community.org 16 Jan '26

16 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40980 Bug ID: 40980 Summary: Clicking a search facet without logging in may trigger a cud-login error Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: pedro.amorim(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 22

[Bug 41408] New: POS Inline Editing Triggers Form Submission on Enter Key
by bugzilla-daemon＠bugs.koha-community.org 16 Jan '26

16 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41408 Bug ID: 41408 Summary: POS Inline Editing Triggers Form Submission on Enter Key Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Point of Sale Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: martin.renvoize(a)openfifth.co.uk On the Point of Sale (POS) page, when editing the cost of an item using inline table editing (clicking to edit the price), pressing Enter to accept the new price inadvertently submits the entire payment form instead of just accepting the inline edit. Steps to Reproduce 1. Navigate to the Point of Sale page (pos/pay.pl) 2. Add an item to "This sale" table using the '+Add' button from the left table 3. Click on the "Cost" cell to edit the price inline 4. Change the value 5. Press Enter to accept the new price Expected Behavior - The Enter key should accept the inline edit and update the cell value - The form should NOT be submitted - User should be able to continue editing other fields or adding more items Actual Behavior - The Enter key accepts the inline edit BUT also triggers the form submission - The payment form is submitted prematurely - User cannot continue with the transaction setup -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14