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

[Bug 42529] New: Move GetAgeRestriction to Koha namespace
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '26

23 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42529 Bug ID: 42529 Summary: Move GetAgeRestriction to Koha namespace 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: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org `C4::Circulation::GetAgeRestriction` parses age restriction strings (e.g. "FSK 16", "PEGI 6") from biblio metadata using the AgeRestrictionMarker system preference. It is used in 3 places (C4::Circulation twice, C4::Reserves once). I propose: * Add Koha::Biblio->age_restriction method that parses the restriction string and returns the numeric age (or undef if none) * Add Koha::Patron->meets_age_restriction($biblio) that returns whether the patron meets the age restriction * Replace all GetAgeRestriction callers with the new methods * Remove GetAgeRestriction from C4::Circulation * Move the existing test (t/Circulation/AgeRestrictionMarkers.t) to cover the new methods -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 54

[Bug 42652] New: Add per-account option to allow restricted patrons to retain SIP inet access
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '26

23 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42652 Bug ID: 42652 Summary: Add per-account option to allow restricted patrons to retain SIP inet access 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: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org This patch adds a new per-account SIP2 configuration flag, `patron_restriction_blocks_inet`, that controls whether a patron with an account restriction (debarment) also has their SIP inet profile blocked. Currently, when a patron is restricted in Koha, the SIP inet field (FID_INET_PROFILE) is set to N. This means online services that use SIP for authentication â such as PC booking systems or printing services â also deny access to the restricted patron. Libraries that want to block a patron from borrowing items but still allow them to use digital services have no way to achieve this. With this flag set to 0/false on a SIP2 account, restricted patrons will receive Y for inet access, allowing them to authenticate to online services, while checkout privileges remain blocked as normal. The default (NULL or true) preserves existing behaviour: restrictions block both checkouts and inet access. Test plan: 1. Apply all patches and run the database update. 2. Go to Administration > SIP2 accounts and edit an account. 3. Confirm the new "Restrictions block internet access" toggle is visible. 4. Create a test patron and apply an account restriction to them. 5. With the toggle unset (default), authenticate the patron via SIP and confirm the patron status response shows charge privileges denied AND inet profile N. 6. Set the toggle to false/disabled for the account and re-authenticate. 7. Confirm the patron status response still shows charge privileges denied but inet profile is now Y. 8. Confirm a non-restricted patron is unaffected. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 42035] New: Add diff support to APIKEYS CREATE and DELETE action logs
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '26

23 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42035 Bug ID: 42035 Summary: Add diff support to APIKEYS CREATE and DELETE action logs Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Transaction logs Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org Blocks: 37940 The action logging for the APIKEYS module (Koha/ApiKey.pm) already has diff support for MODIFY, REVOKE, and ACTIVATE actions. However, CREATE and DELETE actions do not pass the $original parameter. Affected calls in Koha/ApiKey.pm: - APIKEYS/CREATE (~line 84): logaction( 'APIKEYS', 'CREATE', $self->patron_id, $self, undef ); (passes $self as $infos but no $original; for CREATE, $self represents the new state) - APIKEYS/DELETE (~line 142): logaction( 'APIKEYS', 'DELETE', $patron_id ) (no info or original passed at all) For CREATE, passing $self as both $infos and $original (or with undef original) would allow the viewer to show what was created. For DELETE, the API key object should be fetched before deletion and passed as both $infos and $original so the log shows what was deleted. This is important for security audit trails. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37940 [Bug 37940] [OMNIBUS] All modification logged via action logs should include original to create JSON diff -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 42036] New: Add diff support to REPORTS action logs
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '26

23 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42036 Bug ID: 42036 Summary: Add diff support to REPORTS action logs Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Transaction logs Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org Blocks: 37940 The action logging for saved reports does not pass the $original parameter to logaction(), so no structured diff is generated in the action_logs.diff column. Currently log entries store the report name and SQL concatenated as a plain string. Affected calls: - reports/guided_reports.pl MODIFY (~line 250): logaction( "REPORTS", "MODIFY", $id, "$reportname | $sql" ) (no $original; only post-change state captured as a string) - reports/guided_reports.pl ADD (~line 594): logaction( "REPORTS", "ADD", $id, "$name | $sql" ) - C4/Reports/Guided.pm DELETE (~line 798): logaction( "REPORTS", "DELETE", $id, $data->report_name . " | " . $data->savedsql ) This bug covers updating these calls to pass structured hashrefs (e.g. { report_name => ..., savedsql => ... }) as $infos and, for MODIFY, the pre-change report data as $original, enabling proper before/after diff display in the action log viewer. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37940 [Bug 37940] [OMNIBUS] All modification logged via action logs should include original to create JSON diff -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 42037] New: Add diff support to ACQUISITIONS action logs
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '26

