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

[Bug 40392] New: Staff without create_public_lists can create public list from search results
by bugzilla-daemon＠bugs.koha-community.org 24 Apr '26

24 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40392 Bug ID: 40392 Summary: Staff without create_public_lists can create public list from search results Change sponsored?: --- Product: Koha Version: 24.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Lists Assignee: koha-bugs(a)lists.koha-community.org Reporter: sbrown(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl In 24.11, staff can create public lists from search results even if they don't have the create_public_lists permission put in place by Bug 13888 - 'Lists' permission should allow/disallow using the lists module in staff. To recreate: -Find or create a staff member with no permissions from the lists group -While logged in as that staff member, perform a catalog search, select the checkboxes on multiple search results, and click the 'Add to list' button -Select the 'New list' option -Note the option to set the new list to public or private - set to 'Public' -Go to Lists, and note that no Public lists tab shows (so you can't see the list you just created) -Next, log in as a staff member with edit_public_list_contents -Go to Lists, and note that the list created by the permission-less staff member shows up in Public lists -Note that the list is also visible in the OPAC -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 40099] New: Default HOLD and HOLDDGST notices should include expiration date
by bugzilla-daemon＠bugs.koha-community.org 24 Apr '26

24 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40099 Bug ID: 40099 Summary: Default HOLD and HOLDDGST notices should include expiration date Change sponsored?: --- Product: Koha Version: Main Hardware: PC OS: Windows Status: NEW Severity: enhancement Priority: P1 - high Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: hebah(a)bywatersolutions.com A common adjustment to the default hold pickup notices is to include when the patron should pick them up by; especially with branches able to configure the hold expiration via circ rule, it would be nice if that was already in the default notice. Maybe even set to use KohaDate format while we're wishing here. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 40260] New: HOLDDGST doen't work for print
by bugzilla-daemon＠bugs.koha-community.org 24 Apr '26

24 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40260 Bug ID: 40260 Summary: HOLDDGST doen't work for print 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: marion.durand(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Currently, when a patron chooses to receive digest only notification for hold filled but have no email address, Koha fall back on a print notification. This notification is using the HOLD template, and the request to receive digest is ignored. Multiple notification will be generated if multiple holds are filled. This seems due to the code around https://github.com/Koha-Community/Koha/blob/main/C4/Reserves.pm#L1929 in Koha/C4/Reserves.pm function _koha_notify_reserve #Making sure that a print notification is sent if no other transport types can be utilized. if ( !$notification_sent ) { &$send_notification( 'print', 'HOLD' ); } To reproduce : 1- Choose a borrower, make sure it has : - no email address - patron messaging prefereces : Hold filled : Email and Digests only 2-Create 2 holds for this borrower 3- Checkin document for these holds and confirm the hold each time 4- Go back to the patron page, on the Notices tab, 2 print notification are generated. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 39019] New: Do not repeat content in CHECKOUT, CHECKIN, and HOLDDGST notices when digest tags are omitted
by bugzilla-daemon＠bugs.koha-community.org 24 Apr '26

24 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39019 Bug ID: 39019 Summary: Do not repeat content in CHECKOUT, CHECKIN, and HOLDDGST notices when digest tags are omitted Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The CHECKOUT, CHECKIN, and HOLDDGST notices assume some content will appear in the notice once, while other content will be generated per item. The content to be repeated gets wrapped in a set of dashed lines that I called "digest tags" in the bug title. Like: Hey Patron, These books got checked out: ---- [% biblio.title %] ---- While a full list of titles works well in an email, it can get prohibitively long in an SMS, so some libraries prefer a single static line for their SMS notice. However, if one fully omits those digest tags Koha will repeat the entire notice per item. If no digest tags are included in the template, Koha should not repeat any of the content on subsequent items. To recreate: 1: Edit the CHECKOUT notice to read: Test ---- ---- 2: check two items out to a patron set to receive CHECKOUT notices 3: confirm their notice says just "Test" 4: Edit the checkout notice to read: Test 5: check two items out to a different patrons set to receive CHECKOUT notices 6: confirm their notice says "TestTest" -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 26573] New: Limit patron attribute types to more than one patron category
by bugzilla-daemon＠bugs.koha-community.org 23 Apr '26

