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

[Bug 32020] New: Expired pages are still accessible
by bugzilla-daemon＠bugs.koha-community.org 09 Nov '26

09 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32020 Bug ID: 32020 Summary: Expired pages are still accessible Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org When creating a new page with the additional content page, there is a possibility of adding an 'expiration date' to the page, presumably for when the content of the page is not valid anymore. However, the link to that page is still valid after the page has expired. I wonder if the link should return an error page or 404 page or something like that. To test: 1. Go to Tools > Pages > New entry 2. Create a page with no expiry date 4. Access the link to the page in another tab 5. Click 'Edit' next to the page entry 6. Add an expiry date in the past to the entry --> It disappears from the list of pages 7. In the other tab, refresh the page --> It is still accessible -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 41385] New: Exception and error thrown from add_credit method is wrong
by bugzilla-daemon＠bugs.koha-community.org 09 Nov '26

09 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41385 Bug ID: 41385 Summary: Exception and error thrown from add_credit method is wrong Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: emmi.takkinen(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org If credit amount passed to the Koha::Account->add_credit is not negative, Koha throws exception called Koha::Exceptions::Account::AmountNotPositive with error message "Debit amount passed is not positive". This is same error thrown with method add_debit. We should at least change error message as e.g. "Credit amount passed is not negative" and probably create a new exception called Koha::Exceptions::Account::AmountNotNegative to avoid confusion. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 25408] New: CanBookBeReserved should check "opacitemholds" policy
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '26

07 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25408 Bug ID: 25408 Summary: CanBookBeReserved should check "opacitemholds" policy Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: arthur.suzuki(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com how to reproduce : Set an issuing rule with opacitemholds set to "Force" Make a search and select multiple records Place a hold on those records (using multi-hold records) Verify hold is placed on the record (next item available) where it shouldn't! -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 162

[Bug 19501] New: New list category to restrict specific lists to staff & hide from OPAC
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '26

07 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19501 Bug ID: 19501 Summary: New list category to restrict specific lists to staff & hide from OPAC Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Lists Assignee: koha-bugs(a)lists.koha-community.org Reporter: Jeremy.evans(a)nibsc.org QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl We are creating various lists of titles that need to be hidden from view in the OPAC for the time being but other staff members need to see them. At the moment the options are Public or Private so this won't do what we require. We would like an additional list category selection of Staff so that those lists are then visible in the staff client (& presumably also to anyone who logs into the OPAC with a staff permissions login) but are not publicly visible in the OPAC. The intention is that multiple staff members may need to add items to some of these lists. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 61

[Bug 41419] New: Error javascript "undefined" is not valid JSON when showing the order edit modal in orderreceive.tt
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '26

07 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41419 Bug ID: 41419 Summary: Error javascript "undefined" is not valid JSON when showing the order edit modal in orderreceive.tt 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: hammat.wele(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org to reproduce 1. Go to Acquisitions → New vendor, enter a name, check Vendor is Active, and click Save. 2. Click the name of the vendor you just created in the table. 3. Click New → Basket, enter a basket name, and click Save. 4. Click Add to basket → From a new (empty) record. Enter a title, add an item, and click Save. 5. Click Close basket. 6. Click Receive shipments, enter a number in the Vendor invoice field, and click Next. 7. Click Receive for the created line. 8. Open the browser console. 9. In the modal, tick the Receive? checkbox and click Confirm. 10. Go to the previous page → The console shows the error: "undefined" is not valid JSON at JSON.parse (<anonymous>) was shown 11. Apply the patch 12. Go to Acquisitions → Search for the vandor created on step 2 13. Repeat step 3, 4, 5, 6, 7, 8, 9, 10 → There is no js error -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 25

[Bug 37568] New: Explain category types in the manual
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '26

07 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37568 Bug ID: 37568 Summary: Explain category types in the manual Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: philip.orr(a)lmscloud.de QA Contact: testopia(a)bugs.koha-community.org CC: aude.charillon(a)ptfs-europe.com, philip.orr(a)lmscloud.de In the manual section on patron categories, the section on category types ("Adult", "Child", "Staff"... etc.) is unclear on what the category types actually do. It would be good to document what selecting a specific category type actually does for the patrons created using this category type. Manual page: https://koha-community.org/manual/latest/en/html/administration.html#patron… -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 34460] New: Patron category should regulate if account can have permissions
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '26

06 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34460 Bug ID: 34460 Summary: Patron category should regulate if account can have permissions 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Permission management would be simpler if there were a setting in patron categories that indicate whether that category of patron can have permissions. - If no, that option would not appear in the patron menu. - If patron category is changed to a category that does not allow permissions, any existing permissions should be cleared when change is saved. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 25

[Bug 40255] New: Allow custom debit descriptions
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '26

06 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40255 Bug ID: 40255 Summary: Allow custom debit descriptions Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Bug 24865 made it possible to use a notice to replace the default wording of the description for overdue fines. It would be helpful to expand that functionality to all debit types, both system-defined and local. It might make more sense to put this within the Debit Type setup than to continue using notices, though. These custom descriptions would allow Template Toolkit as notices do, however, for formatting, logic, and value transformation -- for example, one library wants the description to tell what portion of the fee goes to local tax. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 74

[Bug 33711] New: Refine the token passing mechanisms introduced in bug 23336
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '26

06 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33711 Bug ID: 33711 Summary: Refine the token passing mechanisms introduced in bug 23336 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com CC: koha-bugs(a)lists.koha-community.org, tomascohen(a)gmail.com Depends on: 23336 Bug 23336 introduces an API workflow for checkouts by adding two endpoints.. one for availability that creates a token for confirmations that can then be used by the checkouts endpoint to verify that availability has been checked. Whilst I think the availability endpoint is worthwhile in it's own right, I think we could also send back the token in the 409 pre-condition failed response of the checkouts endpoint so one could use that single endpoint for double duty in the right circumstances. I also think we could work on how the confirmation token is sent to the endpoint.. it's currently a simple query param but may lend itself to being part of the x-koha-overrides header or another header? Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23336 [Bug 23336] Add an API endpoint for issuing an item to a patron -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes. You are on the CC list for the bug.

1 10

[Bug 38763] New: Missing documentation of export database and export configuration options
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '26

06 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38763 Bug ID: 38763 Summary: Missing documentation of export database and export configuration options Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: aude.charillon(a)ptfs-europe.com, philip.orr(a)lmscloud.de Depends on: 8268 Maybe I'm missing it, but I don't see information in the manual about exporting the Koha database or configuration. The feature was added by Bug 8268 and may have been missed because it requires editing of koha-conf.xml? Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8268 [Bug 8268] Koha should offer way to backup entire db -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4