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

[Bug 38212] New: Optionally allow lost items to fill holds (or not)
by bugzilla-daemon＠bugs.koha-community.org 20 Oct '25

20 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38212 Bug ID: 38212 Summary: Optionally allow lost items to fill holds (or not) Change sponsored?: --- Product: Koha Version: 24.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: catrina(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Some Partners would like the ability to exclude Lost items from making holds available, similar to the AllowHoldsOnDamagedItems system preference. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 40357] New: Notices and Slips library selection
by bugzilla-daemon＠bugs.koha-community.org 20 Oct '25

20 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40357 Bug ID: 40357 Summary: Notices and Slips library selection Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org Currently, if a group of libraries out of the entire selection of libraries need to customize a slip or notice, you have to create a template for each library. It would be more efficient if the templates applied to selected libraries in the template, much like we do for other things in Koha (like attributes). Obviously it would cause issue if more than one copy of a particular template had the same library selected in both, so we could have Koha refuse to save the template with the offending duplicate library if detected. If that were the case, it would need to show which library is being used in a similar template, and which template. The editor could then either give the option to save without the offending libraries, or an option could be given to remove the offending libraries from the other template(s). This workflow would allow us to maintain less templates, and not have to duplicate so much work. Thoughts? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 16207] New: Incorporate circulation and fine rules for library groups
by bugzilla-daemon＠bugs.koha-community.org 20 Oct '25

20 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16207 Bug ID: 16207 Summary: Incorporate circulation and fine rules for library groups Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com I think we could simplify circulation and fine rules by incorporating library groups into the mix. For example, I have 27 libraries, and 8 of them follow the same set of rules that are different from the defaults. So, what if instead of cloning these special rules to 8 different libraries (and who knows how many other duplicated sets of rules there are), we defined a set of rules for a library group. If the library is part of that group, it goes by those rules. I don't know if we want to use the same library groups that are already defined in the libraries and groups, or if we want to create a unique Circ rule group. Because, there is always the chance that one or more of the libraries in the 8 that are grouped together by affiliation or region could have a slightly different set of rules. However, I think rules by groups would make managing rules far less complicated than managing groups of cloned rules. Christopher -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 40555] New: Items with empty itemtype causes Preservation module to crash
by bugzilla-daemon＠bugs.koha-community.org 20 Oct '25

