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

[Bug 27286] New: Patron picture-upload.pl allows arbitrary file extension during upload
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '26

21 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27286 Bug ID: 27286 Summary: Patron picture-upload.pl allows arbitrary file extension during upload Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: saiful(a)semanticconsulting.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Created attachment 114546 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=114546&action=e… Double extension or wrong extension in picture file upload The IT team has flagged two issues with the picture upload tool (Patron Images feature): 1. The tool allows upload of files with double extension. 2. The tool allows upload of files with arbitrary file extension. In essence, the tool does not validate the image file restriction that is mentioned in the top of upload input tag which is: "Only PNG, GIF, JPEG, XPM formats are supported." -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 20281] New: Allow translating library names for notices/slips
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '26

21 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20281 Bug ID: 20281 Summary: Allow translating library names for notices/slips 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: pasi.kallinen(a)joensuu.fi QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr It should be possible to translate the library names, and it should be possible to use those translated names in notices and slips automatically. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 37025] New: Add CLI tool to generate/delete api keys for a given patron on a Koha instance
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '26

21 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37025 Bug ID: 37025 Summary: Add CLI tool to generate/delete api keys for a given patron on a Koha instance Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: paul.derscheid(a)lmscloud.de QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz I bet this will not immediately go through QA. Please don't hesitate to nitpick. :) Just as a disclaimer, I didn't want any flags, just appropriate positional arguments for the two contexts. That's why it might look unconventional. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 62

[Bug 41086] New: Add a helper method to C4/Scrubber to be able to pass allowed tags back to the template
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '26

21 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41086 Bug ID: 41086 Summary: Add a helper method to C4/Scrubber to be able to pass allowed tags back to the template 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: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org With more scrubber profiles being setup it is important to pass the allowable tags/rules back to the user so they know what HTML they can use when content is scrubbed. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 10

[Bug 39372] New: No way to restrict OPAC users from creating private lists specifically
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '26

21 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39372 Bug ID: 39372 Summary: No way to restrict OPAC users from creating private lists specifically Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Lists 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 There are cases where you want library staff users to create and share lists with OPAC users, but you don't want users to be able to create *any* lists. Koha already has a syspref called OpacAllowPublicListCreation to restrict public list creation, but we also need something like OpacAllowPrivateListCreation to restrict private list creation. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 47

[Bug 35818] New: Message queue cron job vs. system preferences
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '26

21 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35818 Bug ID: 35818 Summary: Message queue cron job vs. system preferences Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: alexander.wagner(a)desy.de QA Contact: testopia(a)bugs.koha-community.org In https://koha-community.org/manual/latest/en/html/cron_jobs.html#notices the note reads: ``` Requires that EnhancedMessagingPreferences be set to ‘Allow’. ``` Howerver, it this seems to be wrong. The queue should be processed regardless of the setting for `Enhanced Messages`. Probably, the Note should go to the next section Advanced notice -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 40977] New: t/00-testcritic.t fails on Debian 13
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '26

21 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40977 Bug ID: 40977 Summary: t/00-testcritic.t fails on Debian 13 Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: victor(a)tuxayo.net QA Contact: testopia(a)bugs.koha-community.org Test plan 1. KOHA_IMAGE=main-bookworm ktd up 2. prove t/00-testcritic.t 3. pass 4. KOHA_IMAGE=main-trixie ktd up 5. prove t/00-testcritic Failed test 'Test::Perl::Critic for "C4/Members/Messaging.pm"' Code before strictures are enabled at line 23, column 1. See page 429 of PBP. (Severity: 5) It can be fixed by adding use strict; or use Modern::Perl; Is that just a forgotten occurrence? Severity = major because it makes the CI fail and hides issues even if not as much as Bug 40680. Maybe critical, I don't know. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 40027] New: Use GitHub workflow to automatically close PRs opened on the Koha repo there
by bugzilla-daemon＠bugs.koha-community.org 20 Apr '26

20 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40027 Bug ID: 40027 Summary: Use GitHub workflow to automatically close PRs opened on the Koha repo there Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Developer documentation Assignee: schodkowy.omegi-0r(a)icloud.com Reporter: schodkowy.omegi-0r(a)icloud.com QA Contact: testopia(a)bugs.koha-community.org CC: koha-bugs(a)lists.koha-community.org This is simply based on: https://github.com/mozilla-firefox/firefox/blob/main/.github/workflows/clos… Automatically redirect users who try to submit a PR at GitHub to instructions on how to submit patches and close the PR. Better experience for potential new developers (since they get immediate feedback, while still in the flow for submitting the patch). The sparse checkout of readme is probably required, so that the gh command knows on what repo to work with. The message text is a combination of the Firefox's text with what people used to write when closing Koha's PRs. I think it should be good enough but of course feel free to share any suggestions for change if you feel like it needs one. TEST PLAN: None honestly. This workflow is proven to work on Firefox's repo. The only change is adding \n newlines to the comment for readability, which I didn't test for whether it works... Otherwise it can only be tested after merging (either to Koha repo or to some dummy test repo if you really want to). -- You are receiving this mail because: You are watching all bug changes. You are on the CC list for the bug.

