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

[Bug 12732] Add basket creation date to late orders table for sorting
by bugzilla-daemon＠bugs.koha-community.org 27 Sep '23

27 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12732 Owen Leonard <oleonard(a)myacpl.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Failed QA |Signed Off -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 29716] New: [DOCS] Automated screenshots
by bugzilla-daemon＠bugs.koha-community.org 27 Sep '23

27 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29716 Bug ID: 29716 Summary: [DOCS] Automated screenshots Change sponsored?: --- Product: Koha Version: master Hardware: All URL: https://gitlab.com/davidnind/koha-automated-screenshot s OS: All Status: ASSIGNED Severity: enhancement Priority: P4 Component: Documentation Assignee: david(a)davidnind.com Reporter: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org See if we can automate the capture of as many screenshots as possible for the Koha documentation, in as many languages as possible. -- You are receiving this mail because: You are watching all bug changes.

1 8

[Bug 29992] New: Default Apache config should contain CGIPassAuth directive
by bugzilla-daemon＠bugs.koha-community.org 27 Sep '23

27 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29992 Bug ID: 29992 Summary: Default Apache config should contain CGIPassAuth directive Change sponsored?: --- Product: Koha Version: unspecified 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: andrew.isherwood(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org By default, authorization headers are stripped out by Apache and therefore do not reach the underlying CGI script. This causes problems when Koha is receiving API requests that contain them as the client just receives a 401 response, even if a valid token was provided. I propose we add the CGIPassAuth directive to the API Directory blocks. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 25948] New: Clean up apache protocols and ciphers
by bugzilla-daemon＠bugs.koha-community.org 27 Sep '23

27 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25948 Bug ID: 25948 Summary: Clean up apache protocols and ciphers Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Installation and upgrade (command-line installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: mtompset(a)hotmail.com QA Contact: testopia(a)bugs.koha-community.org SSLCipherSuite was truncated and different between the OPAC and Intranet sections. While cleaning that up, removed TLSv1 as it is supposed to be deprecated already. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 34928] New: Email outgoing address options
by bugzilla-daemon＠bugs.koha-community.org 26 Sep '23

26 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34928 Bug ID: 34928 Summary: Email outgoing address options Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org It might improve email situations if Koha had an option for all outgoing notices to go through a single email address, rather than the individual libraries. This would make it easier for patrons to whitelist a single address, rather than multiple addresses if you are part of a consortium. Emails could also be set with a reply-to address, that could be redirected back to the library that would have originally sent the email, which at that point would make it clearer to email systems that a conversation is being had between the two addresses. In theory. I could be totally wrong about all of this, but in my simple mind, this seems like a better work flow for notices. Although, maybe sending everything out through one address might raise flags quicker? I don't know. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 34808] New: Batch Patron Modification Tool - Select all / clear all does not select/clear all
by bugzilla-daemon＠bugs.koha-community.org 26 Sep '23

26 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34808 Bug ID: 34808 Summary: Batch Patron Modification Tool - Select all / clear all does not select/clear all Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: Laura.escamilla(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To recreate: 1. Open the Batch Patron Modification Tool 2. Insert or open a file with 25+ card numbers or borrower numbers to modify then click on continue. 3. Notice that there are 2 or more pages of entries showing. If you click on clear all, it will only clear entries 1-20 but not anything on the second page (21-...). Similarly if you clear both pages and try to select all, it will only select the entries on the page you are viewing. It would useful if the select all/clear all worked on all entries. Especially for libraries that are modifying hundreds of patrons. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 19014] New: Limit auto-renewal notice to item due immediately. Template Toolkit change ?
by bugzilla-daemon＠bugs.koha-community.org 26 Sep '23

26 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19014 Bug ID: 19014 Summary: Limit auto-renewal notice to item due immediately. Template Toolkit change? Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: r.delahunty(a)arts.ac.uk QA Contact: testopia(a)bugs.koha-community.org Current functionality in 17.05: All copies of an item with auto-renewal enabled, reserved at the title level. Due dates of copies on loan include today, and various dates into the future, some many weeks ahead. When the auto-renewal job runs, Koha is sending an AUTO_RENEWAL email to ALL the users warning them ALL of renewal failure, using the [% ELSIF checkout.auto_renew_error == 'on_reserve' %] Desired functionality in 17.05: When the auto-renewal job runs, Koha should only send an AUTO_RENEWAL email to the user (or possibly users) whose copy is due back today, on the day the auto-renewal job runs. Other people who have copies on loan but which are not yet due back yet should not be contacted by the AUTO_RENEWAL email. Users contacted in this way are being very puzzled and confused. Could this be achieved by an edit to the condition in the template toolkit? So rather this: [% ELSIF checkout.auto_renew_error == 'on_reserve' %] This item has been reserved by another reader. … we have something like this: [% ELSIF checkout.auto_renew_error == 'on_reserve' && checkout.date_due %==today %] This item has been reserved by another reader. Would that work? Is a second condition permissible? How should it be worded? Ray Delahunty University of the Arts London -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 121

[Bug 12732] Add basket creation date to late orders table for sorting
by bugzilla-daemon＠bugs.koha-community.org 26 Sep '23

26 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12732 Emily Lamancusa <emily.lamancusa(a)montgomerycountymd.gov> changed: What |Removed |Added ---------------------------------------------------------------------------- QA Contact|testopia(a)bugs.koha-communit |emily.lamancusa@montgomeryc |y.org |ountymd.gov Status|Signed Off |Failed QA CC| |emily.lamancusa@montgomeryc | |ountymd.gov --- Comment #23 from Emily Lamancusa <emily.lamancusa(a)montgomerycountymd.gov> --- Thanks for the patch on this long-outstanding bug! Just one thing: this patch uses the data-sort attribute in the td tag, but the same table has other rows that use data-order instead. Can this one be adjusted to use data-order for consistency? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 32603] New: Suggester category in Suggestions management
by bugzilla-daemon＠bugs.koha-community.org 26 Sep '23

26 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32603 Bug ID: 32603 Summary: Suggester category in Suggestions management Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: frederic(a)tamil.fr QA Contact: testopia(a)bugs.koha-community.org In Suggestions management, it would be intersting to know the suggester category. This way, it would be possible for example for the librarian managing suggestions rather to prioritize suggestions coming from teachers than those coming from students. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 34319] New: Upgrade Cypress
by bugzilla-daemon＠bugs.koha-community.org 26 Sep '23

26 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34319 Bug ID: 34319 Summary: Upgrade Cypress Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Test Suite Assignee: jonathan.druart+koha(a)gmail.com Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org We are currently using 9.7.0. Since 10 the config file structure changed, and has been renamed cypress.json to cypress.config.ts https://docs.cypress.io/guides/references/migration-guide#Migrating-to-Cypr… Also cypress-studio (used for bug 34076) is not working on 9.7.0. -- You are receiving this mail because: You are watching all bug changes.

1 29