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

[Bug 31503] New: Groundwork for 20380 (mail consent)
by bugzilla-daemon＠bugs.koha-community.org 02 Feb '26

02 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31503 Bug ID: 31503 Summary: Groundwork for 20380 (mail consent) Change sponsored?: --- Product: Koha Version: master 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: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 170

[Bug 31533] New: Add opt-in/opt-out flags to patron consents
by bugzilla-daemon＠bugs.koha-community.org 02 Feb '26

02 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31533 Bug ID: 31533 Summary: Add opt-in/opt-out flags to patron consents Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org Part of the 20380 set. Building on top of 31503. While we now only enforce the GDPR consent if the pref is set to Enforced, we leave other consents empty. Which actually is opt-in. They need to go to the consents page and enable the specific consent. If we would add opt-out, we can either add consents for all users or make PatronConsent a bit smarter and only register refusal (opt-out). It feels more consistent to add all consents to the table, and add them too in the self reg process. But when you add a new consent type and mark it as opt-out, we should then populate the table too. Do we also need a Mandatory flag? Historically, we treat the GDPR consent as such. Other consents may not be of that same category. But we might want the user to make an explicit choice there without the same exceptional approach that we use for GDPR. How do we get him on that page? If he arrives there, we can obviously allow saving only when those mandatories are filled.. -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 30968] New: opac-authorites-home.pl still accessible even when OpacAuthorities system preference is turned off
by bugzilla-daemon＠bugs.koha-community.org 02 Feb '26

02 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30968 Bug ID: 30968 Summary: opac-authorites-home.pl still accessible even when OpacAuthorities system preference is turned off Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: wizzyrea(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org When the system preference OpacAuthorities is turned off, the page https://your.library.here/cgi-bin/koha/opac-authorities-home.pl is still accessible and likely shouldn't be. To test: set OpacAuthorities to Don't Allow try to visit https://your.library.here/cgi-bin/koha/opac-authorities-home.pl note that the page is still accessible. Thanks for checking it out! Liz -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 29557] New: auto-renew notices should handle failed renewal due to patron expiration
by bugzilla-daemon＠bugs.koha-community.org 30 Jan '26

30 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29557 Bug ID: 29557 Summary: auto-renew notices should handle failed renewal due to patron expiration Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The default auto-renew and auto-renew-digest notices should include logic to tell patrons when their renewals have failed due to upcoming patron expiration. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21

[Bug 22740] New: Automatically change lost status when item is paid for
by bugzilla-daemon＠bugs.koha-community.org 28 Jan '26

28 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22740 Bug ID: 22740 Summary: Automatically change lost status when item is paid for Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: mfuerst(a)hmcpl.org QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- When patrons pay for a lost item, our staff change the Lost status of the item from "Lost" or "Long overdue Lost" to "Lost and Paid For." This helps make distinctions in reports and in other workflows. With the advent of online payment options (PayPal), it adds what feels like extra work for us to hunt down these items and make this change. In both cases it would be beneficial if paying for an item resulted in the item's Lost status being changed to a specified authorized value. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 67

[Bug 22312] New: BlockReturnOfLostItems does not prevent lost items filling holds
by bugzilla-daemon＠bugs.koha-community.org 28 Jan '26

28 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22312 Bug ID: 22312 Summary: BlockReturnOfLostItems does not prevent lost items filling holds Change sponsored?: --- 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: phil(a)chetcolibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Target Milestone: --- When the preference BlockReturnOfLostItems is set, it prevents checkin from checking the item in, but it does not prevent prompting to fill a hold with that item. Steps to reproduce: 1. Set BlockReturnOfLostItems to Block 2. Place a hold that can be filled by a particular item 3. Mark that item as Lost (or Missing, or any other flavor of lost) 3. Attempt to check in that item Expected results: Message stating that "Item is lost, cannot be checked in./Cannot check in/NOT CHECKED IN", no message about the hold. Actual results: The "Item is lost, cannot be checked in./Cannot check in/NOT CHECKED IN" message displays in the page, but is quickly covered by the popup saying that it can fill a hold. If any of the Confirm buttons (Confirm, Confirm and print slip, Confirm and transfer) is clicked in the hold popup, when the popup closes the message in the page below is removed, leaving no sign that the hold was just filled by an item which is now both being held and also lost. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 28896] New: Checkin Slip doesn't work for anonymized checkouts
by bugzilla-daemon＠bugs.koha-community.org 28 Jan '26

28 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28896 Bug ID: 28896 Summary: Checkin Slip doesn't work for anonymized checkouts Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Circulation 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, kyle.m.hall(a)gmail.com The new CHECKINSLIP notice does not work on patrons whose checkouts are anonymized upon checkin. Instead it appears that the patron had no checkins at all! This is due to how the feature gets the old issues. The printslip script takes the borrowernumber and a branchcode and searches the old_issues table which is then filtered by date. I think for this to function for anonymized checkouts we need to pass the actual issue_id's as a list to the slip so they can be looked up directly and not inferred by borrowernumber, branchcode and date. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 19360] New: Give items URL a link text
by bugzilla-daemon＠bugs.koha-community.org 28 Jan '26

28 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19360 Bug ID: 19360 Summary: Give items URL a link text Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: alexbuckley(a)catalyst.net.nz Reporter: alexbuckley(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Instead of directly displaying the URL entered into the URI (Uniform Resource Identifier) field the patch attached to this bug report will allow the user to input a link text to be displayed instead of the URL on the intranet and OPAC detail page. -- You are receiving this mail because: You are watching all bug changes.

1 45

[Bug 34556] New: Add a template 'Accessibility statement' page to the default data
by bugzilla-daemon＠bugs.koha-community.org 28 Jan '26

28 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34556 Bug ID: 34556 Summary: Add a template 'Accessibility statement' page to the default data Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Installation and upgrade (web-based installer) 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 Blocks: 23003 We should add a template 'accessibility statement' using the pages feature of Koha and add it optionally to the installer default data. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23003 [Bug 23003] Accessibility improvements -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21

[Bug 33218] New: Should the 'Main contact method' field override the AutoEmailPrimaryAddress at patron-level?
by bugzilla-daemon＠bugs.koha-community.org 27 Jan '26

27 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33218 Bug ID: 33218 Summary: Should the 'Main contact method' field override the AutoEmailPrimaryAddress at patron-level? Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org While I was working on bug 33191 et al. I asked myself if the 'Main contact method' drop down was somehow linked to AutoEmailPrimaryAddress, as a way to override the system preference at patron level. I was told no, but I think it would make sense... If for example AutoEmailPrimaryAddress is set to 'home' (primary email), and a patron chooses their work email as their main contact method, there is no way to send email notices to their work email, is there? I would see it as something like the CheckPrevCheckouts, where it is possible to override the syspref at the patron-level. Not sure how it would work with custom values as introduced in bug 31498, however... -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6