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

[Bug 41113] New: Missing doc-head-close and cssinclude in sci-main.tt
by bugzilla-daemon＠bugs.koha-community.org 05 Oct '26

05 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41113 Bug ID: 41113 Summary: Missing doc-head-close and cssinclude in sci-main.tt Initiative type: --- Sponsorship Sponsored status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: aleisha(a)catalyst.net.nz, alexbuckley(a)catalyst.net.nz, dcook(a)prosentient.com.au, hammat.wele(a)inlibro.com, lucas(a)bywatersolutions.com, testopia(a)bugs.koha-community.org +++ This bug was initially created as a clone of Bug #21266 +++ Many of the some changes should be made to the self checkin templates -- You are receiving this mail because: You are watching all bug changes.

1 16

[Bug 43397] New: SIP accounts with a blank AE field template send an empty patron name
by bugzilla-daemon＠bugs.koha-community.org 05 Oct '26

05 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43397 Bug ID: 43397 Summary: SIP accounts with a blank AE field template send an empty patron name Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Bug 37893 moved SIP accounts from SIPconfig.xml into the database. The new SIP account editor initializes every text field to an empty string rather than null, so an account created through the staff interface gets ae_field_template = '' instead of NULL which is defined and so the empty template is used thus giving an empty AE field in responses for newly created accounts! -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 39962] New: Recalled status does not show properly on staff interface record detail page
by bugzilla-daemon＠bugs.koha-community.org 05 Oct '26

05 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39962 Bug ID: 39962 Summary: Recalled status does not show properly on staff interface record detail page Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com To reproduce: 1. Enable the UseRecalls system preference and set the recalls-related circulation and fines rules. 2. Search for an item. 3. Check out an item to Patron B. 4. Log into the OPAC as Patron A. 5. Request a record-level recall on the record. 6. View the record on the staff interface and look at the holdings table. Notice that the checked out item shows no indication of being recalled, but the recall request does show on the Recalls tab. --> BUG 7. Go to the Recalls tab and cancel the recall. 8. Go back to the OPAC and request an item-level recall on the checked out item. 9. View the record on the staff interface and look at the holdings table. Notice that the checked out item now shows the recalled status, twice. "Recalled by koha (42) on DATE" --> BUG -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 25

[Bug 35937] New: Add hourly support to Bookings
by bugzilla-daemon＠bugs.koha-community.org 05 Oct '26

05 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35937 Bug ID: 35937 Summary: Add hourly support to Bookings Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Depends on: 29002 Bug 29002 adds the ability to book items ahead of time. It works at the daily loan level, but stores hours with the intention of expanding it to support hourly bookings. We should expose these hourly bookings as an option to end users. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29002 [Bug 29002] Add ability to book items ahead of time -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 34

[Bug 25586] New: Something wrong with KOHA_HOME
by bugzilla-daemon＠bugs.koha-community.org 05 Oct '26

05 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25586 Bug ID: 25586 Summary: Something wrong with KOHA_HOME Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org CC: mirko(a)abunchofthings.net -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 41162] New: Warn that printing large barcode ranges can lead to running out of memory
by bugzilla-daemon＠bugs.koha-community.org 04 Oct '26

04 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41162 Bug ID: 41162 Summary: Warn that printing large barcode ranges can lead to running out of memory Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: philip.orr(a)lmscloud.de QA Contact: testopia(a)bugs.koha-community.org If you are using the barcode range option in the label creator, if your barcode range is too large, your Koha server may run out of memory before the process finishes. This causes out of memory errors. This could happen if a library had e.g. "100101223" as their last used barcode and they wanted to print the next 50 barcodes and they make a mistake while entering the "To:" field in the barcode range creator. From: 100101224 To: 1000101274 You could very easily accidentally cause the label-create.pl process to create insane amounts of barcodes. In this case 900 million barcodes would be created, if my math is right. :) The memory usage will slowly increase as barcodes are created and "eventually" there will be no more memory left, causing OOM killer to strike. We should at least warn in the barcode range creation tool that such problems can happen if you aren't careful while entering values. I don't know if there's a good way to stop users from entering too large ranges, maybe there is a valid use case for a large barcode range if you have enough memory. To reproduce (assuming you are on ktd): 1. Check your current memory usage, e.g. with "ps aux --sort -rss" (or "free -h" to see how much memory is still free) 2. Make sure you know how to kill a process in Debian, e.g. "killall -9 /kohadevbox/koha/labels/label-create-pdf.pl" - you will need it soon.. 3. Go to Cataloging -> Label Creator -> Print barcode range 4. Enter in a number in "From:" and a crazy high number in "To:"; see above for an example 5. Print range -> Export (doesn't matter which templates etc.) -> Click on "Download as PDF" 5. Check your memory usage again, it should start spiking over the next minutes. The guilty process should be /kohadevbox/koha/labels/label-create-pdf.pl (assuming you are on ktd). 6. Either kill the process or you will run out of memory -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12

[Bug 42585] New: Add ability for Koha to analyze reports and warn for potentially dangerous reports
by bugzilla-daemon＠bugs.koha-community.org 04 Oct '26

04 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42585 Bug ID: 42585 Summary: Add ability for Koha to analyze reports and warn for potentially dangerous reports Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: lisette(a)bywatersolutions.com It is quite possible to write reports in Koha that, when run, create huge temp tables that crash a database server or cause runreport.pl to use so much RAM that the kernel oom-kills Koha. It would be nice if we had a tool built in to Koha to help warn librarians about reports with the potential to bring down a Koha server. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 40

[Bug 40258] New: Option to only use item-level recalls and disable record-level recalls
by bugzilla-daemon＠bugs.koha-community.org 03 Oct '26

03 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40258 Bug ID: 40258 Summary: Option to only use item-level recalls and disable record-level recalls Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com It would be good to essentially hide the "Recall next available item" options for libraries who do not want record-level recalls -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 43362] New: URI validation for biblio MARC21 field 856$u and items.uri
by bugzilla-daemon＠bugs.koha-community.org 03 Oct '26

03 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43362 Bug ID: 43362 Summary: URI validation for biblio MARC21 field 856$u and items.uri Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Would be nice to add (basic) URI validation for biblio MARC21 field 856$u and items.uri. Opening another report for authority records in relation to the use of external vocabularies, including corresponding biblio subfields. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 43333] New: Restore the name of the vendor as h1 in vendor details page
by bugzilla-daemon＠bugs.koha-community.org 03 Oct '26

03 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43333 Bug ID: 43333 Summary: Restore the name of the vendor as h1 in vendor details page Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- While testing 26.05 prior to rolling it out to our clients, the team noticed that in the vendor's details page, the name of the vendor is not prominent anymore. There is a h2 that says "Vendor #x" but the name of the vendor is only in the small section in the details. For most end users, they don't care that this is vendor #1, #2 or #38. They tell the vendors apart by their name. I can't tell which bug changed this because for some reason vue pages don't react well to git checkout (or maybe I just don't know how it works which is also a possibility). In 25.05.05 which is the version our clients currently use, the vendor name is in an h1. In main (and 26.05.02), the vendor # is in an h2 and, as far as I can tell, there is no h1. To recreate : 1. In KTD, go to Acquisitions 2. Click Search in the vendor search box 3. Click "My vendor" --> The biggest title on the page is "Vendor #1" --> "My vendor" is in the breadcrumbs and in the form, but both are small and a bit lost in the rest of the information 4. Inspect the title "Vendor #1" --> It's a h2 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 31