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

[Bug 39361] New: Hold found modal does not display from circ/branchtransfers.pl
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '26

26 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39361 Bug ID: 39361 Summary: Hold found modal does not display from circ/branchtransfers.pl 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. Find or create an item with a hold on it. 2. Go to Circulation > Transfers 3. Transfer the item from step 1. 4. No modal appears to warn that the item has a hold. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21

[Bug 38921] New: Remove unused href from Cancel hold link
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '26

26 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38921 Bug ID: 38921 Summary: Remove unused href from Cancel hold link Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: phil(a)chetcolibrary.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 34478 We use koha-tmpl/intranet-tmpl/prog/en/includes/holds_table.inc to display the list of existing holds in reserve/request.pl when you are placing a hold. The cancel button-links are JavaScript-only, showing a confirm modal and then POSTing a form from there, since the op is cud-cancel and has to be a POST. But we left behind a pre-CSRF href attribute which is a double false-positive for me, since it has both op=cancel and uses the Template Toolkit html filter rather than the uri filter for things inserted in a URL parameter. You can see that it doesn't do anything by right-clicking and opening it in a new tab - there's no op named cancel, so it just displays the existing holds and lets you add one, repeating the page you opened the link from, only with garbage after the request.pl? in your URL. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34478 [Bug 34478] Full CSRF protection -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 12450] Easily close a branch
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '26

26 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12450 --- Comment #17 from Danielle M. <dmeininger591(a)gmail.com> --- I like Christopher's idea of being able to pick and choose which features I want to shutdown when I close a particular branch. This kind of "checklist" would also help spur questions for libraries as they navigate sometimes sudden closures. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 12450] Easily close a branch
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '26

26 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12450 Danielle M. <dmeininger591(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dmeininger591(a)gmail.com -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 20965] New: Batch patron anonymization logic is flawed
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '26

26 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20965 Bug ID: 20965 Summary: Batch patron anonymization logic is flawed Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org There are two issues here: 1) The tool suggests you can limit by library and checkout date but in fact, the library is not the patrons' library but the library the items were issued at. This is not clear from the UI. 2) When it comes to the actual anonymisation, although we've got a filtered list of Patrons by issues before X and at Library, we then delete ALL issues before X by any of the Patrons selected by the previous query, regardless of which library the checkout took place and thus we ignore the selected Library. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 41947] New: Log runs of cleanborrowers.pl with the parameters
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '26

26 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41947 Bug ID: 41947 Summary: Log runs of cleanborrowers.pl with the parameters Initiative type: --- Sponsorship --- status: Product: Koha Version: Main 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: lisette(a)bywatersolutions.com 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 1

[Bug 41935] New: Patron attribute overflows the boundaries of the aside panel in borrower pages
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '26

26 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41935 Bug ID: 41935 Summary: Patron attribute overflows the boundaries of the aside panel in borrower pages Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com If a borrower attribute is too long, it will flow out of bounds on the side (aside) panel in all of the borrower pages (i.e. circulation.pl). Some rules need to be put in place to keep this information properly contained. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 39856] New: New Option for Default lost item fee refund on return policy: Refund if unpaid and charge new overdue
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '26

26 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39856 Bug ID: 39856 Summary: New Option for Default lost item fee refund on return policy: Refund if unpaid and charge new overdue Change sponsored?: --- Product: Koha Version: 24.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: trevor.diamond(a)mainlib.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The Default lost item fee refund on return policy has an option to only refund the replacement cost if unpaid, but this does nothing regarding the overdue. Similar to the "always refund" or "never refund" options, there needs to be an option for Refund replacement cost (if unpaid) and charge new overdue In theory there should be a corollary "restore overdue" but this would not be used in our consortium and I don't want this bug to be discarded as "too hard" in case adding that option overcomplicates things. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 37512] New: Add a function to reset login attempts
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '26

26 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37512 Bug ID: 37512 Summary: Add a function to reset login attempts 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: baptiste.wojtkowski(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When a user tries to much login attempts, they are blocked. There are two ways to unlock the user: 1 - Change the database 2 - Reset the password There is currently no option to simply remove the lock for a blocked account. In BZ 25947 (https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25947) we added a button to reset the password and another to simply reset the loginattempts. This bug has been created to split the two improvements. This bugs containts the improvements related to the button to reset loginattempts -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 50

[Bug 39625] New: Interface logs incorrectly to statistics table when renewing
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '26

26 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39625 Bug ID: 39625 Summary: Interface logs incorrectly to statistics table when renewing Change sponsored?: --- Product: Koha Version: 24.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: anneli.osterman(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com We have a problem that interface logs incorrectly to statistics when renewing. It seems to log a random interface (intranet, opac, api, sip). Often renewal which is made in staff interface is logged as done via api. How to recreate: 1. Search for a patron with renewable checkouts 2. Renew one of patron's items by checkin it in Renew column and selecting then Renew selected items 3. Check the statistics table which interface is recorded SELECT * FROM statistics WHERE borrowernumber=xxx AND type='renew' ORDER BY 1 DESC 4. Repeat 2-3 few times I cannot recreate this problem in a sandbox but maybe that is because I'm there alone? We are currently using version 24.05.01 (with newer security updates). We found some bugs related to this one but they all were closed as fixed about two years ago so maybe this is something else? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13