20 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40555 Bug ID: 40555 Summary: Items with empty itemtype causes Preservation module to crash Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: pedro.amorim(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com We've hit this recently on our demo installation, but I believe we've stumbled upon this in the past in different parts of Koha that may interact with Items (and Bookings, by extension). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12

[Bug 18327] New: Reception date when receiving multiple issues for a subscription is not the good one
by bugzilla-daemon＠bugs.koha-community.org 20 Oct '25

20 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18327 Bug ID: 18327 Summary: Reception date when receiving multiple issues for a subscription is not the good one Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: severine.queune(a)bulac.fr QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com When receiving several issues for a subscription (Serials > Serial collection > Multi receiving), the reception date is identical to the publication date instead of being the today date. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 25

[Bug 40338] New: Tidy the whole codebase
by bugzilla-daemon＠bugs.koha-community.org 17 Oct '25

17 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40338 Bug ID: 40338 Summary: Tidy the whole codebase Change sponsored?: --- Product: Koha Version: 24.11 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: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: dcook(a)prosentient.com.au, domm(a)plix.at, emily.lamancusa(a)montgomerycountymd.gov, jonathan.druart(a)gmail.com, julian.maurice(a)biblibre.com, katrin.fischer(a)bsz-bw.de, koha(a)trust-box.at, lucas(a)bywatersolutions.com, martin.renvoize(a)openfifth.co.uk, nick(a)bywatersolutions.com, oleonard(a)myacpl.org, paul.derscheid(a)lmscloud.de, pedro.amorim(a)openfifth.co.uk, testopia(a)bugs.koha-community.org, tomascohen(a)gmail.com, victor(a)tuxayo.net We tidied our whole codebase in 25.05.. but this makes backports to the maintenance branches an ongoing challenge. This bug serves to independently backport the tidy to the 24.11.x branch to hopefully make future maintenance simpler. +++ This bug was initially created as a clone of Bug #38664 +++ -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 35654] New: Add option to delete last item to delete_items.pl
by bugzilla-daemon＠bugs.koha-community.org 17 Oct '25

17 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35654 Bug ID: 35654 Summary: Add option to delete last item to delete_items.pl Change sponsored?: --- 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: enica(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Apologies if there's a duplicate bug. It would be great to add a parameter to delete_items.pl to delete the record if the last item getting deleted is the only one that remains. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 52

[Bug 40061] New: Cannot delete image from patron card creator
by bugzilla-daemon＠bugs.koha-community.org 17 Oct '25

17 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40061 Bug ID: 40061 Summary: Cannot delete image from patron card creator Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Label/patron card printing Assignee: cnighswonger(a)foundations.edu Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org I noticed this in 24.05, but it also happens in KTD on main. When you upload an image in the patron card creator, if you try to delete it, it returns an error. 1. Go to Tools > Patron card creator 2. Click New > Image 3. Upload an image (I used a png with transparent background, hence why I had to delete it after, but I also tried with a jpg with the same result) 4. Enter a name for the image (I tried "Logo Bibliothèque" as well as a name all in lowercase letters without spaces or diacritics "tomhanks" with the same result) 5. Click Upload 6. Click Delete on the right-hand side --> Error "WARNING: An error has occurred. Please have your system administrator check the error log for details." plack-intranet-error.log says [2025/06/03 16:40:36] [WARN] No image ids passed in to delete. at /kohadevbox/koha/patroncards/image-manage.pl line 131. -- You are receiving this mail because: You are watching all bug changes.

1 22

[Bug 40250] New: Wrong link to NoIssuesChargeGuarantorWithGuarantees in patron category page
by bugzilla-daemon＠bugs.koha-community.org 17 Oct '25

17 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40250 Bug ID: 40250 Summary: Wrong link to NoIssuesChargeGuarantorWithGuarantees in patron category page Change sponsored?: --- Product: Koha Version: unspecified 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 noticed while translating that the link to the NoIssuesChargeGuarantorsWithGuarantees syspref in the patron category settings page is a link to NoIssuesChargeGuarantees. A simple copy-paste error I think. To recreate: 1. Go to Administration > Patron categories 2. Click New category --> Notice the hint under "Guarantors with guarantees checkout charge limit" is to the NoIssuesChargeGuarantees system preference rather than NoIssuesChargeGuarantorsWithGuarantees -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21

[Bug 38342] New: Koha::Object->store warning on invalid ENUM value
by bugzilla-daemon＠bugs.koha-community.org 17 Oct '25

17 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38342 Bug ID: 38342 Summary: Koha::Object->store warning on invalid ENUM value 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: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Bug 38175 introduced handling for truncated enum values. But the exception that is thrown is missing a parameter, and as such prints a warning when stringifying the exception. To test: 1. On KTD, run: $ ktd --shell k$ prove t/db_dependent/Koha/Booking.t => FAIL: There's: ``` DBIx::Class::Storage::DBI::_dbh_execute(): DBI Exception: DBD::mysql::st execute failed: Data truncated for column 'status' at row 1 at /kohadevbox/koha/Koha/Object.pm line 172 Use of uninitialized value in sprintf at /kohadevbox/koha/Koha/Exceptions/Object.pm line 84. Use of uninitialized value in sprintf at /kohadevbox/koha/Koha/Exceptions/Object.pm line 84. ok 1 - Throws exception when passed booking status would fail enum constraint ``` The 'Use of initialized...' ones are not correct. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13