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

[Bug 40650] New: Identity providers lack support for extended patron attribute type mapping
by bugzilla-daemon＠bugs.koha-community.org 26 Jun '26

26 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40650 Bug ID: 40650 Summary: Identity providers lack support for extended patron attribute type mapping 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: oliver.behnke(a)aei.mpg.de QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org Hi, so far we've been using LDAP authentication and with extended attribute type mapping (on register and login/update) but we have to move to OIDC. Thankfully there's an identity provider (IdP) for that. Great! However, testing and code inspection indicate that extended patron attributes can't be used for IdP mapping. When I try that I get: > There was an error authenticating to external identity provider > No property <ATTRIBUTE> for Koha::Patron At first glance, the code seems to support that assessment. For instance, the "update_on_auth" feature [1] calls set() which isn't overridden in Koha::Patron so Koha::Object.set() is being called [2], which of course isn't aware of those patron-specific extended attributes, eventually triggering the error above. To me that omission is a regression as existing auth methods like LDAP do support mapping extended patron attributes. Without that we can't rely on using identity providers since we'd lose required functionality. Thanks [1] https://github.com/Koha-Community/Koha/blob/8d31c2e06733fbc0f599ea99fe46df5… [2] https://github.com/Koha-Community/Koha/blob/8d31c2e06733fbc0f599ea99fe46df5… -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22

[Bug 32542] New: Coce images not appearing in staff client
by bugzilla-daemon＠bugs.koha-community.org 26 Jun '26

26 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32542 Bug ID: 32542 Summary: Coce images not appearing in staff client Change sponsored?: --- Product: Koha Version: master 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. Have Coce on, use 'https://coce.bywatersolututions.com' as the CoceProviders if needed. Select all providers 2. Turn on IntranetCoce and OpacCoce. 3. Do a OPAC search to retrieve some Coce images on both the OPAC results page and detail. 4. Do the same search and look at the same detail pages in the staff client. Nothing appears. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 31

[Bug 17110] New: Lower CSRF expiry in Koha::Token
by bugzilla-daemon＠bugs.koha-community.org 26 Jun '26

26 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17110 Bug ID: 17110 Summary: Lower CSRF expiry in Koha::Token Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 26

[Bug 28703] New: Display problem in 505$a field
by bugzilla-daemon＠bugs.koha-community.org 26 Jun '26

26 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28703 Bug ID: 28703 Summary: Display problem in 505$a field Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: hc(a)interleaf.ie QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Created attachment 122798 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=122798&action=e… Appearance of arrows in 505 field Content in the 505$ a field (Formatted contents note) is displaying arrows at the beginning and end of the content. This was not appearing on the 19.11 release of Koha. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 40153] New: Add Authen::SASL::Perl as explicit dependency
by bugzilla-daemon＠bugs.koha-community.org 26 Jun '26

26 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40153 Bug ID: 40153 Summary: Add Authen::SASL::Perl as explicit dependency Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor 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 In Mattermost Jan Kissig mentioned how Authen::SASL::Perl wasn't automatically installed with Koha on a new server. At a glance libauthen-sasl-perl is just a recommendation of libemail-sender-perl, so if for whatever reason recommendations aren't installed, it will fail to install and Koha won't be able to send SMTP emails. We'll need a newer version of Authen::SASL::Perl for bug 38338 anyway, so may as well make it explicit sooner rather than later. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 20547] New: Add default indicators for authorities (counterpart of 9701)
by bugzilla-daemon＠bugs.koha-community.org 26 Jun '26

26 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20547 Bug ID: 20547 Summary: Add default indicators for authorities (counterpart of 9701) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org Bug 9701 adds them at the biblio side. We could do the same for authorities. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 25

[Bug 30215] New: "Item found" in accountlines untranslatable
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '26

25 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30215 Bug ID: 30215 Summary: "Item found" in accountlines untranslatable 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 When a lost item is returned and refunded to the patron, the accountline description contains "Item found" which is untranslatable. To generate this accountline: 0- Make sure BlockReturnOfLostItems is set to Don't Block 0- Make sure WhenLostChargeReplacementFee is set to Charge 0- In Circulation rules, make sure Default lost item fee refund on return policy is set to one of the Refund options 0- Make sure your item has a replacement price (field v of the item) 1- Check out the item to a patron 2- Change the status of the item to lost The patron should be charged the replacement price 3- Check in the item The patron should have a new credit Lost item fee refund In the description of this new credit, it says "Item found <itemnumber>". I couldn't find "Item found" anywhere in the po files. In fact, when I git grep it, it only shows up in C4/Items. (Also, I'm wondering if the itemnumber is really useful here, I think it will confuse library staff as I myself was confused, but this is not the point of this bug) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 41489] New: Add "Create from Mana" to the Reports module home
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '26

25 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41489 Bug ID: 41489 Summary: Add "Create from Mana" to the Reports module home Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Mana-kb Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: alex.arnaud(a)biblibre.com We don't expose the module toolbar on the Reports module home page, instead opting to have the "New" options from it exposed in the 'main actions box' as "Create from SQL". If Mana is configured, we should add the option to "Import from Mana" or "Create from Mana" to this box. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 34756] New: Cancelling a hold does not cancel the related transfer
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '26

25 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34756 Bug ID: 34756 Summary: Cancelling a hold does not cancel the related transfer 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: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When a hold is confirmed and its pickup location is different from the item's location, a transfer is initiated. If the hold is cancelled, the item remains in transfer whereas it is no longer needed at the transfer destination. Is this normal behaviour ? It seems that staff users should at least see a message about the transfer and maybe have the ability to cancel it. Steps to reproduce: 1. Create an item at library A 2. Place a hold on this item with a pickup location at library B 3. Check in the item at library A 4. Confirm the hold. The item should now be in transit to library B 5. Cancel the hold. There is no message about the probably useless transfer. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 40

[Bug 35797] New: REST API: Add GET route for patronimage
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '26

25 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35797 Bug ID: 35797 Summary: REST API: Add GET route for patronimage Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: shi-yao.wang(a)inLibro.com CC: tomascohen(a)gmail.com Add GET route to get patronimage database table data -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 70