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

[Bug 29365] New: Koha::Email issues
by bugzilla-daemon＠bugs.koha-community.org 21 Dec '21

21 Dec '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29365 Bug ID: 29365 Summary: Koha::Email issues 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 Follow-up bug for 28729 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 10

[Bug 15121] runreport.pl cronjob ought to let you specify multiple email addresses
by bugzilla-daemon＠bugs.koha-community.org 21 Dec '21

21 Dec '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15121 Koha Team University Lyon 3 <koha(a)univ-lyon3.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=29365 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15121] runreport.pl cronjob ought to let you specify multiple email addresses
by bugzilla-daemon＠bugs.koha-community.org 21 Dec '21

21 Dec '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15121 Koha Team University Lyon 3 <koha(a)univ-lyon3.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |koha(a)univ-lyon3.fr --- Comment #1 from Koha Team University Lyon 3 <koha(a)univ-lyon3.fr> --- Hi, you could add several email with report.pl with a 19.11 version (and previous version also) by spliting the adresses with a comma. For example runreport.pl 683 --format=html --email --to=mail(a)mail.fr, mail2(a)mail.fr It isn't possible anymore since we are in 20.11 version. My colleague Olivier suggest a change in Koha::Email. Could we retrieve this feature ? Thanks Sonia -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 11350] Holds offered to patrons who are not allowed to put the item on hold
by bugzilla-daemon＠bugs.koha-community.org 21 Dec '21

21 Dec '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11350 Alex Buckley <alexbuckley(a)catalyst.net.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=23172 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 11350] Holds offered to patrons who are not allowed to put the item on hold
by bugzilla-daemon＠bugs.koha-community.org 21 Dec '21

21 Dec '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11350 Alex Buckley <alexbuckley(a)catalyst.net.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alexbuckley(a)catalyst.net.nz --- Comment #5 from Alex Buckley <alexbuckley(a)catalyst.net.nz> --- I think this bug report might be a duplicate of bug 23172 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 29295] New: Page specific jQuery
by bugzilla-daemon＠bugs.koha-community.org 20 Dec '21

20 Dec '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29295 Bug ID: 29295 Summary: Page specific jQuery 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Would love it if there was an option laid out, just like sql reports, where we could list jQuery modifications. We would have a global tab for each module (internet, OPAC, Self-Check, etc.) and then we could pick a specific page and have jQuery that was just for that page. That way if you have jQuery that only deals with a specific page, it would only load with that page, and not be loaded in the background when on all the other pages it will never apply to. This would also help organize modifications as well. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 14210] Manage staged marc records deletes replaced item when undoing import into catalog
by bugzilla-daemon＠bugs.koha-community.org 20 Dec '21

20 Dec '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14210 David Cook <dcook(a)prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dcook(a)prosentient.com.au -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 29728] New: upgrade from 21.05 to 21.11 DBI Exception
by bugzilla-daemon＠bugs.koha-community.org 20 Dec '21

20 Dec '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29728 Bug ID: 29728 Summary: upgrade from 21.05 to 21.11 DBI Exception Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: Linux Status: NEW Severity: blocker Priority: P5 - low Component: Installation and upgrade (web-based installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: juanpablovalles(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Upgrading from 21.05 to 21.11 the installer said: Upgrade to 21.06.00.007 [15:41:52]: Bug 11879 - Add a new field to patron record: main contact method ERROR: {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs at /usr/share/koha/lib/C4/Installer.pm line 738 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 14210] Manage staged marc records deletes replaced item when undoing import into catalog
by bugzilla-daemon＠bugs.koha-community.org 20 Dec '21

20 Dec '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14210 Andrew Fuerste-Henry <andrew(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |andrew(a)bywatersolutions.com --- Comment #5 from Andrew Fuerste-Henry <andrew(a)bywatersolutions.com> --- This is still true and still bad. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 29740] New: New Organization field
by bugzilla-daemon＠bugs.koha-community.org 20 Dec '21

20 Dec '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29740 Bug ID: 29740 Summary: New Organization field Change sponsored?: --- Product: Koha Version: unspecified 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.m.hall(a)gmail.com Would suggest we add a new field to the patron record called "organization". Currently we are storing organization names in the surname field. This is inaccurate, and causes some issues between validation (maybe custom validation) and switching from a patron type record and an organization record, especially if anything was left in a first name field at the time. Having a separate organization field would also allow us to correctly record an organization name and a contact at that organization. There are ways around this currently, but typical databases usually include a separate field for an organization name. This would also allow us to more accurately identify organizations with a specific contact person and include lines like "c/o: Joe Smith" under the organization name in notifications. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0