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

[Bug 41909] New: Patron record needs a modification time stamp
by bugzilla-daemon＠bugs.koha-community.org 23 Feb '26

23 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41909 Bug ID: 41909 Summary: Patron record needs a modification time stamp Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons 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, kyle(a)bywatersolutions.com There does not seem to be a sufficient time stamp to indicate when a patron account/record has been modified/updated. The Last Updated time stamp seems to change any time a patron logs in, which completely makes it useless as an indicator as to when a staff member has updated the account information. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 23650] New: Multiple opac-restrictedpage.pl pages
by bugzilla-daemon＠bugs.koha-community.org 23 Feb '26

23 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23650 Bug ID: 23650 Summary: Multiple opac-restrictedpage.pl pages Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org Would like there to be the option to create multiple opac-restrictedpage.pl pages so that depending on patron or library, this information could be custom. Would need: * A way to identify and code for each page * A way to specify which patron types or branches could access each page. -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 41910] New: List of notice modules in letter.tt are in no particular order
by bugzilla-daemon＠bugs.koha-community.org 23 Feb '26

23 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41910 Bug ID: 41910 Summary: List of notice modules in letter.tt are in no particular order Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Based off of a comment from Bug 40255: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40255#c24 The list of notices is in no particular order: TO RECREATE: 1. Go to Tools > Notices & Slips 2. Click '+ New notice' 3. See each module, they are not ordered. I agree with Katrin, they should be ordered by code. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 40882] New: Identity provider errors are not translatable
by bugzilla-daemon＠bugs.koha-community.org 23 Feb '26

23 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40882 Bug ID: 40882 Summary: Identity provider errors are not translatable Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org In Koha/REST/V1/OAuth/Client.pm, when there's an error, we redirect to another page with a URL parameter "auth_error". Here's some example errors: "No configuration found for your provider"; "wrong_csrf_token" "No configuration found for your email domain" "User cannot access this resource" <An exception caught during $c->oauth2->get_token_p> Only the errors after "wrong_csrf_token" are escaped. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 20628] New: Search result highlighting not working with truncated search terms
by bugzilla-daemon＠bugs.koha-community.org 23 Feb '26

23 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20628 Bug ID: 20628 Summary: Search result highlighting not working with truncated search terms Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org This specific issue may fall within the bounds of this larger bug: Bug 11270 - Search Result highlighting should be refactored https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11270 Search terms are not highlighted in search results if the terms are truncated. For example, the search kw:mold will show results with every instance of "mold" highlighted, even if it appears within a larger string like "molding." But a search for kw:mold* or kw,rtrn:mold will not show any highlighting in the search results. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 2646] Add sort option for the series number
by bugzilla-daemon＠bugs.koha-community.org 23 Feb '26

23 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2646 --- Comment #14 from Jason Robb <jrobb(a)sekls.org> --- (In reply to Esther Melander from comment #12) > How would Koha handle a series sort when there is more than one series > statement with different volume numbers? I am thinking of the Magic Tree > House series which was originally published with one series order and then > the publisher re-did the series with a new order. That would mean a title > could conceivably have two series statements and be sorted in two different > ways. This may be an edge example, but I'm sure there are others. It would be neat if you could click on a series facet and it sorts by that. So if your query contains "&limit=title-series:Magic%20Tree%20House" then it sorts the record by the Magic Tree House number, and if your query contains "&limit=title-series:Merlin%20Missions" it sorts the same record by the Merlin Mission number. With Elastic if a record has two 490s, an 800 and an 830 they all get made into individual title-series facets. Maybe the normalized $v from each field could get stored in a pair alongside the series entry so it could be leveraged for sorting by individual series entry? Otherwise it would make sense to prioritize duplicate fields by the order they appear in the record to give the cataloger control. If the "Magic Tree House" 490 comes first it should sort by that, but if you want the "Merlin Missions" 490 to sort first all you should have to do is reorder the two fields in the MARC editor. -- You are receiving this mail because: You are watching all bug changes. You are the QA Contact for the bug.

1 0

[Bug 31378] New: Add a generic OAuth2/OIDC client implementation
by bugzilla-daemon＠bugs.koha-community.org 23 Feb '26

23 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31378 Bug ID: 31378 Summary: Add a generic OAuth2/OIDC client implementation Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org We need a generic client implementation that allows setting different authentication services and configurations. It needs to: - work for the - work for the staff interface - have a CRUD page for dealing with authentication services - be designed so we eventually move other authentication mechanisms into this CRUD (e.g. CAS? LDAP?) - allow setting configurations per-service and per-domain (i.e. an OIDC service might allow authenticating several (campus?) domains and we should handle that). - provide a prettier integration with the login form than CAS and friends Follow-ups: - Prioritize IdP's when displaying login options - Icon / user-oriented presentation Not all of this needs to be implemented on this bug report. Should be splitted. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 360

[Bug 40994] New: Field 651 subfields other than "a" present in Topics facet
by bugzilla-daemon＠bugs.koha-community.org 23 Feb '26

23 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40994 Bug ID: 40994 Summary: Field 651 subfields other than "a" present in Topics facet Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: lari.taskula(a)hypernova.fi QA Contact: testopia(a)bugs.koha-community.org To reproduce: 1. Start creating a new record 2. Populate the following field: 651: _a Suomi _2 yso/fin _0 http://www.yso.fi/onto/yso/p94426 3. Save the record (and ensure the new record gets indexed) 4. On either OPAC or staff client, search for all records 5. Observe "Suomi", "yso/fin", "http://www.yso.fi/onto/yso/p94426" under "Topics" facet How it should be: 4. On either OPAC or staff client, search for all records 5. Observe "Suomi" under "Topics" facet -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 11

[Bug 37418] New: Expand delete_patron.pl / Patrons with defined restrictions should not be deleted
by bugzilla-daemon＠bugs.koha-community.org 23 Feb '26

23 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37418 Bug ID: 37418 Summary: Expand delete_patron.pl / Patrons with defined restrictions should not be deleted Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: michaela.sieber(a)kit.edu QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com In some cases we don't want borrowers / patrons not to be deleted if they have certain restrictions. Therefor we add a new parameter to the cronjob delete_patrons.pl (see manual https://koha-community.org/manual/latest/en/html/cron_jobs.html#batch-delet… ) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 30

[Bug 37182] New: 'datetime' field lost on pseudonymization
by bugzilla-daemon＠bugs.koha-community.org 23 Feb '26

23 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37182 Bug ID: 37182 Summary: 'datetime' field lost on pseudonymization Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Transaction logs Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.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 16