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

[Bug 42635] New: Staff interface curbside pickups - improve slots selection
by bugzilla-daemon＠bugs.koha-community.org 19 May '26

19 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42635 Bug ID: 42635 Summary: Staff interface curbside pickups - improve slots selection Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com This patch will copy some of the CSS from the OPAC template in order to improve the style of the curbside pickups slot selection. The patch will also convert the form to a CSS grid-styled form. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 38902] New: Allow holds fine limit (maxoutstanding) to be determined by patron category
by bugzilla-daemon＠bugs.koha-community.org 19 May '26

19 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38902 Bug ID: 38902 Summary: Allow holds fine limit (maxoutstanding) to be determined by patron category Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: raina(a)flo.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The system preference “maxoutstanding” is used to determine when patrons are blocked from making holds in the OPAC. For example, maxoutstanding: Prevent patrons from making holds on the OPAC if they owe more than 5 USD in fines. This is separate from the checkout fine limit (noissuescharge). Currently the maxoutstanding preference is applied to all patrons, and there's no way of changing the value for individual patron categories. Bug 28924 enables checkout fine limit to be set by patron category, but there's no way of changing the value for "maxoutstanding" by patron category, which means that all patron groups will still be blocked from placing holds in the OPAC at the same amount. It would be helpful to be able to determine when patrons should be blocked from making holds in the OPAC by patron category, like bug 28924 does for the checkout fine limit. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 41991] New: Temporarily suspend a plugin method or specific plugin class
by bugzilla-daemon＠bugs.koha-community.org 19 May '26

19 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41991 Bug ID: 41991 Summary: Temporarily suspend a plugin method or specific plugin class Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Plugin architecture Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org This starts from a use case where I do want to suspend a certain item plugin hook for a specific command line process. But I dont want to disable the plugin for all processes. So yes, this requires enough understanding from the admin who does that. My idea is to introduce something similar here to the override_syspref construct. To allow suspending a plugin method or class via an environment variable. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 49

[Bug 41067] New: Patrons can self-register without mandatory patron attribute completed if it's not editable
by bugzilla-daemon＠bugs.koha-community.org 19 May '26

19 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41067 Bug ID: 41067 Summary: Patrons can self-register without mandatory patron attribute completed if it's not editable Initiative type: --- Sponsorship --- status: Product: Koha Version: 25.05 Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: sbrown(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com If an attribute has 'OPAC mandatory' selected but does not have 'Editable in OPAC' checked, the attribute will not appear on the self-registration form. Patrons can still successfully self-register, however. To make this clearer, the description for 'OPAC mandatory' should be updated to remove 'creating or' from 'Check to make this attribute mandatory when creating or editing a patron from the OPAC', *or* a note should be added indicating that 'Editable in OPAC' must also be checked for the attribute to be included on the self-reg form. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21

[Bug 41766] New: Fix POD in search_for_data_inconsistencies.pl
by bugzilla-daemon＠bugs.koha-community.org 19 May '26

19 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41766 Bug ID: 41766 Summary: Fix POD in search_for_data_inconsistencies.pl Initiative type: --- Sponsorship --- status: 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: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz misc/maintenance/search_for_data_inconsistencies.pl has POD that looks like this: =head1 DESCRIPTION Catch data inconsistencies in Koha database * Items with undefined homebranch and/or holdingbranch * Authorities with undefined authtypecodes/authority types * Item types: * if item types are defined at item level (item-level_itypes=specific item), then items.itype must be set else biblioitems.itemtype must be set * Item types defined in items or biblioitems must be defined in the itemtypes table * Invalid MARCXML in bibliographic records * Patrons with invalid category types due to lower and upper age limits * Any date fields in the database (timestamp, datetime, date) set to 0000-00-00 The list is not in POD list syntax, so it is rendered like this: DESCRIPTION Catch data inconsistencies in Koha database * Items with undefined homebranch and/or holdingbranch * Authorities with undefined authtypecodes/authority types * Item types: * if item types are defined at item level (item-level_itypes=specific item), then items.itype must be set else biblioitems.itemtype must be set * Item types defined in items or biblioitems must be defined in the itemtypes table * Invalid MARCXML in bibliographic records * Patrons with invalid category types due to lower and upper age limits * Any date fields in the database (timestamp, datetime, date) set to 0000-00-00 The list should either be indented to render as a sort of "pre formatted text block" or have the proper list syntax with something like "=item *". -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 38755] New: search_for_data_inconsistencies.pl: Fix list of inconsistencies
by bugzilla-daemon＠bugs.koha-community.org 19 May '26

