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

[Bug 38203] New: Split the purpose of RENEWAL and AUTO_RENEWALS_DGST notices.
by bugzilla-daemon＠bugs.koha-community.org 17 Jan '26

17 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38203 Bug ID: 38203 Summary: Split the purpose of RENEWAL and AUTO_RENEWALS_DGST notices. Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: r.delahunty(a)arts.ac.uk QA Contact: testopia(a)bugs.koha-community.org As bug 29382 points out RENEWAL is sent in parallel with AUTO_RENEWALS_DGST when the autorenewals script runs providing message preferences are set (and RenewalSendNotice is enabled… not mentioned in that bug). We recently enabled AllowRenewalLimitOverride and I configured RENEWAL to use TT code to send appropriately worded notices for renewals of interlibrary loans, notforloan items issued, and for other loan items manually renewed. My (wrong) expectation was that the DGST notice would go out from 01:30 when our autorenewals script runs, and the RENEWAL would go out only and whenever an item was manually renewed. If auto-renewal is enabled then we are wasting useful functionality that could use RENEWAL to notify of (perhaps special cases of) manual renewal if the purpose of the two notices were separated. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 39014] New: Storing a guarantee fails due to TrackLastPatronActivityTriggers "creating a patron"
by bugzilla-daemon＠bugs.koha-community.org 16 Jan '26

16 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39014 Bug ID: 39014 Summary: Storing a guarantee fails due to TrackLastPatronActivityTriggers "creating a patron" Change sponsored?: --- 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: lmstrand(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Adding a new guarantee and storing it fails with "Creating a patron" selected in TrackLastPatronActivityTriggers when guarantors are set to be mandatory. Feature was added in ticket 23486. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 73

[Bug 40980] New: Clicking a search facet without logging in may trigger a cud-login error
by bugzilla-daemon＠bugs.koha-community.org 16 Jan '26

16 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40980 Bug ID: 40980 Summary: Clicking a search facet without logging in may trigger a cud-login error Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: pedro.amorim(a)openfifth.co.uk 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 22

[Bug 40452] New: Vendor in EDIFACT messages is sometimes incorrect before importing invoice
by bugzilla-daemon＠bugs.koha-community.org 16 Jan '26

16 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40452 Bug ID: 40452 Summary: Vendor in EDIFACT messages is sometimes incorrect before importing invoice Change sponsored?: --- Product: Koha Version: 24.11 Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: sbrown(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org For libraries who have EdifactInvoiceImport set to "[Don't] automatically import invoice...", the Vendor shown in EDIFACT messages for invoices is sometimes incorrect while the message is pending import. Once it imports, all order/invoice info is correct, and the Vendor in the EDIFACT messages table updates to the correct vendor. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 38345] New: Remove support for OpenSearch
by bugzilla-daemon＠bugs.koha-community.org 16 Jan '26

16 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38345 Bug ID: 38345 Summary: Remove support for OpenSearch Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Truth is our test suite has been exploding consistently when trying to launch OpenSearch: * https://jenkins.koha-community.org/job/Koha_Main_OS2/ * https://jenkins.koha-community.org/job/Koha_Main_OS1/ This has some precedent discussion on [issue 429](https://gitlab.com/koha-community/koha-testing-docker/-/issues/429) in `KTD` project issues. We are not going to remove it, I guess. But some noise is needed as people using OpenSearch in production don't seem to care we are not being able to run the test suite, so probably promising some 'OpenSearch support' that we cannot guarantee in any way. And if there's a problem with OpenSearch, we (devs) cannot launch a working environment to fix/test. My two cents on this matter. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 67

[Bug 41145] New: Logging patron attributes logs even if there's no changes
by bugzilla-daemon＠bugs.koha-community.org 16 Jan '26

16 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41145 Bug ID: 41145 Summary: Logging patron attributes logs even if there's no changes Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisette(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com Bug 26744 implemented logging for patron extended attributes. If a patron is in a batch import and the attributes are the same, it logs a change even if nothing else changed, thus making the patron logs large and unhelpful. This can be a problem for academic libraries who have automated loading processes to sync patron with their academic systems. Maybe could use the diff, if diff o=n don't log? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 30

[Bug 37796] New: Generated issue has incorrect number in pattern when receiving
by bugzilla-daemon＠bugs.koha-community.org 16 Jan '26

16 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37796 Bug ID: 37796 Summary: Generated issue has incorrect number in pattern when receiving Change sponsored?: --- Product: Koha Version: 24.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: esther.melander(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 170927 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=170927&action=e… Incorrect number on generated issue Discovered while testing Bug 35646 To Replicate 1. Follow Bug 35646 and create a numbering pattern for {MonthName} {Year}. 2. Test the pattern for a 1/month frequency, subscription start date on the first day of the month. See that the numbering pattern increments correctly for the month names and year. 3. Find a serial in the catalog and add a new subscription. 4. On the second page of the subscription configuration, select the numbering pattern for MonthName Year. 5. Test the prediction pattern and see everything increments correctly. 6. Save the subscription. 7. Receive. See the the first issue displays correctly for the month name and year. 8. Mark the issue as arrived and generate the next issue. See the next issue does not have the correct month name and year. (image attached). 9. Mark the next issue Arrived and generate the third issue. The date published and number continue to increment incorrectly. Possibly connected to bug 20653, though this example is not irregular. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 44

[Bug 19704] New: OPACs most popular feature is displaying links to items set to be hidden in the opachiddenitems syspref which gives 404 errors when links are clicked
by bugzilla-daemon＠bugs.koha-community.org 16 Jan '26

16 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19704 Bug ID: 19704 Summary: OPACs most popular feature is displaying links to items set to be hidden in the opachiddenitems syspref which gives 404 errors when links are clicked Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P3 Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: alexbuckley(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org When a library item has multiple bibliographic records and associated items with differing item types (e.g. fiction and express fiction and non-fiction) the Most popular feature is displaying links to items which are set to be hidden in the opachiddenitems syspref. When the user clicks on the link to these items a 404 error is displayed to the user. Therefore the most popular feature is incorrectly displaying links to hidden items. -- You are receiving this mail because: You are watching all bug changes.

1 35

[Bug 17704] New: OAI-PMH compatiblity with Ubuntu Xenial and Debian Stretch
by bugzilla-daemon＠bugs.koha-community.org 16 Jan '26

16 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17704 Bug ID: 17704 Summary: OAI-PMH compatiblity with Ubuntu Xenial and Debian Stretch Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Actually OAI-PMH in Koha uses HTTP::OAI lib from version in Jessie 3.27. This module is not compatible with version 4.03 which is in Ubuntu Xenial and Debian Stretch. You get the error : Can't call method "start_element" on an undefined value at /usr/share/perl5/HTTP/OAI/Response.pm line 114 This is because the method HTTP::OAI::Response::generate() has changed, it needs an argument $driver. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 60

[Bug 30913] New: Show itemtype notforloan with ILS-DI service GetRecords
by bugzilla-daemon＠bugs.koha-community.org 16 Jan '26

16 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30913 Bug ID: 30913 Summary: Show itemtype notforloan with ILS-DI service GetRecords Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org Discovery services like EBSCO's EDS use the GetRecords ILS-DI service, but the "notforloan" there only includes item-level notforloan and not item-type notforloan. In theory, they should use GetAvailability for availability but I can see why they'd use GetRecords since it has so much more information and that way they can do 1 API call instead of 2. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13