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

[Bug 31736] New: Context for translation: "All"
by bugzilla-daemon＠bugs.koha-community.org 10 Aug '26

10 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31736 Bug ID: 31736 Summary: Context for translation: "All" Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr "All" is used all over Koha, and refers to different things. In French, those different things have different genders and the "All" must be in that gender ("tous" for "male-gendered" things and "toutes" for "female-gendered" things). In fr-CA-staff-prog, it says "All" is used in these places #: koha-tmpl/intranet-tmpl/prog/en/modules/acqui/invoices.tt:313 #: koha-tmpl/intranet-tmpl/prog/en/modules/acqui/invoices.tt:380 #: koha-tmpl/intranet-tmpl/prog/en/modules/acqui/parcel.tt:347 #: koha-tmpl/intranet-tmpl/prog/en/modules/admin/columns_settings.tt:121 #: koha-tmpl/intranet-tmpl/prog/en/modules/admin/columns_settings.tt:123 #: koha-tmpl/intranet-tmpl/prog/en/modules/admin/smart-rules.tt:208 #: koha-tmpl/intranet-tmpl/prog/en/modules/admin/smart-rules.tt:216 #: koha-tmpl/intranet-tmpl/prog/en/modules/admin/smart-rules.tt:387 #: koha-tmpl/intranet-tmpl/prog/en/modules/admin/smart-rules.tt:396 #: koha-tmpl/intranet-tmpl/prog/en/modules/admin/smart-rules.tt:918 #: koha-tmpl/intranet-tmpl/prog/en/modules/admin/smart-rules.tt:939 #: koha-tmpl/intranet-tmpl/prog/en/modules/catalogue/itemsearch.tt:45 #: koha-tmpl/intranet-tmpl/prog/en/modules/circ/view_holdsqueue.tt:247 #: koha-tmpl/intranet-tmpl/prog/en/modules/circ/view_holdsqueue.tt:254 #: koha-tmpl/intranet-tmpl/prog/en/modules/circ/view_holdsqueue.tt:261 #: koha-tmpl/intranet-tmpl/prog/en/modules/circ/view_holdsqueue.tt:268 #: koha-tmpl/intranet-tmpl/prog/en/modules/members/readingrec.tt:57 #: koha-tmpl/intranet-tmpl/prog/en/modules/onboarding/onboardingstep5.tt:63 #: koha-tmpl/intranet-tmpl/prog/en/modules/onboarding/onboardingstep5.tt:74 #: koha-tmpl/intranet-tmpl/prog/en/modules/onboarding/onboardingstep5.tt:86 #: koha-tmpl/intranet-tmpl/prog/en/modules/reports/acquisitions_stats.tt:203 #: koha-tmpl/intranet-tmpl/prog/en/modules/reports/acquisitions_stats.tt:248 #: koha-tmpl/intranet-tmpl/prog/en/modules/reports/acquisitions_stats.tt:263 #: koha-tmpl/intranet-tmpl/prog/en/modules/reports/cash_register_stats.tt:111 #: koha-tmpl/intranet-tmpl/prog/en/modules/reports/dictionary.tt:116 #: koha-tmpl/intranet-tmpl/prog/en/modules/reports/guided_reports_start.tt:245 #: koha-tmpl/intranet-tmpl/prog/en/modules/reports/guided_reports_start.tt:259 #: koha-tmpl/intranet-tmpl/prog/en/modules/reports/guided_reports_start.tt:887 #: koha-tmpl/intranet-tmpl/prog/en/modules/reports/guided_reports_start.tt:1494 #: koha-tmpl/intranet-tmpl/prog/en/modules/reports/itemslost.tt:152 #: koha-tmpl/intranet-tmpl/prog/en/modules/reports/itemslost.tt:156 #: koha-tmpl/intranet-tmpl/prog/en/modules/reports/itemslost.tt:165 #: koha-tmpl/intranet-tmpl/prog/en/modules/reports/itemslost.tt:179 #: koha-tmpl/intranet-tmpl/prog/en/modules/serials/checkexpiration.tt:50 #: koha-tmpl/intranet-tmpl/prog/en/modules/serials/serials-search.tt:281 #: koha-tmpl/intranet-tmpl/prog/en/modules/serials/serials-search.tt:396 #: koha-tmpl/intranet-tmpl/prog/en/modules/serials/serials-search.tt:415 #: koha-tmpl/intranet-tmpl/prog/en/modules/serials/subscription-bib-search.tt:25 #: koha-tmpl/intranet-tmpl/prog/en/modules/serials/subscription-bib-search.tt:37 #: koha-tmpl/intranet-tmpl/prog/en/modules/tools/additional-contents.tt:135 #: koha-tmpl/intranet-tmpl/prog/en/modules/tools/marc_modification_templates.tt:226 #: koha-tmpl/intranet-tmpl/prog/en/modules/tools/viewlog.tt:217 #: koha-tmpl/intranet-tmpl/prog/en/modules/tools/viewlog.tt:219 #: koha-tmpl/intranet-tmpl/prog/en/modules/tools/viewlog.tt:238 #: koha-tmpl/intranet-tmpl/prog/en/modules/tools/viewlog.tt:240 #: koha-tmpl/intranet-tmpl/prog/en/modules/tools/viewlog.tt:268 #: koha-tmpl/intranet-tmpl/prog/en/modules/tools/viewlog.tt:270 #: koha-tmpl/intranet-tmpl/prog/en/includes/additional-fields-entry.inc:12 #: koha-tmpl/intranet-tmpl/prog/en/includes/av-build-dropbox.inc:16 #: koha-tmpl/intranet-tmpl/prog/en/includes/patron-search.inc:247 #: koha-tmpl/intranet-tmpl/prog/en/includes/subscriptions-search.inc:33 #: koha-tmpl/intranet-tmpl/prog/en/includes/str/tinymce_i18n.inc:2 We should add context so that translators know what that "All" refers to. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 126

