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

[Bug 31442] New: Node.js v12 is EOL
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '23

25 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31442 Bug ID: 31442 Summary: Node.js v12 is EOL 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: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org The currently maintained LTS release is v16. We could start using v18 which will be the new LTS in october and would be current until 2025. https://nodejs.org/en/about/releases/ -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 8658] Don't display patron attributes which have been limited to another patron category
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '23

25 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8658 Esther Melander <esther.melander(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |esther.melander@bywatersolu | |tions.com --- Comment #2 from Esther Melander <esther.melander(a)bywatersolutions.com> --- This bug still exists in 22.11 To Replicate: 1. Create two patrons, Patron A and Patron B in two different patron categories. 2. Create a patron attribute. Select Display in OPAC, Editable in OPAC, and limit the attribute to the patron category assigned to Patron A. 3. Edit Patron A to have the patron attribute. 4. Login to the OPAC with Patron B's account. See the patron attribute is displayed and editable to patron B. The expected behavior is that Patron B would not see or be able to edit the patron attribute because they are in a different patron category. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 34374] New: Built in Offline Circulation interface browser not Compatible.
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '23

25 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34374 Bug ID: 34374 Summary: Built in Offline Circulation interface browser not Compatible. Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: drigney(a)equinoxinitiative.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Built-in offline circulation interface gives the following error message: Offline circulation disabled Your browser is not compatible with the built-in offline circulation tool. I tried this on Chrome (Version 114.0.5735.199 and Version 115.0.5790.102), Edge (Version 114.0.1823.82) and Firefox (115.0.2). Koha 21.05 is not giving that error message. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 5463] Limit to available shows on hold items
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '23

25 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5463 Amanda Campbell <acampbell(a)hmcpl.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |acampbell(a)hmcpl.org -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 5463] Limit to available shows on hold items
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '23

25 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5463 Lisette Scheer <lisette.scheer(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lisette.scheer@bywatersolut | |ions.com -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 7012] Limit to available does not exclude in-transit items
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '23

25 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7012 Amanda Campbell <acampbell(a)hmcpl.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |acampbell(a)hmcpl.org -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 29489] New: <<branches.branchname>> in RENEWAL notice subject field
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '23

25 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29489 Bug ID: 29489 Summary: <<branches.branchname>> in RENEWAL notice subject field Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: george(a)nekls.org QA Contact: testopia(a)bugs.koha-community.org Using <<branches.branchname>> returns the library name when used in the subject field for a notice template with one apparent exception. If an item is renewed from the OPAC the RENEWAL notice is sent with the subject "<<branches.branchname>>" We are set up so that an item renewal via the OPAC should get recorded statistically as a renewal by the branch the item was checked out at. It would be nice if <<branches.branchname>> filled in the branch name of the library where the item was checked out rather than "branches.branchcode" -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 34370] New: E-mail not sending to patrons
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '23

25 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34370 Bug ID: 34370 Summary: E-mail not sending to patrons Change sponsored?: --- Product: Koha Version: 23.05 Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: priyanshu(a)tatvic.com QA Contact: testopia(a)bugs.koha-community.org Hi, I want to know how to configure the e-mail setting in a library to send mails to patrons. Please send all the steps and if there is any option for a live chat, please let me know. Thank you -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 1993] Task Scheduler Needs Re-write
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '23

25 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=1993 --- Comment #58 from David Cook <dcook(a)prosentient.com.au> --- As Martin has noted elsewhere: (In reply to Martin Renvoize from comment #6) > I've long felt our use of 'at' in scheduler was wrong, but we've not had a > reasonable alternative. We now have BackgroundJobs and I could see us using > that system as an alternative to using 'at' and calling a script. I agree about using BackgroundJobs for the execution. We'll still need a scheduler, and I think the shortest path forward is a cronjob-based scheduler script, which polls the database every X interval looking for jobs to run. -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 32993] New: Holds priority changed incorrectly with dropdown selector
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '23

25 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32993 Bug ID: 32993 Summary: Holds priority changed incorrectly with dropdown selector Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: emmi.takkinen(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com When one tries to change holds priority via dropdown selector, holds priority doesn't change correctly. To test: 1. Find record with at least 3 holds. 2. Change first holds priority as 2. => Priority is changed to 3. 3. Try to change priority back to 1. => Priority is changed to 2. Somewhat same as bug 19636 but not quite. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 18