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

[Bug 36525] New: Rename Notices and slips tool to Templates
by bugzilla-daemon＠bugs.koha-community.org 02 Feb '26

02 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36525 Bug ID: 36525 Summary: Rename Notices and slips tool to Templates Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org Now that the Notices and slips tool encompasses more than notices and slips, it makes more sense to rename the tool to Templates. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11

[Bug 41696] New: Error handling in additem.pl is too specific and insufficient
by bugzilla-daemon＠bugs.koha-community.org 02 Feb '26

02 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41696 Bug ID: 41696 Summary: Error handling in additem.pl is too specific and insufficient 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: tadeusz(a)sosnierz.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl additem.tt template "humanizes" every error it knows about, and ignores all others. This problem is noted in additem.pl itself (https://gitlab.com/koha-community/Koha/-/blob/166604f9f3938307de6ea5f2530b6…) The way it currently works is that any unhandled failure when adding/editing items fails quietly on the backend, but returns a 200 and shows a successful page to the user (a background job handling the same, but batched edit would fail visibly). The code and the template should be changed so that any caught exception leaves *some* trace in the interface and clearly indicates that an action has failed. (Patch incoming). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 38769] New: Add plugins consent types to OPAC self registration process
by bugzilla-daemon＠bugs.koha-community.org 02 Feb '26

02 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38769 Bug ID: 38769 Summary: Add plugins consent types to OPAC self registration process Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org The new functionality allows plugins to add patron consent types to the system doesn't expose those consent types to the user at self registration time like we do for the data processing consent. We should have that option -- You are receiving this mail because: You are watching all bug changes.

1 13

[Bug 31503] New: Groundwork for 20380 (mail consent)
by bugzilla-daemon＠bugs.koha-community.org 02 Feb '26

02 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31503 Bug ID: 31503 Summary: Groundwork for 20380 (mail consent) Change sponsored?: --- Product: Koha Version: master 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: 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. You are the assignee for the bug.

1 170

[Bug 31533] New: Add opt-in/opt-out flags to patron consents
by bugzilla-daemon＠bugs.koha-community.org 02 Feb '26

02 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31533 Bug ID: 31533 Summary: Add opt-in/opt-out flags to patron consents Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org Part of the 20380 set. Building on top of 31503. While we now only enforce the GDPR consent if the pref is set to Enforced, we leave other consents empty. Which actually is opt-in. They need to go to the consents page and enable the specific consent. If we would add opt-out, we can either add consents for all users or make PatronConsent a bit smarter and only register refusal (opt-out). It feels more consistent to add all consents to the table, and add them too in the self reg process. But when you add a new consent type and mark it as opt-out, we should then populate the table too. Do we also need a Mandatory flag? Historically, we treat the GDPR consent as such. Other consents may not be of that same category. But we might want the user to make an explicit choice there without the same exceptional approach that we use for GDPR. How do we get him on that page? If he arrives there, we can obviously allow saving only when those mandatories are filled.. -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 30968] New: opac-authorites-home.pl still accessible even when OpacAuthorities system preference is turned off
by bugzilla-daemon＠bugs.koha-community.org 02 Feb '26