[Bug 42894] New: Port "Circulation" and "Cataloging" landing pages to a standard set of components
by bugzilla-daemon＠bugs.koha-community.org 10 Aug '26

10 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42894 Bug ID: 42894 Summary: Port "Circulation" and "Cataloging" landing pages to a standard set of components Initiative type: --- Sponsorship --- status: 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: olivia.reynolds(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Target Milestone: --- Building off of the work in Bug 36165, it would be good to port these landing pages to use the same set of components, perhaps with extensions if required. These two landing pages already have the same design, just implemented ad-hoc. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 42826] New: Reports: Allow transfer/adoption of report ownership
by bugzilla-daemon＠bugs.koha-community.org 10 Aug '26

10 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42826 Bug ID: 42826 Summary: Reports: Allow transfer/adoption of report ownership Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: lisette(a)bywatersolutions.com Target Milestone: --- Bug 42667 introduces the edit_all_reports permission, restricting report editing to the report's creator unless the librarian holds that permission. This surfaces a gap: there is currently no mechanism to change the borrowernumber recorded as a report's owner. Two common real-world scenarios are blocked without this: 1. Staff departure. A librarian leaves the organisation. Their reports become ownerless (if the patron record is deleted) or remain locked to a departed account. Other staff with create_reports but not edit_all_reports cannot maintain them. 2. Adoption of ownerless/legacy reports. Reports created before ownership tracking was tightened, or imported via Mana, may have no owner. A librarian who wants to claim such a report and take ongoing responsibility for it has no way to do so without involving a superlibrarian. Proposed behaviour: - On the report edit form and/or via a dedicated action in the saved-reports list, a librarian holding edit_all_reports should be able to reassign the report's owner to any other staff patron, or clear the owner field. - A bulk-transfer option for the staff-departure case: reassign all reports owned by patron X to patron Y. This could live in the patron deletion workflow or in the reports administration area. - A librarian without edit_all_reports should be able to adopt an ownerless report (setting themselves as owner), since this is a tightening of access rather than a loosening. Acceptance criteria: - Single-report ownership transfer, restricted to edit_all_reports holders - Ownerless-report adoption available to any create_reports holder - Bulk transfer (move all reports from patron A to patron B), restricted to edit_all_reports holders -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 42949] New: Add configurable complexity score header for WAF rate limiting
by bugzilla-daemon＠bugs.koha-community.org 10 Aug '26

10 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42949 Bug ID: 42949 Summary: Add configurable complexity score header for WAF rate limiting 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- We should have an optional complexity score response header that enables per-endpoint rate limiting in things like Cloudflare WAF Rate Limiting Rules. Heavy endpoints (search results, AJAX) get higher scores so they consume more of a client's rate limit budget. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 39027] New: News are order with older on top
by bugzilla-daemon＠bugs.koha-community.org 10 Aug '26

