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

[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 17593] New: Extend circulation rules to include shelving location
by bugzilla-daemon＠bugs.koha-community.org 20 Apr '26

20 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17593 Bug ID: 17593 Summary: Extend circulation rules to include shelving location Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: stefan.berndtsson(a)ub.gu.se QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com We are in the process of moving over to Koha, and are still trying to manage all the details around this. Circulation rules are a big thing we have to tackle here. At the moment, we have multiple libraries, and within each library we have both open and closed stacks as well as multiple other segmentations, all specified as shelving locations (authorized value LOC). These locations are not always governed by the same set of rules, so it would be very helpful if the system could support LOC as a circulation rule condition alongside library, patron category and item type. >From doing a fairly brief look at the code, it seems GetIssuingRule and GetLoanLength in C4/Circulation.pm are the main points where the ruleset is retreived. There will of course be all the places calling these two functions, as well as database management parts to consider. If we were to develop some sort of extension to these rules, what would be an appropriate approach? It should certainly be an option to turn on to be used, but should we consider LOC as a starting point, or should LOC just be one many possible choices in the configuration? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 11

[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

[Bug 24535] New: Add the ability to have longer barcodes than 20 digits
by bugzilla-daemon＠bugs.koha-community.org 20 Apr '26

20 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24535 Bug ID: 24535 Summary: Add the ability to have longer barcodes than 20 digits Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: nick(a)bywatersolutions.com Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Currently, in Koha, an item's barcode can only be up to 20 digits, it would be nice to increase this value to possibly a higher number such as 32. Koha recently increased the patron's barcode length to 32 and it was helpful to libraries. -- You are receiving this mail because: You are watching all bug changes.

1 18

[Bug 38723] New: Move widely used TT plugins to LOAD_PLUGINS
by bugzilla-daemon＠bugs.koha-community.org 20 Apr '26

20 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38723 Bug ID: 38723 Summary: Move widely used TT plugins to LOAD_PLUGINS Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: baptiste.wojtkowski(a)biblibre.com, david(a)davidnind.com, fridolin.somers(a)biblibre.com, jonathan.druart(a)gmail.com, katrin.fischer(a)bsz-bw.de, kyle(a)bywatersolutions.com, m.de.rooy(a)rijksmuseum.nl, martin.renvoize(a)ptfs-europe.com, nick(a)bywatersolutions.com, oleonard(a)myacpl.org, testopia(a)bugs.koha-community.org, tomascohen(a)gmail.com Depends on: 37634 Whilst QAing bug 37634 it felt silly to me to be adding [% USE Koha %] to so many templates.. there must be a better way. So I added a follow-up.. but then we discussed it on chat and decided we could expand the scope a bit further from 'Koha' to 'Koha', 'Asset' and 'raw' plugins.. the three most commonly called TT plugins in Koha templates. So.. to keep things easy for RMaints, I've opted to move my cleanup patches here. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37634 [Bug 37634] Missing "USE Koha" causes JS errors and missing "Last patron" menu -- You are receiving this mail because: You are watching all bug changes.

1 16

[Bug 39427] New: Searching lists table by owner can only enter firstname or surname
by bugzilla-daemon＠bugs.koha-community.org 20 Apr '26

20 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39427 Bug ID: 39427 Summary: Searching lists table by owner can only enter firstname or surname 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl C4/Utils/DataTables/VirtualShelves.pm 61 if ( defined $shelfname and $shelfname ne '' ) { 62 push @where_strs, 'shelfname LIKE ?'; 63 push @args, "%$shelfname%"; 64 } We don't split the argument, so only either of the fields can be searched -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 29

[Bug 37604] New: Give skip_open_orders checkbox an ID in batch record deletion template
by bugzilla-daemon＠bugs.koha-community.org 20 Apr '26

20 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37604 Bug ID: 37604 Summary: Give skip_open_orders checkbox an ID in batch record deletion template Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl This is so that clicking on the label will put the cursor focus on the checkbox. At the moment the label and the checkbox are not semantically 'linked' without an ID -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 22

[Bug 39930] New: Saved configuration states on tables cause extra columns to show
by bugzilla-daemon＠bugs.koha-community.org 20 Apr '26

20 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39930 Bug ID: 39930 Summary: Saved configuration states on tables cause extra columns to show Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: jrobb(a)sekls.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com This is hard to replicate but I did come across it on main in ktd. When "Save configuration state on page change" is enabled for a table, after an amount of time or some undetermined action, the table settings seem to go wonky. On the issues table at circ/circulation.pl for example, the grouping breaks and the sort_order and todays_or_previous_checkouts get revealed where they should be perma-hidden: Table showing columns that shouldn't be there: https://snipboard.io/TYL3Oe.jpg Table settings for that table: https://snipboard.io/kU7Tiw.jpg Column settings from local storage: https://snipboard.io/6aS8e4.jpg The steps that led to this were: 1. Set AlwaysLoadCheckoutsTable syspref to Do 2. Check out an item (39999000018516) to a patron (42) 3. Close the tab for a while (I didn't log out, just closed then reopened a few hours later) 4. Pull up the patron, extra mysterious columns have appeared This isn't isolated to the checkouts table, as we've come across it with saved reports and other tables that get saved states as well. Unchecking the save state box seems to avoid the problem. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 34

[Bug 39987] New: Batch item deletion breadcrumb uses wrong link
by bugzilla-daemon＠bugs.koha-community.org 20 Apr '26

20 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39987 Bug ID: 39987 Summary: Batch item deletion breadcrumb uses wrong link Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Currently it points to: http://localhost:8081/cgi-bin/koha/tools/batchMod.pl Should be: http://localhost:8081/cgi-bin/koha/tools/batchMod.pl?del=1 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 38906] New: REGEXP_REPLACE not in MySQL < 5.8 DB update 24.06.00.064 fails
by bugzilla-daemon＠bugs.koha-community.org 20 Apr '26

20 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38906 Bug ID: 38906 Summary: REGEXP_REPLACE not in MySQL < 5.8 DB update 24.06.00.064 fails Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Database Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org In bug 38436 Katrin mentions that REGEXP_REPLACE was a problem, it still can be if using MySQL 5.7 or below We had a test site update fail Seems to be easily fixed by changing to: UPDATE columns_settings SET columnname=SUBSTRING(columnname,LOCATE("_",columnname)+1) WHERE module="catalogue" AND page="detail" AND ( tablename="holdings_table" OR tablename="otherholdings_table"); -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 31