May 2024 - Koha-bugs - lists.koha-community.org

[Bug 33218] New: Should the 'Main contact method' field override the AutoEmailPrimaryAddress at patron-level?
by bugzilla-daemon＠bugs.koha-community.org 27 Jan '26

27 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33218 Bug ID: 33218 Summary: Should the 'Main contact method' field override the AutoEmailPrimaryAddress at patron-level? 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: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org While I was working on bug 33191 et al. I asked myself if the 'Main contact method' drop down was somehow linked to AutoEmailPrimaryAddress, as a way to override the system preference at patron level. I was told no, but I think it would make sense... If for example AutoEmailPrimaryAddress is set to 'home' (primary email), and a patron chooses their work email as their main contact method, there is no way to send email notices to their work email, is there? I would see it as something like the CheckPrevCheckouts, where it is possible to override the syspref at the patron-level. Not sure how it would work with custom values as introduced in bug 31498, however... -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 22832] New: Require plugins to specify the methods they implement
by bugzilla-daemon＠bugs.koha-community.org 27 Jan '26

27 Jan '26

1 18

[Bug 25316] New: Koha::Plugin::Base should automatically find plugin metadata and store it in the database for retreival
by bugzilla-daemon＠bugs.koha-community.org 27 Jan '26

27 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25316 Bug ID: 25316 Summary: Koha::Plugin::Base should automatically find plugin metadata and store it in the database for retreival 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org We should store plugin metadata in the database for easy retrieval. Koha::Plugins::Base::get_metadata should check the database for its own metadata. If it doesn't find anything in the database, it should check itself for a $metadata global as it does now, but if one does not exist, it should then check for a companion PLUGIN.yml file ( from Bug 24631 ) in the bundle_path() and load the metadata from there. In either case it should then be stored in the database. InstallPlugins() should force the plugins metadata to be updated from source to the database, as the plugin metadata may ( and should ) have changed in the updated plugin. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 23975] New: Add ability to search and install plugins from GitHub
by bugzilla-daemon＠bugs.koha-community.org 27 Jan '26

27 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23975 Bug ID: 23975 Summary: Add ability to search and install plugins from GitHub Change sponsored?: --- Product: Koha Version: unspecified 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org It would be nice to be able to search and install plugins directly from GitHub ( and GitLab if possible ). This would make it easier to verify the authenticity of plugins and make discovering new plugins easier as well as making installation of plugins simpler. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 81

[Bug 24631] New: Plugin metadata should be outside the main class
by bugzilla-daemon＠bugs.koha-community.org 27 Jan '26

27 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24631 Bug ID: 24631 Summary: Plugin metadata should be outside the main class Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Plugin architecture Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Currently, plugin metadata is stored within the main plugin class file but this means one has to load the class to read it. We should pull this data out into a manifest/metadata file in a standard format (JSON/YAML) to allow simpler external parsing. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 91

[Bug 25174] New: Plugins that fail to load should still display in the plugins table, but with an error indicator
by bugzilla-daemon＠bugs.koha-community.org 27 Jan '26

27 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25174 Bug ID: 25174 Summary: Plugins that fail to load should still display in the plugins table, but with an error indicator 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Right now, if a plugin does not load, for example, because it relies on a Koha subroutine that doesn't exist in this version of Koha, it simply disappears from the table of installed plugins. We should instead allow it to show in the table with and icon that indicates it is not loadable, and perhaps the error message from the attempt to load it. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 34027] New: Add functionality to cleanup_database.pl to purge action logs in batches
by bugzilla-daemon＠bugs.koha-community.org 27 Jan '26

27 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34027 Bug ID: 34027 Summary: Add functionality to cleanup_database.pl to purge action logs in batches Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Some of our libraries did not have the --logs argument in place for cleanup_database.pl and their action logs tables have grown very large (millions of rows) and taking up lots of space on the disk. We need to be able to clear these logs incrementally (in batches), as the sheer size of the delete query has overloaded the server. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 30

[Bug 33519] New: Update description of ILS-DI:AuthorizedIPs
by bugzilla-daemon＠bugs.koha-community.org 27 Jan '26

27 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33519 Bug ID: 33519 Summary: Update description of ILS-DI:AuthorizedIPs Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration 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 After bug 24537, "we can use addresses in a variety of formats [in ILS-DI:AuthorizedIPs]. This includes 127.0.0.1, 192.168.1.0/24, 10.0.0, and so on." It would be nice if this was reflected in the description of the syspref. This syspref used to take a plain list of IPs, so if you missed it in the release notes, there is no hint that the functionality has been changed/enhanced. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 36682] New: Replace yarn with pnpm
by bugzilla-daemon＠bugs.koha-community.org 26 Jan '26

26 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36682 Bug ID: 36682 Summary: Replace yarn with pnpm Change sponsored?: --- Product: Koha Version: unspecified 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: me(a)paulderscheid.xyz QA Contact: testopia(a)bugs.koha-community.org The idea is to deprecate yarn in favor of pnpm as it offers - better disk space efficiency - speed (compared to yarn) - deterministic installs - stricter dependency isolation -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 25090] New: Customize destination for OPAC self registration vertification email
by bugzilla-daemon＠bugs.koha-community.org 26 Jan '26

26 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25090 Bug ID: 25090 Summary: Customize destination for OPAC self registration vertification email Change sponsored?: 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: alexbuckley(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Currently libraries can use the PatronSelfRegistrationVerifyByEmail syspref to restrict self registering users from being able to access the OPAC after registering until they have acknowledged the email sent by Koha. If that syspref is disabled then self registering users will be able to login to the OPAC straight after filling in the self registration form. It would be good if libraries had further control over what users can login to the OPAC. Why? Many online resources (e.g. 3rd party database access) require only OPAC login to be able to be accessed. Special libraries may want to limit OPAC login access only to those users within their organisation as these online resources do charge the libraries on a usage basis. How can further control over what users trying to self register can access the OPAC be achieved whilst keeping the default, current Koha behaviour? 1. Ensure 'PatronSelfRegistrationVerifyByEmail' syspref is set to 'Require' 2. Add a new syspref 'PatronSelfRegistrationVerificationRecipient'(This dropdown syspref would allow libraries to choose): * email address of branch * KohaAdminEmailAddress * Requesting user If email address of branch or KohaAdminEmailAddress then the verification email generated after the user has submitted the registration form will go to the library. The email will contain some details entered by the patron, so the library can confirm if they are happy that the registering user is able to login to the OPAC then they will acknowledge the email (click on the opac-registration-verify.pl link) which will actually make the patron account. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 89