10 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39027 Bug ID: 39027 Summary: News are order with older on top Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: marion.durand(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org When a news is created, it is displayed last in the news list at the OPAC. You can change that behaviors by using the field 'Number' to order them manually but then, you have to manually edit all news to add a new one first. -- You are receiving this mail because: You are watching all bug changes.

1 38

[Bug 39160] New: Mojolicious::Plugin::OAuth2 is loaded suboptimally
by bugzilla-daemon＠bugs.koha-community.org 10 Aug '26

10 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39160 Bug ID: 39160 Summary: Mojolicious::Plugin::OAuth2 is loaded suboptimally Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org This is a deep cut, but the following line is not optimal: $self->plugin( 'Mojolicious::Plugin::OAuth2' => $oauth_configuration ); Mojolicious will first try to load that as Mojolicious::Plugin::Mojolicious::Plugin::OAuth2 before it realises that we've already loaded Mojolicious::Plugin::OAuth2 earlier in Koha::REST::V1. I reckon that should say: $self->plugin( 'OAuth2' => $oauth_configuration ); -- In the grand scheme of things, it's not a big deal, but we can save ourselves 26 system calls by changing 1 line. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 18

[Bug 32776] New: Choose to convert oldest reserve or all possible reserves to recalls
by bugzilla-daemon＠bugs.koha-community.org 09 Aug '26

09 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32776 Bug ID: 32776 Summary: Choose to convert oldest reserve or all possible reserves to recalls Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Bug 31415 introduces a script to convert reserves to recalls. By default, it will take the oldest reserve on a record and convert it to a recall. We should be able to customise which reserve(s) are converted to recalls. Options may include: - oldest reserve - one reserve for each issued item available to be recalled -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 25

[Bug 37196] New: Automatically add punctuation to Marc21 title fields
by bugzilla-daemon＠bugs.koha-community.org 09 Aug '26

09 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37196 Bug ID: 37196 Summary: Automatically add punctuation to Marc21 title fields Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P4 Component: MARC Bibliographic data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: alexander.wagner(a)desy.de QA Contact: testopia(a)bugs.koha-community.org Blocks: 21303 If the record leader 18 specifies `c` or `n` the Marc record in question does not hold any punctuation chars. IOW the record would look like ``` 245 10 |a Feynman-Kac-type theorems and Gibbs measures on path space |b with applications to rigorous quantum field theory |c József Lörinczi ; Fumio Hiroshima ; Volker Betz ``` (Sample from DNB: http://d-nb.info/988967189/about/marcxml) Currently, Koha will display this as ``` Feynman-Kac-type theorems and Gibbs measures on path space with applications to rigorous quantum field theory József Lörinczi ; Fumio Hiroshima ; Volker Betz ``` while it should actually be displayed like ``` Feynman-Kac-type theorems and Gibbs measures on path space : with applications to rigorous quantum field theory / József Lörinczi ; Fumio Hiroshima ; Volker Betz ``` In this example, if leader 18 == `c`|`n`, Koha should - add the missing ` : ` between title and remainder of title - Add ` / ` before the statement of responsibility - Add a `<span class="title_remainder">` around the remainder of title to allow for formatting Analogously, it should treat the other fields of 245. Use https://www.loc.gov/aba/pcc/documents/isbdmarc2016.pdf as a guideline. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21303 [Bug 21303] XSLT should look in LDR/18 to know whether to add punctuation or not -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 26

[Bug 42842] New: Remove materialized patron data from tmp_holdsqueue
by bugzilla-daemon＠bugs.koha-community.org 09 Aug '26

09 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42842 Bug ID: 42842 Summary: Remove materialized patron data from tmp_holdsqueue Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal 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 Depends on: 42503 Target Milestone: --- Since bug 42503 converted the holds queue page to be API-driven, the materialized patron fields in tmp_holdsqueue (surname, firstname, phone, cardnumber) are no longer used. The page now embeds patron data via the borrowernumber FK through the REST API. These columns should be removed because: 1. They are dead code â nothing reads them after bug 42503 2. They leave patron PII (name, phone, card number) in an unaudited table that is not subject to patron data cleanup/anonymization routines 3. Privacy concern: tmp_holdsqueue is rebuilt periodically but retains patron information between rebuilds, and this data is not covered by GDPR/privacy cleanup tools The fix should: - Remove surname, firstname, phone, cardnumber columns from tmp_holdsqueue - Stop populating them in C4::HoldsQueue::CreatePicklistFromItemMap - Update Koha::Schema::Result::TmpHoldsqueue - Remove the undef mappings in Koha::Hold::HoldsQueueItem::to_api_mapping Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42503 [Bug 42503] Render the holds queue using the REST API -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 31

[Bug 41500] New: Expired hold charge value containing decimal with fraction dropped when editing a rule
by bugzilla-daemon＠bugs.koha-community.org 09 Aug '26

09 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41500 Bug ID: 41500 Summary: Expired hold charge value containing decimal with fraction dropped when editing a rule Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: emmi.takkinen(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com When one edits a circulation rule where Expired hold charge value contains decimal with fractions other than 0 (e.g. 1.30), value is not copied to editing row. This happens because column is considered as column which cannot contain nothing else than integer value and is therefore left blank if fraction is used. To reproduce: 1. Add or modify existing circulation rule and set Expired hold charge value as 1.30. 2. Edit the rule you just created or modified. => Note that Expired hold charge is not displayed. => When saving the rule note that Expired hold charge is now overwritten with blank value. 3. Edit the rule again and set Expired hold charge value as 1.00. 4. Now edit rule again. => Note that Expired hold charge is now displayed as expected and saving doesn't overwrite the value. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14