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

[Bug 40933] New: Add sms support under Add message feature
by bugzilla-daemon＠bugs.koha-community.org 22 Oct '26

22 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40933 Bug ID: 40933 Summary: Add sms support under Add message feature Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: lari.taskula(a)hypernova.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Staff interface -> Patron details -> Add Message Current options are: Staff - Internal note OPAC Email - email addresses of patron Add: SMS - sms number of patron -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 40

[Bug 43336] New: Remove support for LibrisSpellcheck
by bugzilla-daemon＠bugs.koha-community.org 22 Oct '26

22 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43336 Bug ID: 43336 Summary: Remove support for LibrisSpellcheck Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- The Swedish National Library has discontinued the "bibspell" API that used to live at http://api.libris.kb.se/bibspell/ on which the LibrisSpellcheck feature was built, so we need to remove this feature from Koha. This should include at least: - The code - The sysprefs LibrisKey and LibrisURL - Settings for LibrisSpellcheck in the syspref OPACdidyoumean MariaDB [koha_kohadev]> select * from systempreferences where variable = 'opacdidyoumean'\G *************************** 1. row *************************** variable: OPACdidyoumean value: [{ "name": "AuthorityFile"}, { "name": "ExplodedTerms"}, { "name": "LibrisSpellcheck"}] options: NULL explanation: Did you mean? configuration for the OPAC. Do not change, as this is controlled by /cgi-bin/koha/admin/didyoumean.pl. type: Free $ grep -rn LibrisSpell * Koha/SuggestionEngine/Plugin/LibrisSpellcheck.pm:1:package Koha::SuggestionEngine::Plugin::LibrisSpellcheck; Koha/SuggestionEngine/Plugin/LibrisSpellcheck.pm:27: return 'LibrisSpellcheck'; Koha/SuggestionEngine/Plugin/LibrisSpellcheck.pm:68:Koha::SuggestionEngine::Plugin::LibrisSpellcheck koha-tmpl/intranet-tmpl/prog/en/modules/admin/didyoumean.tt:24: [% CASE 'LibrisSpellcheck' %] -- You are receiving this mail because: You are watching all bug changes.

1 37

[Bug 43863] New: Change padding for OPAC wrapper to use 100% width
by bugzilla-daemon＠bugs.koha-community.org 22 Oct '26

22 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43863 Bug ID: 43863 Summary: Change padding for OPAC wrapper to use 100% width Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- While smaller screens don't use padding for the OPAC wrapper, it would be nice on larger screens to use 100% of the width as well for a cleaner UI/UX. -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 42886] New: CSS files not installed
by bugzilla-daemon＠bugs.koha-community.org 22 Oct '26

22 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42886 Bug ID: 42886 Summary: CSS files not installed Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Installation and upgrade (command-line installer) Assignee: jonathan.druart(a)gmail.com Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com Depends on: 42850 Target Milestone: --- Follow-up of bug 42850, where I found that we have more than the ILL css files that are not installed. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42850 [Bug 42850] ILL requests stylesheet is not installed -- You are receiving this mail because: You are watching all bug changes.

1 31

[Bug 43525] New: Batch patron deletion and anonymization should be a background job
by bugzilla-daemon＠bugs.koha-community.org 21 Oct '26

21 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43525 Bug ID: 43525 Summary: Batch patron deletion and anonymization should be a background job 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: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Patron deletion can be slow. When I test with 10,000 borrowers it takes 3minutes 45 seconds. We should move this to a background job. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 39

[Bug 42418] New: Add Koha::Checkin(s) â checkin as a first-class resource
by bugzilla-daemon＠bugs.koha-community.org 21 Oct '26

21 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42418 Bug ID: 42418 Summary: Add Koha::Checkin(s) â checkin as a first-class resource Initiative type: --- Sponsorship --- status: 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: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com Depends on: 41728 Blocks: 24401 Checkins in Koha are currently a side effect â they happen to checkouts, transfers, and holds, but there is no single record that captures 'a staff member scanned this item and here is what happened.' This bug introduces checkins as a proper resource: - New `checkins` table tracking the full context (who, what, where, when) and outcomes (checkout returned, transfer triggered, hold filled) - Koha::Checkin and Koha::Checkins object classes - Wire into AddReturn so every checkin path (returns.pl, SIP, API) produces a Koha::Checkin record This addresses several long-standing gaps: - 'Who checked this in?' is currently unreliable (no checkin_user_id on old_issues) - Transfers and holds triggered by a return have no causal link back to the scan - Lost item fee refunds cannot be traced to the return event that caused them - Plugins (e.g. Rapido ILL) have to reconstruct context from side effects Depends on bug 41728 (checkin availability). Blocks bug 24401 (checkin REST API endpoint). Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24401 [Bug 24401] REST API: Check-in https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41728 [Bug 41728] Add `Koha::Item::Checkin::Availability` to centralize logic -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 152

