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

[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 43209] New: Add X-Content-Type-Options security headers
by bugzilla-daemon＠bugs.koha-community.org 09 Aug '26

09 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43209 Bug ID: 43209 Summary: Add X-Content-Type-Options security headers 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: --- Koha already sends X-Frame-Options: SAMEORIGIN on its responses but does not send X-Content-Type-Options. Without it a browser may MIME sniff a response and treat it as a content type other than the one declared, which can turn an otherwise harmless response into executable script and enable content type confusion attacks. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

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

09 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 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 43239] New: Serial items item type can be set incorrectly when receiving multiple items
by bugzilla-daemon＠bugs.koha-community.org 09 Aug '26

09 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43239 Bug ID: 43239 Summary: Serial items item type can be set incorrectly when receiving multiple items Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: emmi.takkinen(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Target Milestone: --- It is possible to create serial item with wrong itemtype if syspreference makePreviousSerialAvailable is enabled and field "item type for older issues" isn't filled when creating a subscription for biblio record. This happens when multiple items are created. In installations where itemtypes differ between items and biblios, this causes data inconsistencies and leads to errors in biblios Holdings table. To reproduce: 1. Enable systempreference makePreviousSerialAvailable. 2. Create new biblio record. 3. Create a new subscription for biblio record you made, select option "Create an item record", select different item type from "Item type" selection than biblio record has but leave selection "item type for older issues" empty. 4. Receive a serial item for subscription. Check from biblio records Holdings table that its item type matches item type selected in step 3. 5. Now receive 3 serial items. After creating them check Holdings table again. => Note that last item created now has same item type as biblio record. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[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

[Bug 43255] New: Batch remove items from a single label batch
by bugzilla-daemon＠bugs.koha-community.org 08 Aug '26

08 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43255 Bug ID: 43255 Summary: Batch remove items from a single label batch Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Label/patron card printing Assignee: chris.nighswonger(a)veritassuperaitsolutions.com Reporter: crosenthal(a)pwcgov.org QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Would be nice to be able to select all items in a label batch (label-edit-batch.pl) and batch remove them from that batch. Could be useful for re-using a label batch as opposed to creating a new one each time -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 7386] Label batches cannot be batch deleted
by bugzilla-daemon＠bugs.koha-community.org 08 Aug '26

08 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7386 crosenthal(a)pwcgov.org <crosenthal(a)pwcgov.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |crosenthal(a)pwcgov.org --- Comment #8 from crosenthal(a)pwcgov.org <crosenthal(a)pwcgov.org> --- +1 -- You are receiving this mail because: You are watching all bug changes.

1 0