1 18

[Bug 40449] New: xt/author/valid-templates.t generates warnings
by bugzilla-daemon＠bugs.koha-community.org 20 Apr '26

20 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40449 Bug ID: 40449 Summary: xt/author/valid-templates.t generates warnings Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 40444 those are diag xt/author/valid-templates.t .. 1/3 # excluding template /kohadevbox/koha/koha-tmpl/opac-tmpl/bootstrap/en/includes/opac-bottom.inc because it cannot stand on its own # excluding template /kohadevbox/koha/koha-tmpl/opac-tmpl/bootstrap/en/includes/doc-head-close.inc because it cannot stand on its own # excluding template /kohadevbox/koha/koha-tmpl/opac-tmpl/bootstrap/en/includes/ill/backends/Standard/shared/forms because it cannot stand on its own # excluding template /kohadevbox/koha/koha-tmpl/opac-tmpl/bootstrap/en/includes/ill/backends/Standard/shared/forms/chapter.inc because it cannot stand on its own # excluding template /kohadevbox/koha/koha-tmpl/opac-tmpl/bootstrap/en/includes/ill/backends/Standard/shared/forms/thesis.inc because it cannot stand on its own # excluding template /kohadevbox/koha/koha-tmpl/opac-tmpl/bootstrap/en/includes/ill/backends/Standard/shared/forms/book.inc because it cannot stand on its own # excluding template /kohadevbox/koha/koha-tmpl/opac-tmpl/bootstrap/en/includes/ill/backends/Standard/shared/forms/other.inc because it cannot stand on its own # excluding template /kohadevbox/koha/koha-tmpl/opac-tmpl/bootstrap/en/includes/ill/backends/Standard/shared/forms/journal.inc because it cannot stand on its own # excluding template /kohadevbox/koha/koha-tmpl/opac-tmpl/bootstrap/en/includes/ill/backends/Standard/shared/forms/article.inc because it cannot stand on its own # excluding template /kohadevbox/koha/koha-tmpl/opac-tmpl/bootstrap/en/includes/ill/backends/Standard/shared/forms/resource.inc because it cannot stand on its own # excluding template /kohadevbox/koha/koha-tmpl/opac-tmpl/bootstrap/en/includes/ill/backends/Standard/shared/forms/dvd.inc because it cannot stand on its own # excluding template /kohadevbox/koha/koha-tmpl/opac-tmpl/bootstrap/en/includes/ill/backends/Standard/shared/forms/conference.inc because it cannot stand on its own # excluding template /kohadevbox/koha/koha-tmpl/intranet-tmpl/prog/en/includes/ill/backends/Standard/shared/forms because it cannot stand on its own # excluding template /kohadevbox/koha/koha-tmpl/intranet-tmpl/prog/en/includes/ill/backends/Standard/shared/forms/chapter.inc because it cannot stand on its own # excluding template /kohadevbox/koha/koha-tmpl/intranet-tmpl/prog/en/includes/ill/backends/Standard/shared/forms/thesis.inc because it cannot stand on its own # excluding template /kohadevbox/koha/koha-tmpl/intranet-tmpl/prog/en/includes/ill/backends/Standard/shared/forms/book.inc because it cannot stand on its own # excluding template /kohadevbox/koha/koha-tmpl/intranet-tmpl/prog/en/includes/ill/backends/Standard/shared/forms/other.inc because it cannot stand on its own # excluding template /kohadevbox/koha/koha-tmpl/intranet-tmpl/prog/en/includes/ill/backends/Standard/shared/forms/journal.inc because it cannot stand on its own # excluding template /kohadevbox/koha/koha-tmpl/intranet-tmpl/prog/en/includes/ill/backends/Standard/shared/forms/article.inc because it cannot stand on its own # excluding template /kohadevbox/koha/koha-tmpl/intranet-tmpl/prog/en/includes/ill/backends/Standard/shared/forms/resource.inc because it cannot stand on its own # excluding template /kohadevbox/koha/koha-tmpl/intranet-tmpl/prog/en/includes/ill/backends/Standard/shared/forms/dvd.inc because it cannot stand on its own # excluding template /kohadevbox/koha/koha-tmpl/intranet-tmpl/prog/en/includes/ill/backends/Standard/shared/forms/conference.inc because it cannot stand on its own Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40444 [Bug 40444] Add a test to ensure all Perl test files use Test::NoWarnings -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 16786] New: No longer to add multiple emails addresses in an email field
by bugzilla-daemon＠bugs.koha-community.org 20 Apr '26

20 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16786 Bug ID: 16786 Summary: No longer to add multiple emails addresses in an email field Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Previous to Koha 3.22, it was possible to enter multiple comma separated email addresses in a patron's email field. This allowed a patron to opt to receive a copy of any given email in more than one address! Now the email validation disallows this, but there is no technical reason to disallow it as far as I am aware. The email validator should be updated to supported multiple comma separated email addresses in any given email field. -- You are receiving this mail because: You are watching all bug changes.

1 28