19 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38755 Bug ID: 38755 Summary: search_for_data_inconsistencies.pl: Fix list of inconsistencies 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: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz The relevant POD looks like this: ----------------------------------------------------- =head1 DESCRIPTION Catch data inconsistencies in Koha database * Items with undefined homebranch and/or holdingbranch * Authorities with undefined authtypecodes/authority types * Item types: * if item types are defined at item level (item-level_itypes=specific item), then items.itype must be set else biblioitems.itemtype must be set * Item types defined in items or biblioitems must be defined in the itemtypes table * Invalid MARCXML in bibliographic records * Patrons with invalid category types due to lower and upper age limits * Any date fields in the database (timestamp, datetime, date) set to 0000-00-00 =cut ----------------------------------------------------- perldoc renders the list as running text, which is kind of hard to read. The list should either be formatted with "=item" or indented to be treated as "pre formatted" chunk of text. I would vote for the first option. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 40588] New: Clarify impact of edit_any_item permission when no library groups are defined
by bugzilla-daemon＠bugs.koha-community.org 19 May '26

19 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40588 Bug ID: 40588 Summary: Clarify impact of edit_any_item permission when no library groups are defined Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20256#c342 Per discussion on Bug 20256, the intended behavior is that when no library groups are defined a user with edit_items but not edit_any_item should only be able to edit items with a homebranch matching the user's logged in branch. Koha's doing this successfully, but the permissions and manual aren't clear about what the user should expext. The edit_items permission says: "Edit items (not including items restricted by library group) (edit_items)" The edit_any_item permissions says "Edit any item including items that would otherwise be restricted" The manual says of edit_any_item "This permission grants the ability to edit items belonging to libraries from other library groups." Together, these imply the assumption that item edits are unrestricted *unless* one defines library groups with the "Limit item edits" option set. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 41600] New: javascript-format translation "# of % selected"
by bugzilla-daemon＠bugs.koha-community.org 19 May '26

19 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41600 Bug ID: 41600 Summary: javascript-format translation "# of % selected" Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: translate.koha-community.org Assignee: koha-bugs(a)lists.koha-community.org Reporter: Igor.A.Sychev(a)mail.ru QA Contact: testopia(a)bugs.koha-community.org How do I make a translate? English # of % selected Russian # из % выбранных koha-tmpl/intranet-tmpl/prog/js/categories.js:127 koha-tmpl/intranet-tmpl/prog/js/ill-list-table.js:653 https://translate.koha-community.org/translate/koha/25-11/messages-js/ru/?c… -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 42633] New: Linking to a host item changes the record framework to default
by bugzilla-daemon＠bugs.koha-community.org 19 May '26

19 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42633 Bug ID: 42633 Summary: Linking to a host item changes the record framework to default Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: stalkernoid(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 42580] New: 500 error for patron holds table when using group holds (DisplayAddHoldGroups)
by bugzilla-daemon＠bugs.koha-community.org 19 May '26

19 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42580 Bug ID: 42580 Summary: 500 error for patron holds table when using group holds (DisplayAddHoldGroups) Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, lisette(a)bywatersolutions.com, tomascohen(a)gmail.com If you place a group hold, you get a 500 error when attempting to view the patron's holds table (for both the check out and details sections). To reproduce: 1. Enable the DisplayAddHoldGroups system preference. 2. Search in the staff interface for "perl". 3. Select three items to place a hold on (for example, Programming Perl, CGI programming with Perl, Intermediate Perl). 4. Click the "Place hold" action. 5. Select a patron. 6. Tick the "Treat as hold group" option. 7. Select the pickup locations for the items. 8. Click "Place holds" 9. Go to the patrons account > Details > Holds tab. 10. You get a browser pop-up window/dialogue box with a "Something went wrong when loading the table. 500: Internal Server Error." error, and nothing is displayed in the table when you click OK (says "Loading...") 11. Console error is "DataTables warning: table id=holds-table - Ajax error. For more information about this error, please see https://datatables.net/tn/7" -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3