November 2025 - Koha-bugs - lists.koha-community.org

[Bug 26744] New: Log changes to extended patron attributes
by bugzilla-daemon＠bugs.koha-community.org 23 Jul '26

23 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26744 Bug ID: 26744 Summary: Log changes to extended patron attributes Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com It looks like changes to a patron's "extended patron attributes" are not logged, when BorrowersLog is on. They should probably be. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 96

[Bug 24911] New: Exception holidays treated as unique holidays in calendar
by bugzilla-daemon＠bugs.koha-community.org 23 Jul '26

23 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24911 Bug ID: 24911 Summary: Exception holidays treated as unique holidays in calendar Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Holidays Assignee: koha-bugs(a)lists.koha-community.org Reporter: emmi.takkinen(a)outlook.com QA Contact: testopia(a)bugs.koha-community.org When exception holiday is made it's still treated as unique holiday. Only days that aren't holidays but are included in the range of "Generate exceptions on a range of dates" are exceptions. To test: 1. Create holidays on a range e.g 23-24/3 2. Create exceptions on a range of 24-25/3 3. When editing: => 24/3 has label "Unique holiday" and is listed both in "Unique holidays" and "Exception holidays" lists => 25/3 has label "Holiday exception" and is listed only in "Exception holidays" Problems this is causing: 1. If you edit title and description of 24th day, you'll notice from holiday lists that edit only applies to unique holiday. In "Exception holidays" title and description remain the same. 2. When trying to delete 24th, only option "Delete this holiday" is given, not "Delete this exception" as it should. And if you use "Delete this holiday", unique holiday "beneath" exception gets deleted but day remains as exception holiday. Of course "Delete exceptions on range" still works and single exceptions can be deleted with it. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 38338] New: Add support for XOAUTH2 authentication for SMTP servers
by bugzilla-daemon＠bugs.koha-community.org 23 Jul '26

23 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38338 Bug ID: 38338 Summary: Add support for XOAUTH2 authentication for SMTP servers Change sponsored?: --- 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 Both Google and Microsoft have been pushing XOAUTH2 for SMTP AUTH over the traditional basic username/password authentication for some time now and we haven't really had a good answer for Koha admins. For SMTP connections in Koha, we use Email::Sender::Transport::SMTP::Persistent which uses Authen::SASL which uses libsasl2 (if available) or a pure Perl fallback. Out of the box, neither libsasl2 nor Authen::SASL::Perl provides XOAUTH2 support. However, there are a number of SASL plugins out there. I'll explain more in the comments. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 118

[Bug 37054] New: Allow for custom branch colors in the staff interface header search
by bugzilla-daemon＠bugs.koha-community.org 23 Jul '26

23 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37054 Bug ID: 37054 Summary: Allow for custom branch colors in the staff interface header search Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The staff interface includes a green bar at the top of almost every page, #header_search.toptab I have been writing custom JavaScript to color this bar differently per branch. It would be much nice if you could just do this in Koha without JS. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 139

[Bug 39297] New: Show due date on recalls queue if a recalled item is overdue to be returned
by bugzilla-daemon＠bugs.koha-community.org 23 Jul '26

23 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39297 Bug ID: 39297 Summary: Show due date on recalls queue if a recalled item is overdue to be returned Change sponsored?: --- 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: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com If a recalled item is overdue to be returned to the library, the checkout's due date does not show on the recalls queue. This is still useful information. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 11

[Bug 34879] New: ./catalogue/getitem-ajax.pl appears to be unused
by bugzilla-daemon＠bugs.koha-community.org 22 Jul '26

22 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34879 Bug ID: 34879 Summary: ./catalogue/getitem-ajax.pl appears to be unused Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl I can't find any reference to ./catalogue/getitem-ajax.pl in Koha, so I think it could probably be removed. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 41081] New: Link from 856$u points to http://%20%20%20%20
by bugzilla-daemon＠bugs.koha-community.org 22 Jul '26

22 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41081 Bug ID: 41081 Summary: Link from 856$u points to http://%20%20%20%20 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: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl http://%20%20%20%20 We should not provide such useless links. The field only contained four spaces. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 39296] New: Provide a template plugin to return MARC::Record for MARCXML metadata
by bugzilla-daemon＠bugs.koha-community.org 22 Jul '26

22 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39296 Bug ID: 39296 Summary: Provide a template plugin to return MARC::Record for MARCXML metadata Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org ExtractValue() is a useful MySQL function but it's limited in what it can do. Sometimes, you want to do reporting off a more nuanced understanding of MARC. I had thought about exposing XML::LibXML::Document and XML::LibXML::XPathContext objects, but they're too powerful/vulnerable to abuse. Instead, I decided that MARC::Record should give all the power we need while not upsetting the status quo or security (after all, we already allow access to MARC::Record objects via $biblio objects in Templates). In this case, you fetch the whole "metadata" blob from the database in your report, and you transform it using a template using Koha::Template::Plugin::KohaMarcRecord It lets you perform more advanced reporting using the full MARC record. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 20

[Bug 35471] New: Automatically select child MARC framework when adding child records
by bugzilla-daemon＠bugs.koha-community.org 22 Jul '26

22 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35471 Bug ID: 35471 Summary: Automatically select child MARC framework when adding child records Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: lari.taskula(a)hypernova.fi QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Some libraries create their own MARC frameworks for component/child records. When adding a child record through host record, Koha currently selects the default MARC framework and a librarian must manually change to the child record framework. This Bug adds a parent-child relationship to MARC frameworks and aims to skip the manual step of selecting child record framework. The goal is to automatically select child MARC framework when adding child record through the host record. To reproduce problem: Administration -> MARC bibliographic framework 1. Create framework with frameworkcode "A" 2. Create framework with frameworkcode "A-child" Record view 1. Save record with framework "A" 2. Navigate to a record 3. Click "+ New", a drop-down opens 4. Click "New child record" 5. After add biblio form opens, click "Settings" 6. Observe default framework selected 7. You must manually select "A-child framework" After this change, To test: Administration -> MARC bibliographic framework 1. Create framework with frameworkcode "A" 2. Create framework with frameworkcode "A-child" 3. Set "A" as "A-child" 's parent framework Record view 1. Save record with framework "A" 2. Navigate to a record 3. Click "+ New", a drop-down opens 4. Click "New child record" 5. After add biblio form opens, click "Settings" 6. Observe "A-child" framework automatically selected -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 55

[Bug 40646] New: ‘Patron account expiry’ message selections un-set when switching 'Enforce patron account expiry notice' from Yes to No
by bugzilla-daemon＠bugs.koha-community.org 22 Jul '26

22 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40646 Bug ID: 40646 Summary: ‘Patron account expiry’ message selections un-set when switching 'Enforce patron account expiry notice' from Yes to No Change sponsored?: --- Product: Koha Version: 25.05 Hardware: All OS: All Status: NEW Severity: normal 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 With 30301, the ‘Patron account expiry’ message line doesn't show in 'Default messaging preferences for this patron category' if 'Enforce patron account expiry notice' is set to Yes. This means that if the notice is being enforced and the library needs to edit its default preferences, they have to switch 'Enforce patron account expiry notice' to No, click Save, and then open the category back up for editing. However, switching 'Enforce patron account expiry notice' from Yes to No un-sets the existing preferences rather than just showing existing selections for editing. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11