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

[Bug 27603] New: Add API for lists management
by bugzilla-daemon＠bugs.koha-community.org 01 Sep '26

01 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27603 Bug ID: 27603 Summary: Add API for lists management Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: oleonard(a)myacpl.org Created attachment 116256 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=116256&action=e… Screenshot of the list modal idea I was playing around with making the list add form a modal instead of a popup, and while it can be hacked together as things are now it really would be better to have an API to work with. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 38050] New: Add REST endpoints for working with "lists"/"virtual shelves"
by bugzilla-daemon＠bugs.koha-community.org 01 Sep '26

01 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38050 Bug ID: 38050 Summary: Add REST endpoints for working with "lists"/"virtual shelves" Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com We don't yet expose the lists functionality over API's, this would be a beneficial enhancement both for internal use and thrid party integrations wishing to integrate with this functionality. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 72

[Bug 42719] New: OAuth/OIDC login crashes with 500 when no CGISESSID cookie exists (IdP-initiated flow)
by bugzilla-daemon＠bugs.koha-community.org 01 Sep '26

01 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42719 Bug ID: 42719 Summary: OAuth/OIDC login crashes with 500 when no CGISESSID cookie exists (IdP-initiated flow) Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: martin.renvoize(a)openfifth.co.uk CC: dpavlin(a)rot13.org When a user initiates login from the IdP (e.g. clicking an app tile in Okta), they are redirected directly to Koha's /api/v1/oauth/login/{provider}/{interface} endpoint without ever visiting a Koha page first. Since no Koha page was visited, no session exists and no CGISESSID cookie is present. The code at Koha::REST::V1::OAuth::Client line 99 calls: $c->req->cookie('CGISESSID')->value This crashes with: Can't call method "value" on an undefined value The fix is to create a session on-the-fly when the initial OAuth request has no existing session cookie. This supports IdP-initiated SSO flows while preserving CSRF protection (the state parameter is still bound to the session via the browser's cookie jar). The same guard is needed on the callback branch's check_csrf call â if the cookie is missing on callback, redirect with an error instead of crashing. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 32

[Bug 17385] New: Add custom export notices
by bugzilla-daemon＠bugs.koha-community.org 31 Aug '26

31 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17385 Bug ID: 17385 Summary: Add custom export notices Change sponsored?: --- Product: Koha Version: 16.05 Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: bouzid.fergani(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl this patch, add custom export notices using xslt. -- You are receiving this mail because: You are watching all bug changes.

1 423

[Bug 42097] New: Add link to create new club from list of club templates
by bugzilla-daemon＠bugs.koha-community.org 31 Aug '26

31 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42097 Bug ID: 42097 Summary: Add link to create new club from list of club templates Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org To create a new club you have to choose the club template from a (potentially) long list of club templates. I think it would be useful to also offer the option of creating a new club directly from the club templates actions. -- You are receiving this mail because: You are watching all bug changes.

1 8

[Bug 40092] New: Adding authorities - clicking save doesn't fill auto-populated fields
by bugzilla-daemon＠bugs.koha-community.org 31 Aug '26

31 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40092 Bug ID: 40092 Summary: Adding authorities - clicking save doesn't fill auto-populated fields Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org When adding a new authority record, clicking save (without filling in any fields) doesn't fill in the auto-populated fields such as 000, 003, and 008. In a 24.11.x instance, this works (start up a local instance or use one of the demos): 1. Authorities > New authority > Topical term 2. Don't enter any information in any fields. 3. Click 'save'. 4. Note that fields such as 000 and 003 are auto-populated (not sure if that is the right term). In 25.05.00 or main, this no longer works: 1. Repeat steps 1 to 3. 2. Note that: - fields such as 000 and 003 are not auto-populated - the mandatory fields are now highlighted in yellow - clicking the individual fields doesn't auto-populate them -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 26

[Bug 35870] New: Adding an edit_authorities subpermission for editauthorities
by bugzilla-daemon＠bugs.koha-community.org 31 Aug '26

31 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35870 Bug ID: 35870 Summary: Adding an edit_authorities subpermission for editauthorities 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: wainuiwitikapark(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 50

[Bug 35914] New: Add permission for changing a user password
by bugzilla-daemon＠bugs.koha-community.org 31 Aug '26

31 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35914 Bug ID: 35914 Summary: Add permission for changing a user password Change sponsored?: --- Product: Koha Version: 23.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com There are situations where libraries do not want staff to be able to change a patron's password using the Change Password button but there is currently no way to split out permission to block this. You have to turn off the ability to view/edit all patron info which is also not helpful. Some libraries prefer that staff either send a password reset email, or direct patrons to the OPAC to reset a password. It would be a great enhancement to add a subpermission to BORROWERS to allow/disallow the ability for staff to change a patron password. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 32122] New: Wrong permissions check on item circulation alerts
by bugzilla-daemon＠bugs.koha-community.org 31 Aug '26

31 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32122 Bug ID: 32122 Summary: Wrong permissions check on item circulation alerts Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Bug 14391 added granular permissions for the administration module, however, there was a mismatch in the check on item circulation alerts and the new permission -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 10

[Bug 42166] New: Cannot Edit as new (duplicate) a record without a 008 in the advanced editor
by bugzilla-daemon＠bugs.koha-community.org 31 Aug '26

31 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42166 Bug ID: 42166 Summary: Cannot Edit as new (duplicate) a record without a 008 in the advanced editor Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl To recreate: 1. Edit or create a framework that does not require the 008. 2. Make or edit a record in that framework without a 008. 3. Turn on EnableAdvancedCatalogingEditor, and make sure you are using the advanced editor. 4. Go to the record from step 2 and click "Edit as new (duplicate)" 5. The record won't load in the advanced editor. Uncaught TypeError: record.field(...).subfield is not a function -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17