23 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26573 Bug ID: 26573 Summary: Limit patron attribute types to more than one patron category 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: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Currently, Koha doesn't allow to limit a patron attribute type to more than one patron category. Let's say I have a patron attribute type STUDENTID, and I want to limit this attribute to the categories "undergrad students" and "grad students". I have to create two different patron attribute types. To replicate: 1) Go to Administration > Patron attribute types 2) Create a new patron attribute 3) Note that the "Category" field is a dropdown and you can't choose more than one patron category to assign this attribute type to. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 91

[Bug 29000] New: Create a display of patrons with permissions
by bugzilla-daemon＠bugs.koha-community.org 23 Apr '26

23 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29000 Bug ID: 29000 Summary: Create a display of patrons with permissions Change 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: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Actually it is hard to find which patrons have which permissions. It can lead to mistakes and security issues. I've created a POC plugin : https://github.com/biblibre/koha-plugin-users-with-permissions Maybe permissions could be displayed in patrons search table. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 39250] New: Add archive_purchase_suggestions.pl to cron.daily commented
by bugzilla-daemon＠bugs.koha-community.org 23 Apr '26

23 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39250 Bug ID: 39250 Summary: Add archive_purchase_suggestions.pl to cron.daily commented Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz A commented cron job reminds admins of its existence and potential use. It can be easily enabled automatically with a sed statement in a Docker file or so. This patch deals with archive_purchase_suggestions.pl (which came with 20.05) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 31736] New: Context for translation: "All"
by bugzilla-daemon＠bugs.koha-community.org 23 Apr '26

