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

[Bug 14962] Temp Shelving Location / On Display Module
by bugzilla-daemon＠bugs.koha-community.org 28 Aug '26

28 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14962 Emily Lamancusa (emlam) <emily.lamancusa(a)montgomerycountymd.gov> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #203700|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14962] Temp Shelving Location / On Display Module
by bugzilla-daemon＠bugs.koha-community.org 28 Aug '26

28 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14962 Emily Lamancusa (emlam) <emily.lamancusa(a)montgomerycountymd.gov> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #203699|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14962] Temp Shelving Location / On Display Module
by bugzilla-daemon＠bugs.koha-community.org 28 Aug '26

28 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14962 Emily Lamancusa (emlam) <emily.lamancusa(a)montgomerycountymd.gov> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #203698|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 42875] New: Wrong failure message when adding an item to a bundle
by bugzilla-daemon＠bugs.koha-community.org 28 Aug '26

28 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42875 Bug ID: 42875 Summary: Wrong failure message when adding an item to a bundle Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com Target Milestone: --- If bc_1 is checked out and I try to add bc_2 I get: "Failure: Item 'bc_2' belongs to another bundle" The POST returns 409 {"error":"Bundle is checked out","error_code":"bundle_checked_out"} The JS code: - } else if (response.error_code === "bundle_checkout_out") { - $("#addResult").replaceWith('<div id="addResult" class="alert alert-danger">' + _("Failure: Bundle is currently checked out") + "</div>"); -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21

[Bug 40435] New: CanBookBeRenewed should respect future holds or even more
by bugzilla-daemon＠bugs.koha-community.org 28 Aug '26

28 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40435 Bug ID: 40435 Summary: CanBookBeRenewed should respect future holds or even more Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, lisette(a)bywatersolutions.com, tomascohen(a)gmail.com This is a follow-up of bug 37651. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 41

[Bug 43403] New: Clarify FutureHoldsBlockRenewals description
by bugzilla-daemon＠bugs.koha-community.org 28 Aug '26

28 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43403 Bug ID: 43403 Summary: Clarify FutureHoldsBlockRenewals description Initiative type: --- Sponsorship --- status: Product: Koha Version: 25.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: sbrown(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Depends on: 40435 Target Milestone: --- The system preference description for FutureHoldsBlockRenewals reads "[Allow/Don't allow] future holds (within the same number of days) to block renewals". However, since the preference only blocks future item-level holds, it would be helpful if that was indicated in the system preference ("[Allow/Don't allow] future item-level holds (within the same number of days) to block renewals" or similar). Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40435 [Bug 40435] Allow CanBookBeRenewed to consider future holds -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 31268] New: Clearly indicate reason for failed item creation when receiving expired subscription
by bugzilla-daemon＠bugs.koha-community.org 28 Aug '26

28 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31268 Bug ID: 31268 Summary: Clearly indicate reason for failed item creation when receiving expired subscription Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrewfh(a)dubcolib.org QA Contact: testopia(a)bugs.koha-community.org Bug 29188 points out that while the manual says one cannot receive issues in an expired subscription, Koha is currently allowing one to do so. However, Koha *is* refusing to create an item when receiving an issue on an expired subscription. To recreate: 1 - create a subscription set to *not* create items, subscription end date in the past 2 - save subscription, confirm it shows as expired, confirm you can receive an issue anyway 3 - create a subscription set *to* create items, subscription end date in the past 4- save subscription, confirm it shows as expired, confirm you can get to the receiving page but setting the dropdown for the expected issue to "Arrived" does not cause an item edit box to appear 5- create a subscription set *to* create items, subscription end date in the future, number of issues set to 1 6- save subscription, receive 1 issue, confirm it works as intended 7- confirm subscription now shows a confusing "Subscription will expire on [subscription end date]" message even though the date isn't the problem 8- Attempt to receive another issue, confirm that now the item edit box won't pop up, as in step 4 In steps 4 and 8, the item edit box will appear if one attempts to receive a supplemental issue, but the item will refuse to save, giving an erroneous "missing required field" message. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 43169] New: Patron photo enhancements
by bugzilla-daemon＠bugs.koha-community.org 28 Aug '26

28 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43169 Bug ID: 43169 Summary: Patron photo enhancements Initiative type: --- Sponsorship --- status: Product: Koha Version: Main 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(a)bywatersolutions.com Target Milestone: --- It would be an improvement to the patron page if we were to update the patron photo a bit. Layout of photo and patron data is extremely basic. Current Microsoft Outlook contact info lays out contacts with a name in ID card fashion, with name in a header, photo to the left, and contact info to the right of the photo. On my screen, it could fit in the left panel. I was also thinking that there could be a footer overlay that could add a library logo (based on homebranch) and patron category. This would be helpful to identify staff/patrons better. It would be great if there were a field in the library table to save a library photo or logo. And if you have the photos turned on, and there is no patron photo, the homebranch logo could go there instead of as a footer overlay. Just some ideas I thought I'd shoot out. See if anyone thinks this could be laid out better or dressed up nicer. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 35203] New: Koha::Biblio->get_coins support 214 field in addition to 210 (pubyear and publisher values)
by bugzilla-daemon＠bugs.koha-community.org 28 Aug '26

28 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35203 Bug ID: 35203 Summary: Koha::Biblio->get_coins support 214 field in addition to 210 (pubyear and publisher values) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: thibaud.guillot(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Hello, The publisher info and publication date for the <span Z3988> tag (corners) are based on the 210 but more and more records are now based on 214. Hence a loss of information. NB This is also the case for BIBTEXT and RIS formats. I will therefore propose a patch to add the new 214 field to the get->coins() method. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 42926] New: Return passwordmustchange flag when patron password is expired
by bugzilla-daemon＠bugs.koha-community.org 28 Aug '26

28 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42926 Bug ID: 42926 Summary: Return passwordmustchange flag when patron password is expired Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: thibaud.guillot(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com Target Milestone: --- Hello, When a patron's password is expired (whether due to ForcePasswordResetWhenSetByStaff or natural expiration), the REST API can returns a structured 403 response with a `passwordmustchange` boolean flag. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 10