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

[Bug 37661] New: Disable/Enable Bookings
by bugzilla-daemon＠bugs.koha-community.org 16 Sep '26

16 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37661 Bug ID: 37661 Summary: Disable/Enable Bookings Change sponsored?: --- Product: Koha Version: 24.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation 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, kyle.m.hall(a)gmail.com If libraries are not planning to use the bookings feature, there's no way to hide this option. Even if staff don’t have the manage_bookings permission, they can still set an item as bookable, but the “place booking” button won’t appear for them. It would be nice if the bookings feature could be set to enable/disable via a system preference, similar to EnablePointOfSale, EnableItemGroups, HouseboundModule, ERMModule, ILLModule, and PreservationModule. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 132

[Bug 22707] New: Allow manual definition of AutoMemberNum range
by bugzilla-daemon＠bugs.koha-community.org 16 Sep '26

16 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22707 Bug ID: 22707 Summary: Allow manual definition of AutoMemberNum range 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Target Milestone: --- It'd be great to have a way to tell Koha where to start when assigning card numbers via AutoMemberNum and to see what the next number will be. Bug 19263 introduced a feature that uses an authorized value to set up ranges of auto-incremented control numbers in bib records. Could something similar be used for card numbers? Ideally, this could also allow the definition of separate card number ranges for different branches. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 42

[Bug 39976] New: Serving static error pages from Apache instead of Starman
by bugzilla-daemon＠bugs.koha-community.org 16 Sep '26

16 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39976 Bug ID: 39976 Summary: Serving static error pages from Apache instead of Starman Change sponsored?: --- Product: Koha Version: Main 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: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org At the moment, all error documents are produced dynamically by Starman/Koha. When Apache encounters an error, it uses custom ErrorDocument directives which end up proxying to Starman to get the errors. For example, http://localhost:8081/blah. When Plack encounters an error, it needs to produce its own error documents and that's why we have the ErrorDocument middleware. For example, an Internal Server Error in a Perl script. Since we're using persistent processes, this is mostly fine. But if someone does 100 concurrent requests to http://localhost:8081/blah, it doesn't really make sense to transfer that load onto Starman/Plack. It would be good if Apache could just handle it without touching the backend. Pre-generating static pages isn't a big drama in itself, but the issue we'll face is multilingualism. But... in theory we could use mod_negotiation or mod_rewrite to do an internal redirect to the language appropriate error document (based off the Koha Language cookie ). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 41297] New: Add duplicate invoice number detection on EDI invoice import
by bugzilla-daemon＠bugs.koha-community.org 16 Sep '26

16 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41297 Bug ID: 41297 Summary: Add duplicate invoice number detection on EDI invoice import Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org EDIFACT invoice processing should detect and block duplicate invoice numbers, notify the supplier (possibly via an EDI CONTRL message), and alert library staff. While Koha has the AcqWarnOnDuplicateInvoice system preference for manual invoice creation (implemented in Bug 10366), this check is not applied to invoices created automatically via EDIFACT/EDI processing in Koha/EDI.pm. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 72

[Bug 31391] New: Staff-side recalls
by bugzilla-daemon＠bugs.koha-community.org 16 Sep '26

16 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31391 Bug ID: 31391 Summary: Staff-side recalls 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: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Add functionality for recalls to be placed via the staff interface -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 364

[Bug 34896] New: Separate Z39.50 permission from edit_catalogue
by bugzilla-daemon＠bugs.koha-community.org 15 Sep '26

15 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34896 Bug ID: 34896 Summary: Separate Z39.50 permission from edit_catalogue Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: mnero(a)oslri.net QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl The majority of our library staff use Z39.50 to bring in records using the Fast Add framework, and we do not want them to be able to edit records that use the Default framework. We currently need to give everyone the edit_catalogue permission because that is the only way to give them access to Z39.50. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 22232] New: Advanced Cataloguing Editor (Rancor) to edit authority records?
by bugzilla-daemon＠bugs.koha-community.org 15 Sep '26

15 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22232 Bug ID: 22232 Summary: Advanced Cataloguing Editor (Rancor) to edit authority records? Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: clopez(a)dml.vic.edu.au QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Target Milestone: --- Dear colleagues How hard would it be to allow Rancor to edit authority records? Regards, Carlos Lopez Dalton McCaughey Library -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 36

[Bug 15685] New: Allow creation of items (AcqCreateItem) to be customizable per-basket
by bugzilla-daemon＠bugs.koha-community.org 15 Sep '26

15 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15685 Bug ID: 15685 Summary: Allow creation of items (AcqCreateItem) to be customizable per-basket Change sponsored?: Sponsored Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: jweaver(a)bywatersolutions.com Reporter: jweaver(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: nicole(a)bywatersolutions.com -- You are receiving this mail because: You are watching all bug changes.

1 119

[Bug 15997] New: Hold Ratios for ordered items doesn't count orders where AcqCreateItem is set to 'receiving'
by bugzilla-daemon＠bugs.koha-community.org 15 Sep '26

15 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15997 Bug ID: 15997 Summary: Hold Ratios for ordered items doesn't count orders where AcqCreateItem is set to 'receiving' 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Currently, the hold ratios script only counts on order items where the record item is created at the time the order is placed, and not if the item is created when the item is received. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 32748] New: Library limitations will cause data loss when editing items
by bugzilla-daemon＠bugs.koha-community.org 15 Sep '26

15 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32748 Bug ID: 32748 Summary: Library limitations will cause data loss when editing items Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Moving this from bug 31422 where another issue was fixed to a new bug report: The library limitations are used to limit down the selection in pull downs in several spots. If you are editing data from library B while logged in at library A, doing so might result in data loss as the value stored in the modified object might be missing from the drop downs your user sees. Example 1: Item values Itemtype: BK Books - limited to Centerville AV LOC: FIC Fiction - limited to Centerville Your user: logged in for Centerville * Edit an item and make sure it uses the itemtype Books and location Fiction. * Switch library to any but Centerville. * Edit item: Both item type and location drow downs will be empty. * Saving now will empty out itemtype (if not set mandatory) and location resulting in data loss. I initially thought that bug 20256 might help here, but it won't as there is a mismatch of one feature checking the login library and the other checking the home library of the staff patron. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 97