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

[Bug 37826] New: Templates that use the variable script_name should be called by scripts that set it
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '26

26 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37826 Bug ID: 37826 Summary: Templates that use the variable script_name should be called by scripts that set it Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: phil(a)chetcolibrary.org QA Contact: testopia(a)bugs.koha-community.org We have templates that use the variable script_name for the path and filename of the script that called them, particularly as the action attribute of forms that call back to it. We have scripts that set the template->param script_name to their path and filename. What we don't have is a 1:1 match between templates and scripts, as the failure mode in bug 37797 comment 1 shows. If you set action="[% script_name %]" when it isn't defined, you get action="", which may work for years if every form submitted to that script is a POST, but once someone changes one to a get, action="" will POST to aqbudgetperiods.pl?op=delete_confirm&budget_period_id=2 and both the things in the POST body and also things in the query string will wind up being sent to the script. What I don't have is any good idea how to find templates using unset script_name, short of just brute force looking at every one. -- You are receiving this mail because: You are watching all bug changes.

1 13

[Bug 38395] New: Title is not displayed in hold history when biblio is deleted
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '26

26 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38395 Bug ID: 38395 Summary: Title is not displayed in hold history when biblio is deleted Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com, nick(a)bywatersolutions.com Depends on: 30648 Bug 30648 made Koha retain deleted_biblionumber in reserves and old_reserves, but did not make Koha use that deleted_biblionumber to display a title in holds history. To recreate: - place a hold - cancel the hold - look in patron hold history, see the title - delete the biblio - reload patron hold history, see "No bibliographic record" - use a report to look at your hold in old_reserves, confirm your deleted biblionumber is in the table Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30648 [Bug 30648] Title is lost in holds history when bibliographic record is deleted -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 26

[Bug 35560] New: Use the REST API for holds history
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '26

26 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35560 Bug ID: 35560 Summary: Use the REST API for holds history Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Blocks: 34832 On members/holdshistory.pl Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34832 [Bug 34832] [OMNIBUS] API all the Tables! -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 91

[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