23 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31736 Bug ID: 31736 Summary: Context for translation: "All" 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: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr "All" is used all over Koha, and refers to different things. In French, those different things have different genders and the "All" must be in that gender ("tous" for "male-gendered" things and "toutes" for "female-gendered" things). In fr-CA-staff-prog, it says "All" is used in these places #: koha-tmpl/intranet-tmpl/prog/en/modules/acqui/invoices.tt:313 #: koha-tmpl/intranet-tmpl/prog/en/modules/acqui/invoices.tt:380 #: koha-tmpl/intranet-tmpl/prog/en/modules/acqui/parcel.tt:347 #: koha-tmpl/intranet-tmpl/prog/en/modules/admin/columns_settings.tt:121 #: koha-tmpl/intranet-tmpl/prog/en/modules/admin/columns_settings.tt:123 #: koha-tmpl/intranet-tmpl/prog/en/modules/admin/smart-rules.tt:208 #: koha-tmpl/intranet-tmpl/prog/en/modules/admin/smart-rules.tt:216 #: koha-tmpl/intranet-tmpl/prog/en/modules/admin/smart-rules.tt:387 #: koha-tmpl/intranet-tmpl/prog/en/modules/admin/smart-rules.tt:396 #: koha-tmpl/intranet-tmpl/prog/en/modules/admin/smart-rules.tt:918 #: koha-tmpl/intranet-tmpl/prog/en/modules/admin/smart-rules.tt:939 #: koha-tmpl/intranet-tmpl/prog/en/modules/catalogue/itemsearch.tt:45 #: koha-tmpl/intranet-tmpl/prog/en/modules/circ/view_holdsqueue.tt:247 #: koha-tmpl/intranet-tmpl/prog/en/modules/circ/view_holdsqueue.tt:254 #: koha-tmpl/intranet-tmpl/prog/en/modules/circ/view_holdsqueue.tt:261 #: koha-tmpl/intranet-tmpl/prog/en/modules/circ/view_holdsqueue.tt:268 #: koha-tmpl/intranet-tmpl/prog/en/modules/members/readingrec.tt:57 #: koha-tmpl/intranet-tmpl/prog/en/modules/onboarding/onboardingstep5.tt:63 #: koha-tmpl/intranet-tmpl/prog/en/modules/onboarding/onboardingstep5.tt:74 #: koha-tmpl/intranet-tmpl/prog/en/modules/onboarding/onboardingstep5.tt:86 #: koha-tmpl/intranet-tmpl/prog/en/modules/reports/acquisitions_stats.tt:203 #: koha-tmpl/intranet-tmpl/prog/en/modules/reports/acquisitions_stats.tt:248 #: koha-tmpl/intranet-tmpl/prog/en/modules/reports/acquisitions_stats.tt:263 #: koha-tmpl/intranet-tmpl/prog/en/modules/reports/cash_register_stats.tt:111 #: koha-tmpl/intranet-tmpl/prog/en/modules/reports/dictionary.tt:116 #: koha-tmpl/intranet-tmpl/prog/en/modules/reports/guided_reports_start.tt:245 #: koha-tmpl/intranet-tmpl/prog/en/modules/reports/guided_reports_start.tt:259 #: koha-tmpl/intranet-tmpl/prog/en/modules/reports/guided_reports_start.tt:887 #: koha-tmpl/intranet-tmpl/prog/en/modules/reports/guided_reports_start.tt:1494 #: koha-tmpl/intranet-tmpl/prog/en/modules/reports/itemslost.tt:152 #: koha-tmpl/intranet-tmpl/prog/en/modules/reports/itemslost.tt:156 #: koha-tmpl/intranet-tmpl/prog/en/modules/reports/itemslost.tt:165 #: koha-tmpl/intranet-tmpl/prog/en/modules/reports/itemslost.tt:179 #: koha-tmpl/intranet-tmpl/prog/en/modules/serials/checkexpiration.tt:50 #: koha-tmpl/intranet-tmpl/prog/en/modules/serials/serials-search.tt:281 #: koha-tmpl/intranet-tmpl/prog/en/modules/serials/serials-search.tt:396 #: koha-tmpl/intranet-tmpl/prog/en/modules/serials/serials-search.tt:415 #: koha-tmpl/intranet-tmpl/prog/en/modules/serials/subscription-bib-search.tt:25 #: koha-tmpl/intranet-tmpl/prog/en/modules/serials/subscription-bib-search.tt:37 #: koha-tmpl/intranet-tmpl/prog/en/modules/tools/additional-contents.tt:135 #: koha-tmpl/intranet-tmpl/prog/en/modules/tools/marc_modification_templates.tt:226 #: koha-tmpl/intranet-tmpl/prog/en/modules/tools/viewlog.tt:217 #: koha-tmpl/intranet-tmpl/prog/en/modules/tools/viewlog.tt:219 #: koha-tmpl/intranet-tmpl/prog/en/modules/tools/viewlog.tt:238 #: koha-tmpl/intranet-tmpl/prog/en/modules/tools/viewlog.tt:240 #: koha-tmpl/intranet-tmpl/prog/en/modules/tools/viewlog.tt:268 #: koha-tmpl/intranet-tmpl/prog/en/modules/tools/viewlog.tt:270 #: koha-tmpl/intranet-tmpl/prog/en/includes/additional-fields-entry.inc:12 #: koha-tmpl/intranet-tmpl/prog/en/includes/av-build-dropbox.inc:16 #: koha-tmpl/intranet-tmpl/prog/en/includes/patron-search.inc:247 #: koha-tmpl/intranet-tmpl/prog/en/includes/subscriptions-search.inc:33 #: koha-tmpl/intranet-tmpl/prog/en/includes/str/tinymce_i18n.inc:2 We should add context so that translators know what that "All" refers to. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 100

[Bug 40508] New: Set maxlength in marc21_framework_DEFAULT.yml
by bugzilla-daemon＠bugs.koha-community.org 22 Apr '26

22 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40508 Bug ID: 40508 Summary: Set maxlength in marc21_framework_DEFAULT.yml Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor 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 By explicitly setting maxlength in marc21_framework_DEFAULT.yml, we can change the default maxlength for fields in the default framework (and to a degree the ACQ framework). See Bug 40471 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 20

[Bug 40471] New: Long barcodes in "Add item" throw 500 error
by bugzilla-daemon＠bugs.koha-community.org 22 Apr '26

22 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40471 Bug ID: 40471 Summary: Long barcodes in "Add item" throw 500 error Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Cataloging 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 If you try to enter a very long barcode for an item in the "Add item" screen, you'll get a 500 error and the following in the logs: [WARN] DBIx::Class::Storage::DBI::_dbh_execute(): DBI Exception: DBD::mysql::st execute failed: Data too long for column 'barcode' at row 1 at /kohadevbox/koha/Koha/Object.pm line 174 It should be trivial for us to add length limit checks in the HTML and the Perl. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3