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

[Bug 42871] New: Show local installable plugins on plugins-home.pl
by bugzilla-daemon＠bugs.koha-community.org 18 Jun '26

18 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42871 Bug ID: 42871 Summary: Show local installable plugins on plugins-home.pl 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: --- There are times where you might have Koha plugins available in a plugin_dir, but you haven't installed the plugin via the CLI. It would be cool to add an option to discover Koha plugins that could be installed. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 25222] New: Add ability to let plugins live in individual subdirectories
by bugzilla-daemon＠bugs.koha-community.org 18 Jun '26

18 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25222 Bug ID: 25222 Summary: Add ability to let plugins live in individual subdirectories 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 >From Tomas: "We really need to put each plugin in its own subdirectory (to identify them individually) and have a metadata file we can refer to." This would make things much more manageable. Right now, plugins get all mixed together in the plugins directory. For example, installing the kitchen sink plugin results in Koha/Plugin/Com/ByWaterSolutions/KitchenSink.pm being created in the plugins directory. Installing CoverFlow will create CoverFlow.pm in the same directory as KitchenSink.pm. There is no reason that plugins cannot be created to install in a subdirectory directly in the kpz file. In that case, the plugins directory would contain something like kitchen-sink/Koha/Plugin/Com/ByWaterSolutions/KitchenSink.pm, while CoverFlow would live in coverflow/Koha/Plugin/Com/ByWaterSolutions/CoverFlow.pm. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 46

[Bug 38198] New: Expired patrons can still make purchase suggestions through OPAC
by bugzilla-daemon＠bugs.koha-community.org 18 Jun '26

18 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38198 Bug ID: 38198 Summary: Expired patrons can still make purchase suggestions through OPAC Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: rkuiper(a)roundrocktexas.gov QA Contact: testopia(a)bugs.koha-community.org We would like to add the ability to block expired patrons from placing purchase suggestions. Maybe add this to the BLOCKEXPIREDPATRONOPACACTION system preference as an option? -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 42179] New: Use Microsoft Graph for Sending Messages
by bugzilla-daemon＠bugs.koha-community.org 18 Jun '26

18 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42179 Bug ID: 42179 Summary: Use Microsoft Graph for Sending Messages 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: brian.pichman(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 196176 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=196176&action=e… patch This changes outbound email delivery via Microsoft Graph using a host-managed Entra application and tenant consent from the Koha staff interface. The goal is to reduce partner setup complexity. The host configures one Microsoft 365 app in sysprefs, and the library admin completes tenant connection by clicking “Connect Microsoft 365” from the SMTP server configuration screen. Main changes: - Add Microsoft Graph as a delivery transport (left room to be expanded on later -- IE one click AWS SES set up for partners could be accomplished this way using API calls that can add domains and share back verification needs) for smtp_servers - Add host-level sysprefs for Graph client ID/client secret - Add tenant connection storage and connection workflow - Add shared connection scope so one tenant connection can be used for all libraries using the server - Add dedicated callback endpoint for Microsoft consent return - Route queued email delivery through Graph when configured Known setup requirements: - Redirect URI must be registered in Entra - App must have Microsoft Graph Mail.Send application permission - Admin consent must be granted This shouldn't conflict with this bug: 38338 as I'm recommending an entirely new layer within smtp_servers.pl. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 42433] New: Cannot hide Home library column from pay-fines-table (Make a payment)
by bugzilla-daemon＠bugs.koha-community.org 17 Jun '26

17 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42433 Bug ID: 42433 Summary: Cannot hide Home library column from pay-fines-table (Make a payment) Initiative type: --- Sponsorship --- status: 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: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com I don't know if this is the same bug as bug 41604 or if it is different. I was trying to hide the "Home library" column from the "Make a payment" table for a library who only has one branch and wishes to simplify the tables and remove useless information (such as the branch, when you only have one). To recreate: 1. Create a manual charge in a patron account 1.1. Go to a patron account (i.e. http://localhost:8081/cgi-bin/koha/members/moremember.pl?borrowernumber=19) 1.2. Go to the Accounting tab 1.3. Click on the Create manual invoice tab 1.4. Enter an amount 1.5. Click Save 2. View the table in the "Make a payment" tab --> There is a "Home library" column 3. Hide the column by default for the table 3.1. Go to Administration > Table settings > Patrons > pay > pay-fines-table 3.2. Check the option "Is hidden by default" for the "home_library" column 3.3. Click Save 4. Go back to the patron's account in Accounting > Make a payment and do CTRL + F5 --> The "Home library" column is still there -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 41317] New: Release team 26.05
by bugzilla-daemon＠bugs.koha-community.org 17 Jun '26