[Bug 23415] New: Notify patron fines when renewing
by bugzilla-daemon＠bugs.koha-community.org 21 Oct '26

21 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23415 Bug ID: 23415 Summary: Notify patron fines when renewing 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: emmi.takkinen(a)outlook.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com It is possible to renew items for patron who has fines over accepted limit on renew page or from checkout list. There should be alert to notify staff that patron has fines over limit and confirmation to renew. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 369

[Bug 43258] New: Add a centralized IP range matching helper
by bugzilla-daemon＠bugs.koha-community.org 21 Oct '26

21 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43258 Bug ID: 43258 Summary: Add a centralized IP range matching helper 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 Depends on: 20846 Target Milestone: --- Several OPAC features check whether the client IP matches a configured range (OpacSuppressionByIPRange, RestrictedPageLocalIPs, SelfCheckAllowByIPRanges, etc). Each repeats the same inline pattern: my $ip_address = $ENV{'REMOTE_ADDR'}; my $in_range = ( $ip_address =~ /^$ip_range/ ); This should be centralized into a helper method (e.g. on C4::Context or a utility class) so callers can simply ask 'does the current request match this range?' without reimplementing the logic. A centralized helper would also be the right place to: - Handle edge cases (undef REMOTE_ADDR, empty range) - Document that the matching is regex-based, not CIDR - Eventually support CIDR notation if needed Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20846 [Bug 20846] Suppressed records still appear in public lists -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 43871] New: MEMBERSHIP_RENEWED/Account renewal should have its own messaging preference
by bugzilla-daemon＠bugs.koha-community.org 21 Oct '26

21 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43871 Bug ID: 43871 Summary: MEMBERSHIP_RENEWED/Account renewal should have its own messaging preference Initiative type: --- Sponsorship --- status: Product: Koha Version: 26.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: sbrown(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com Target Milestone: --- Account renewals/MEMBERSHIP_RENEWED messages are currently bundled into the 'Patron account expiry' messaging preference. There should be a separate option for 'Account renewal' messages, since libraries may want to enforce expiry messages but not renewal messages, and patrons may only want one or the other. It's also currently confusing for staff and patrons since the 'Patron account expiry' label doesn't indicate that it controls account renewal messages in addition to expiry. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 43757] New: EDIFACT parser drops syntax 4 interchanges silently and dies on a missing UNA
by bugzilla-daemon＠bugs.koha-community.org 21 Oct '26

21 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43757 Bug ID: 43757 Summary: EDIFACT parser drops syntax 4 interchanges silently and dies on a missing UNA Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Koha::Edifact::service_string_advice only accepts the exact string ":+.? '" and the failure paths are silent or fatal: 1. An interchange using syntax version 4 service characters, for example UNA:+.?*' , is not accepted. In syntax version 3 the fifth UNA character is reserved (a space); in syntax version 4 it is the repetition separator (default asterisk). Koha does not use repetition, so it can simply be ignored, but at present the file is thrown away. Result on main: the parser only carps "Non standard Service String Advice", Koha::Edifact->message_array returns 0 messages, process_invoice (and process_quote / process_ordrsp) then mark the message 'received' having done nothing. An invoice is lost without any error being shown to staff. 2. An interchange that does not start with UNA makes Koha::Edifact->new croak ("File does not start with a Service string advice"). The calls in edi_cron.pl are not wrapped, so the whole cron run stops: the remaining messages and accounts are not processed and the message is left in status 'processing'. Reproduced on main with a minimal interchange: - UNA:+.?*' -> messages = 0, warning only - no UNA -> dies References: ISO 9735 service string advice as profiled for syntax versions 3 and 4 (for example Odette OS11 "Structure of an EDIFACT Interchange", sections 2.2 and 4, and GS1 EANCOM syntax documentation). Note that for character sets other than UNOA/UNOB the default separators are non-printable, so a sender using printable separators is required to send UNA; a missing UNA is therefore a supplier-side error rather than something Koha should guess at. Proposed changes: a. Accept the syntax 4 service string advice by ignoring position 5, and keep refusing separators Koha cannot handle. b. When an interchange cannot be parsed, or parses to no messages, set the edifact_messages status to 'error', add an edifact_errors row with the reason, and carry on with the next message instead of marking it received or dying. (Optionally, as a follow-up, assume the standard separators when UNA is absent.) Test plan: 1. Add an INVOIC message whose interchange starts with UNA:+.?*' to edifact_messages and process it. 2. Without the patch: no invoice is created, the message is marked received, and no error is recorded. 3. With the patch: the invoice is created as it would be with UNA:+.? '. 4. Add a message with no UNA and a second, valid message, then run misc/cronjobs/edi_cron.pl (or process_invoice on both). 5. Without the patch: the cron dies on the first message. With the patch: the first message has status 'error' with an edifact_errors row, and the second is processed. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6