23 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42037 Bug ID: 42037 Summary: Add diff support to ACQUISITIONS action logs Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Transaction logs Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org Blocks: 37940 The action logging for acquisitions events does not pass structured data or the $original parameter to logaction(), so no structured diff is generated in the action_logs.diff column. Currently the only logged acquisitions action is: - acqui/cancelorder.pl CANCEL_ORDER (~line 82): logaction( 'ACQUISITIONS', 'CANCEL_ORDER', $ordernumber ); (no $infos or $original passed) This bug covers a broader review of acquisitions logging to: 1. Update the CANCEL_ORDER log call to pass the order data (Koha::Acquisition::Order object or its unblessed hashref) as both $infos and $original so the log shows what was cancelled. 2. Identify and add logaction() calls for other significant acquisitions events (order creation, modification, receipt) that are currently unlogged or poorly logged, passing appropriate $infos and $original data to enable diff support. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37940 [Bug 37940] [OMNIBUS] All modification logged via action logs should include original to create JSON diff -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 23873] New: Allow marc modification templates to use capturing groups in substitutions
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '26

23 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23873 Bug ID: 23873 Summary: Allow marc modification templates to use capturing groups in substitutions Change sponsored?: --- Product: Koha Version: 19.05 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To test: - Find/create a bib record with a date formatted as YYYYMMDD - Create a marc modification template to Copy and Replace your field with this regex: s/(\d{4})(\d{2})(\d{2})/\1\-\2\-\3/ -- this should reformat your date as "YYYY-MM-DD" - Apply your template to your bib - Observe that the match worked, but the substitution failed -- the value "\1\-\2\-\3" is treated literally Apparently this fails due to some aspect of how regex works within perl? It'd be hugely useful if we could get it working. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 35

[Bug 15836] New: Labels: Offer configuration option for splitting call number in layout definition
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '26

23 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15836 Bug ID: 15836 Summary: Labels: Offer configuration option for splitting call number in layout definition Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Label/patron card printing Assignee: cnighswonger(a)foundations.edu Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Currently the call number splitting seems to be mostly implemented for DDC and LC classifications. Those are both not very common in Germany and possibly other countries. A lot of our libraries use their own custom classification schemes so the call number splitting is something that should be individually configurable. One option would be using a regex expression, that can be set in the layout additional to the standard splitting offered by the checkbox. (see bug 2500 for some discussion about the splitting algorithms implemented atm) -- You are receiving this mail because: You are watching all bug changes.

1 132

[Bug 42302] New: xgettext.pl does not output to STDOUT correctly
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '26

23 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42302 Bug ID: 42302 Summary: xgettext.pl does not output to STDOUT correctly Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: tadeusz(a)sosnierz.com QA Contact: testopia(a)bugs.koha-community.org CC: f.demians(a)tamil.fr, jonathan.druart(a)gmail.com xgettext.pl tries to produce output to STDOUT but default, but fails because of the coding error: ``` $ echo koha-tmpl/opac-tmpl/bootstrap/en/includes/serial-status.inc > transfiles $ ./misc/translator/xgettext.pl -vaf transfiles ./misc/translator/xgettext.pl: Outputting to STDOUT... ./misc/translator/xgettext.pl: Opening input file list "transfiles" ./misc/translator/xgettext.pl: Processing file "./koha-tmpl/opac-tmpl/bootstrap/en/includes/serial-status.inc" $ head \&STDOUT # SOME DESCRIPTIVE TITLE. # Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER # This file is distributed under the same license as the PACKAGE package. # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. # #, fuzzy msgid "" msgstr "" "Project-Id-Version: Koha\n" "POT-Creation-Date: 2026-04-08 13:45+0200\n" ``` It should go to actual STDOUT instead of a file called that :) Patch coming in. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 41938] New: Argument "" isn't numeric in numeric gt (>) ... warnings in circulation.tt
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '26

23 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41938 Bug ID: 41938 Summary: Argument "" isn't numeric in numeric gt (>) ... warnings in circulation.tt Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: roman.dolny(a)jezuici.pl Reporter: roman.dolny(a)jezuici.pl QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com The warnings: [WARN] Argument "" isn't numeric in numeric gt (>) at /kohadevbox/koha/koha-tmpl/intranet-tmpl/prog/en/modules/circ/circulation.tt line 1072. [WARN] Argument "" isn't numeric in numeric gt (>) at /kohadevbox/koha/koha-tmpl/intranet-tmpl/prog/en/modules/circ/circulation.tt line 1188. appears in the plack-intranet-error.log. To reproduce: 1. Use a fresh KTD, observe plack-intranet-error.log. 2. Find any patron and go to "Check out" tab. ==> Warnings should appear in plack-intranet-error.log -- You are receiving this mail because: You are watching all bug changes.

1 17

[Bug 23833] New: [Omnibus] JavaScript should conform to coding guidelines recommended by ESLint
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '26

23 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23833 Bug ID: 23833 Summary: [Omnibus] JavaScript should conform to coding guidelines recommended by ESLint Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org An updated version of Bug 9284. ESLint can be used to check JavaScript for errors and potential problems. It can be installed on a variety of platforms and integrated into various editors: https://eslint.org/docs/user-guide/integrations This bug will serve as an omnibus for any bug devoted to ESLint-related cleanup. -- You are receiving this mail because: You are watching all bug changes.

1 14