17 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41317 Bug ID: 41317 Summary: Release team 26.05 Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: About Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: david(a)davidnind.com, fridolin.somers(a)biblibre.com, katrin.fischer(a)bsz-bw.de, lucas(a)bywatersolutions.com, martin.renvoize(a)openfifth.co.uk, paul.derscheid(a)lmscloud.de, testopia(a)bugs.koha-community.org, wainuiwitikapark(a)catalyst.net.nz Depends on: 40022 New cycle, new release team. Let's add the new team to the about page. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40022 [Bug 40022] Release team 25.11 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 30

[Bug 5276] subscription end date shouldn't be required / allow indefinite subscriptions
by bugzilla-daemon＠bugs.koha-community.org 17 Jun '26

17 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5276 Angela Berrett <angela.berrett(a)familysearch.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |angela.berrett@familysearch | |.org --- Comment #5 from Angela Berrett <angela.berrett(a)familysearch.org> --- +1 Going to hope this one floats back to the top of the interest pile again. -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 38487] New: Budget permissions need more granularity
by bugzilla-daemon＠bugs.koha-community.org 17 Jun '26

17 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38487 Bug ID: 38487 Summary: Budget permissions need more granularity Change sponsored?: --- Product: Koha Version: 24.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: catrina(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org In a consortia, libraries need to be able to create budgets that cannot be edited by other libraries. However, the permissions in Koha are not granular enough to be able to accommodate that. Even without the budget_manage_all permission, libraries can view ALL budgets from Acquisitions > Administration: Budget (from left navigation). Selecting the green hyperlink returns a "No Fund Found" error (correctly). However, the Action buttons are available and libraries can edit another library's overall budget amount and add funds to that budget. They shouldn't be able to do this without the budget_manage_all permission. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 35811] New: Adding a new item type does not clear cache (causing new type to not show properly in OPAC)
by bugzilla-daemon＠bugs.koha-community.org 17 Jun '26

17 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35811 Bug ID: 35811 Summary: Adding a new item type does not clear cache (causing new type to not show properly in OPAC) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: schodkowy.omegi-0r(a)icloud.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Item type descriptions are cached with cache key of 'itemtype:description:'.$lang, which is used by function C4::Biblio::GetAuthorisedValueDesc, used for example in OPAC during display of item's item type in the details view table: https://github.com/Koha-Community/Koha/blob/3df1cb33c277925b689b1e45c736ea8… The problem is, when a new item type is added, that cache key isn't flushed, meaning the new item type won't be displayed in OPAC, an empty field will be shown instead. Flushing memcached mitigates this issue. The cache key is cleared here during tests for instance: https://github.com/Koha-Community/Koha/blob/3df1cb33c277925b689b1e45c736ea8… I suspect the cache flushing should occur in `admin/itemtypes.pl`, after $op 'add_validate'. However, I'm not sure how to get the list of all languages to purge (and I assume all of them should be purged). I've found code snippet below, but I'm not sure if this approach would be acceptable (after adjusting the regex of course), given this gets cache by `Koha::Cache::Memory::Lite->get_instance` instead of `Koha::Caches->get_instance`... my $memory_cache = Koha::Cache::Memory::Lite->get_instance; for my $k ( $memory_cache->all_keys ) { $memory_cache->clear_from_cache($k) if $k =~ m{^CircRules:}; } I've also found this snippet (I see itemtypes.pl calls ->store, so this gets called too): https://github.com/Koha-Community/Koha/blob/2ce83fc784ad8bc716bd65f14845141… It seems to purge only English, which might be why I experienced the issue that I've experienced. So the question that prevails then is: how do we purge all the used languages? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 24712] New: Use YAML files for some of the update data
by bugzilla-daemon＠bugs.koha-community.org 17 Jun '26

17 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24712 Bug ID: 24712 Summary: Use YAML files for some of the update data 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr Depends on: 13897, 24262 Bug 13897 with bug 24262 refine our translation process for install files converting the old SQL files used in the installer for mandatory and optional data into YAML files and adding processing to allow centralised translation of those files alongside the rest of the translation project. It raises the question, however, of how we should deal with the same data during upgrades. Currently we add the American English values with standard SQL in an atomicupdate file (copied into updatedatabase at push time). I'm envisaging we may be able to do away with the atomicupdates for this type of data insertion during upgrade and replace it with a step inside updatedatabase that pulls the data, translations and all from the yaml files. Opening this bug to discus and attempt such an implementation. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13897 [Bug 13897] Use YAML files for installer data https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24262 [Bug 24262] Translate installer data in YAML format -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 30