02 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30968 Bug ID: 30968 Summary: opac-authorites-home.pl still accessible even when OpacAuthorities system preference is turned off Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: wizzyrea(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org When the system preference OpacAuthorities is turned off, the page https://your.library.here/cgi-bin/koha/opac-authorities-home.pl is still accessible and likely shouldn't be. To test: set OpacAuthorities to Don't Allow try to visit https://your.library.here/cgi-bin/koha/opac-authorities-home.pl note that the page is still accessible. Thanks for checking it out! Liz -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 41743] New: AWS Subsription Install Does Not Setup Correctly
by bugzilla-daemon＠bugs.koha-community.org 02 Feb '26

02 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41743 Bug ID: 41743 Summary: AWS Subsription Install Does Not Setup Correctly Initiative type: --- Sponsorship --- status: Product: Koha Version: 25.11 Hardware: Other OS: Linux Status: NEW Severity: major Priority: P5 - low Component: Installation and upgrade (web-based installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: baceman007(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Hello, I subscribed to and used the CloudFormation install option on AWS to install Koha. I made sure my database is connected to my EC2 instance and that all relevant ports are open including 3306. When I try to enter a new record in the catalog, or import a record using the SRU option on the same page I receive the error. "Could not compile /usr/share/koha/intranet/cgi-bin/cataloguing/addbiblio.pl: "prepare_host_field" is not exported by the C4::Biblio module Can't continue after import errors at /usr/share/koha/intranet/cgi-bin/cataloguing/addbiblio.pl line 29. BEGIN failed--compilation aborted at /usr/share/koha/intranet/cgi-bin/cataloguing/addbiblio.pl line 41. at /usr/local/share/perl/5.34.0/CGI/Compile.pm line 144" I tried commenting out the "prepare_host_field" parameter in addbiblio.pl but this setup does not allow me to do so as I do not have permission to modify the file via the AWS setup. Has anyone else run into this issue? How did you solve it? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 41723] New: Library groups needs feature to limit switching libraries within the group
by bugzilla-daemon＠bugs.koha-community.org 02 Feb '26

02 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41723 Bug ID: 41723 Summary: Library groups needs feature to limit switching libraries within the group Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com We've wanted staff to be limited to switching libraries to specific libraries in their group. It makes sense to put a feature in library groups that could limit what libraries they can switch between, if allowed to switch. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 39669] New: Update reserves notices to use Koha::Patron->queue_notice
by bugzilla-daemon＠bugs.koha-community.org 30 Jan '26

30 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39669 Bug ID: 39669 Summary: Update reserves notices to use Koha::Patron->queue_notice Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org Blocks: 37214 This is one of the more challenging cases as C4::Reservers supports Digests and thus uses C4::Message. It would be a good one to build out tests for and enhance the Koha::Patron->enqueue_notice message, allowing for more adoption of messaging preferences and digest functionality. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37214 [Bug 37214] We should migrate to Koha::Patron->queue_notice wherever possible -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 39176] New: Update additional_field_values.record_id to varchar(255)
by bugzilla-daemon＠bugs.koha-community.org 30 Jan '26

30 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39176 Bug ID: 39176 Summary: Update additional_field_values.record_id to varchar(255) 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org In bug 38663 we had to switch from int(11) to varchar(11) so we could properly store branchcode, the primary key for the branches table. In bug 38457 I'm now faced with the same issue of needing to update the field from varchar(11) to varchar(80) to allow for the code field in the account_debit_types table which is a varchar(80) primary key. Looking to the future and how we're starting to add more and more uses of additional fields I think we should pick the largest current primary key field and match that. SELECT t.TABLE_NAME AS table_name, k.COLUMN_NAME AS primary_key_field, CASE WHEN k.CHARACTER_MAXIMUM_LENGTH IS NOT NULL THEN CONCAT(k.DATA_TYPE, '(', k.CHARACTER_MAXIMUM_LENGTH, ')') WHEN k.NUMERIC_PRECISION IS NOT NULL THEN CONCAT(k.DATA_TYPE, '(', k.NUMERIC_PRECISION, ')') ELSE k.DATA_TYPE END AS primary_key_type FROM INFORMATION_SCHEMA.TABLES t JOIN INFORMATION_SCHEMA.COLUMNS k ON t.TABLE_NAME = k.TABLE_NAME AND t.TABLE_SCHEMA = k.TABLE_SCHEMA JOIN INFORMATION_SCHEMA.KEY_COLUMN_USAGE ku ON t.TABLE_NAME = ku.TABLE_NAME AND t.TABLE_SCHEMA = ku.TABLE_SCHEMA AND k.COLUMN_NAME = ku.COLUMN_NAME JOIN INFORMATION_SCHEMA.TABLE_CONSTRAINTS tc ON ku.TABLE_NAME = tc.TABLE_NAME AND ku.TABLE_SCHEMA = tc.TABLE_SCHEMA AND ku.CONSTRAINT_NAME = tc.CONSTRAINT_NAME WHERE t.TABLE_SCHEMA = DATABASE() AND tc.CONSTRAINT_TYPE = 'PRIMARY KEY' ORDER BY t.TABLE_NAME; Using the above query, I believe that shows the largest is a varchar(255). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2