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

[Bug 42810] New: New patron category form does not show self-renewal information message field
by bugzilla-daemon＠bugs.koha-community.org 17 Aug '26

17 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42810 Bug ID: 42810 Summary: New patron category form does not show self-renewal information message field Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: System Administration Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Depends on: 26355 Target Milestone: --- The patron category template logic works in such a way that if you're creating a new patron category the "Self-renewal information message" field is not shown, but the hint for the field is shown. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26355 [Bug 26355] Allow patron account renewals through the OPAC -- You are receiving this mail because: You are watching all bug changes.

1 25

[Bug 42953] New: Creating a Progressive Web App (PWA) for the OPAC
by bugzilla-daemon＠bugs.koha-community.org 17 Aug '26

17 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42953 Bug ID: 42953 Summary: Creating a Progressive Web App (PWA) for the OPAC Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- I first heard about Progressive Web Apps (PWAs) back in 2018, but I never really had time or motivation to work on one. But the other day I was reminded about their existence, and then when I was installing MarcEdit 7.8 I noticed it has a dependency on WebView2 which is a Microsoft-based technology that provides a native app wrapper around a web view (ie a HTML/CSS/Javascript frontend). While mobile apps like Solus have integrations with Koha, Koha itself has had any downloadable/installable apps but people have certainly asked for them. I know we're short on time overall, but I wonder how challenging it might be to provide a PWA for the OPAC. Whether we could just wrap the existing OPAC or whether we'd need to build something more separately (which could take advantage of APIs). Anyway, just a thought for now... -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 31180] New: Provide a koha-conf.xml (etc.) checker.
by bugzilla-daemon＠bugs.koha-community.org 17 Aug '26

17 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31180 Bug ID: 31180 Summary: Provide a koha-conf.xml (etc.) checker. Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: egpetridis(a)yahoo.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com I feel that a checker should be provided that checks the various configuration files -koha-conf.xml is a prime suspect- and notify the library admin of missing stanzas or invalid values. For example, missing information on fonts to be used, or reference to non-existent (or non-accessible) files and/or folders. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 23260] New: Anonymize (remove) patron data from items_last_borrower
by bugzilla-daemon＠bugs.koha-community.org 14 Aug '26

14 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23260 Bug ID: 23260 Summary: Anonymize (remove) patron data from items_last_borrower Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: joy(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Increase level of patron privacy by removing patron information from the items_last_borrower table after a set period of time. Adjust the batch_anonymize cronjob to also remove data from the items_last_borrower table when the data is more than x days old (runtime option) but not if the item is lost, damaged, or withdrawn. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 336

[Bug 42909] New: Suspend class missing from suspended holds on request.pl
by bugzilla-daemon＠bugs.koha-community.org 14 Aug '26

14 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42909 Bug ID: 42909 Summary: Suspend class missing from suspended holds on request.pl Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: emily.lamancusa(a)montgomerycountymd.gov QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, lisette(a)bywatersolutions.com, tomascohen(a)gmail.com Depends on: 23269 Target Milestone: --- When viewing the holds list for a particular biblio record, the tr (table row) elements previously had a "suspend" class, allowing CSS styling of suspended holds. As of 25.11.05, that class is missing. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23269 [Bug 23269] Long hold queues are slowing the service -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 19

[Bug 29285] New: UI tests: Selenium 4 support
by bugzilla-daemon＠bugs.koha-community.org 14 Aug '26

14 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29285 Bug ID: 29285 Summary: UI tests: Selenium 4 support Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: victor(a)tuxayo.net QA Contact: testopia(a)bugs.koha-community.org Now v4 is the default when getting the docker image selenium/standalone-firefox . For Selenium 4, the maintainer of our current perl bindings wrote another client: https://metacpan.org/pod/Selenium::Client -- You are receiving this mail because: You are watching all bug changes.

1 16

[Bug 33840] New: UpdateItemLocationOnCheckin needs a duration and library parameters
by bugzilla-daemon＠bugs.koha-community.org 14 Aug '26

14 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33840 Bug ID: 33840 Summary: UpdateItemLocationOnCheckin needs a duration and library parameters Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation 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 It would be nice if we could define in UpdateItemLocationOnCheckin how long the change takes effect. Either add a |0 for indefinite, or |60 for 60 minutes (enter the duration in minutes. Maybe also have a |[BRANCH,ETC] or |[ALL] parameter to indicate what branches this would affect. That way, you could specify which branches to apply which timings to. The reason for this is that the reset to permanent is currently done through a cron, so we can't see this in settings, and it is global. It affects everyone. Some libraries return items to the shelf sooner than others. We could streamline this to adjust to each libraries reshelving rate. I guess the only issue would be the trigger for this. Should a cron job be checking these updates, and should there be a minimum on how often this cron runs so that it doesn't bog down the system? Would it bog down the system looking for items in shelving location at a branch? Should it be limited to hours and not minutes? Also, should UpdateItemLocationOnCheckin be left as a global setting, and should we have a branch level setting in the branches setups? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 43188] New: Remove mentions of version 24.11 in the Koha Manual
by bugzilla-daemon＠bugs.koha-community.org 14 Aug '26

14 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43188 Bug ID: 43188 Summary: Remove mentions of version 24.11 in the Koha Manual Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: aude.charillon(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: aude.charillon(a)openfifth.co.uk, david(a)davidnind.com, philip.orr(a)lmscloud.de Target Milestone: --- When we moved to the one manual for all versions, the Documentation team decided the Manual is for Koha versions supported by the community. 24.11 is now the new LTS version; we should use this as the base version and remove from the Manual any mentions it. What is actually new is what happened *since* 24.11, not *in* 24.11. - Remove the 24.11 section from the What's new page. - Search for any mentions of 24.11 in other pages. There will be version notes (new features) and attention notes (existing functionality deprecated or updated). The version notes should be removed. You may need to remove the whole paragraph or section an attention note is part of, if the feature does not work that way / does not exist in 24.11 and later. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 43187] New: Remove mentions of version 24.05 in the Koha Manual
by bugzilla-daemon＠bugs.koha-community.org 14 Aug '26

14 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43187 Bug ID: 43187 Summary: Remove mentions of version 24.05 in the Koha Manual Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: aude.charillon(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: aude.charillon(a)openfifth.co.uk, david(a)davidnind.com, philip.orr(a)lmscloud.de Target Milestone: --- When we moved to the one manual for all versions, the Documentation team decided the Manual is for Koha versions supported by the community. 24.11 is now the new LTS version; we should remove any mentions of older versions in the Manual. - Remove the 24.05 section from the What's new page. - Search for any mentions of 24.05 in other pages. There will be version notes (new features) and attention notes (existing functionality deprecated or updated). The version notes should be removed. You may need to remove the whole paragraph or section an attention note is part of, if the feature does not work that way / does not exist in 24.05 and later. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 37381] New: Suggestion mandatory fields needed in staff interface
by bugzilla-daemon＠bugs.koha-community.org 14 Aug '26

14 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37381 Bug ID: 37381 Summary: Suggestion mandatory fields needed in staff interface Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: esther.melander(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org It is possible to mark fields mandatory in the purchase suggestion form for the OPAC with OPACSuggestionMandatoryFields. It should also be possible to mark fields mandatory for the purchase suggestion form in the staff interface. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3