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

[Bug 42918] New: SRU-Abfrage in Deutscher Nationalbibliothek liefert keine Treffer.
by bugzilla-daemon＠bugs.koha-community.org 26 Jun '26

26 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42918 Bug ID: 42918 Summary: SRU-Abfrage in Deutscher Nationalbibliothek liefert keine Treffer. Initiative type: --- Sponsorship --- status: Product: Koha Version: 26.05 Hardware: All OS: All Status: NEW Severity: blocker Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: holger.voss(a)posteo.de QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Target Milestone: --- Created attachment 200991 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=200991&action=e… 4 Screenshots Despite the correct settings, the DNB does not return any hits in the SRU search or the Z39.50 search. The DNB server is accessible and delivers reliable results via the browser, but not via Koha's query module. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[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 42923] New: Require Email::Sender 2.601+ (for Email::Sender::Transport::SMTP)
by bugzilla-daemon＠bugs.koha-community.org 26 Jun '26

26 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42923 Bug ID: 42923 Summary: Require Email::Sender 2.601+ (for Email::Sender::Transport::SMTP) 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: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Koha already uses Email::Sender::Transport::SMTP but from version 2.601 onwards there is support for providing your own Authen::SASL authenticator object. When used with Authen::SASL >= 2.18, this allows Koha to use XOAUTH2 authentication over SMTP. Since Microsoft are moving towards XOAUTH2 authentication, it would be wise for us to backport this version for Koha. (2.601+ is available in Debian Trixie and up, and it's available in Ubuntu 24.04 and up) So we'd need it for Ubuntu 22.04 and Debian Bullseye and Debian Bookworm -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 42922] New: Require Authen::SASL >= 2.18
by bugzilla-daemon＠bugs.koha-community.org 26 Jun '26

26 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42922 Bug ID: 42922 Summary: Require Authen::SASL >= 2.18 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: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Authen::SASL gets used by Email::Sender::Transport::SMTP, but from version 2.18 onwards it includes the module Authen::SASL::Perl::XOAUTH2 which allows Koha to use the XOAUTH2 SASL authentication mechanism with SMTP. Since Microsoft are moving towards XOAUTH2 authentication, it would be wise for us to backport this version for Koha. (It's available in Debian Forky which hasn't been released yet, and it's available in Ubuntu 26.04.) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[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 42372] New: Allow plugins to add record display customizations
by bugzilla-daemon＠bugs.koha-community.org 26 Jun '26

26 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42372 Bug ID: 42372 Summary: Allow plugins to add record display customizations Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Plugin architecture Assignee: koha-bugs(a)lists.koha-community.org Reporter: tadeusz(a)sosnierz.com QA Contact: testopia(a)bugs.koha-community.org Following up on the feature introduced in https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39860, it'd be nice if plugins could add their own record display customisations as well. Patch coming in. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 9589] Authorities to authorities linker
by bugzilla-daemon＠bugs.koha-community.org 26 Jun '26

26 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9589 Thea Anne <jezzinelibraryamnq(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jezzinelibraryamnq(a)gmail.co | |m --- Comment #4 from Thea Anne <jezzinelibraryamnq(a)gmail.com> --- This is still a problem. My library has upgraded from a very ancient edition of KOHA & I am sorely missing this ability. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[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