April 2020 - Koha-bugs - lists.koha-community.org

[Bug 24628] New: Fine grained control over reserve notice recipients
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '24

06 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24628 Bug ID: 24628 Summary: Fine grained control over reserve notice recipients 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org In bug 17014 comment 32 Ray requested a more advanced configurability of reserve notices as quoted below: >No Notice Before parameter: Rather than this being a system preference I see it better as an additional column in the Circulation & Fine rules. This would be configurable line by line (user category / item type) and allow the Koha library to email as many or as few current holders of the non-renewed items as they wished. Libraries that wanted to be more lenient that us could increase the No Renewal Before to 1, 2, or 3, say, but it would be the wise choice of a No Notice Before value that would be the best driver in targeting users whose items are likely to fulfil the reservation / hold. > We have multiple copies of the same item (with various loan periods) out on loan. If a reservation is placed we want to send renewal-failure notification only to users whose copy is due “soon”, and not to people who have, say, just taken a long-term loan copy out. Native Koha auto-renewal functionality currently sees every holder of the item emailed. But the first copy returned satisfies the reservation. Why pester everyone- we want to better target the email. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 24626] New: error en RunSQL.pm line 273.
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '24

06 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24626 Bug ID: 24626 Summary: error en RunSQL.pm line 273. Change sponsored?: --- Product: Koha Version: 19.05 Hardware: All OS: Linux Status: NEW Severity: enhancement Priority: P5 - low Component: Installation and upgrade (web-based installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: xavierxamora(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Created attachment 98685 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=98685&action=ed… image with the error that comes out install koha on ubuntu 16.04.06 versions 19.11 and 19.05 and I get the same error as this [Mon Feb 10 17:12:17 2020] install.pl: DBD :: mysql :: st execute failed: Cannot delete or update a parent row: a foreign key constraint fails at /usr/share/perl5/DBIx/RunSQL.pm line 273. I am doing my university stay and at the time of installation I get this, some solution; I am occupying mariadb 10.0.38 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 24613] New: SIP reports unable to checkin withdrawn item if not checked out and checked_in_ok set
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '24

06 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24613 Bug ID: 24613 Summary: SIP reports unable to checkin withdrawn item if not checked out and checked_in_ok set Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The code that checks circ_ok against checked_in_ok comes after warning about withdrawn item so it says return has been blocked even if it hasn't -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 22276] New: Add client storage of user-selected DataTables configuration
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '24

06 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22276 Bug ID: 22276 Summary: Add client storage of user-selected DataTables configuration Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- DataTables has a "stateSave" option which uses's the browser's local storage to "remember" how someone last changed the configuration of a DataTable: columns settings, filters, etc. This option doesn't work by default because we always load the configuration stored in Columns Settings. I propose to add a function which will check for the existence of a locally-store table configuration before defaults are loaded. -- You are receiving this mail because: You are watching all bug changes.

1 34

[Bug 24334] New: Barcode should be included in Marcitemfieldstoorder
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '24

06 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24334 Bug ID: 24334 Summary: Barcode should be included in Marcitemfieldstoorder Change sponsored?: --- Product: Koha Version: 19.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When libraries are ordering shelf-ready books, most of these records from the vendor include a barcode. The system preference marcitemfieldstoorder, does not accept a barcode to be included in this system preference, so the library can not save the barcode of the item that they are receiving. Currently, there are a lot of item level fields that can be used such as a non-public note, public note, URI, call number, etc. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 24326] New: Problem with advance_notices_digest.t
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '24

06 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24326 Bug ID: 24326 Summary: Problem with advance_notices_digest.t 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Depends on: 20478 (In reply to Jonathan Druart from comment #26) > There is something terribly wrong with this test file, the cronjob script is > run outside the transaction and so changes are effective. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20478 [Bug 20478] Advance notices: send separate digest messages per library -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 18908] New: Warning "Compatibility levels before 9 are deprecated"
by bugzilla-daemon＠bugs.koha-community.org 05 Jan '24

05 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18908 Bug ID: 18908 Summary: Warning "Compatibility levels before 9 are deprecated" Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: mtompset(a)hotmail.com QA Contact: testopia(a)bugs.koha-community.org CC: mirko(a)abunchofthings.net The following output: dh: Compatibility levels before 9 are deprecated (level 7 in use) dh_testdir -O--fail-missing dh_auto_clean -O--fail-missing dh_auto_clean: Compatibility levels before 9 are deprecated (level 7 in use) dh_clean -O--fail-missing is given when trying to following these instructions: https://wiki.koha-community.org/wiki/Building_Debian_Packages_-_The_Easy_Way -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 11

[Bug 25328] New: Date formatting from JS - Remove tz handling
by bugzilla-daemon＠bugs.koha-community.org 03 Jan '24

03 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25328 Bug ID: 25328 Summary: Date formatting from JS - Remove tz handling Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: agustinmoyano(a)theke.io Reporter: agustinmoyano(a)theke.io QA Contact: testopia(a)bugs.koha-community.org CC: jonathan.druart(a)bugs.koha-community.org, martin.renvoize(a)ptfs-europe.com, tomascohen(a)gmail.com Depends on: 24455, 24980 After some discussion, I now believe timezone handling in JS is redundant, and should be removed. Dates that comes from the API are already converted to the corresponding timezone with dt_from_string, so there is no need for a second conversion here. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24455 [Bug 24455] Date formatting from JS https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24980 [Bug 24980] Date formatting from JS - use timezone only with dates with offset -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 19616] New: Formatted Contents Note (Marc 21 505), subfield g isn' t visible in the OPAC
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '24

02 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19616 Bug ID: 19616 Summary: Formatted Contents Note (Marc 21 505), subfield g isn't visible in the OPAC Change sponsored?: --- Product: Koha Version: 16.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: verolencinas(a)yahoo.com.ar QA Contact: testopia(a)bugs.koha-community.org The 505 field in Marc 21, Formatted Contents Note, includes subfield g "Miscellaneous information". According to the Marc 21 format for bibliographic data, it is used to record "volume, part, page numbering or other extent information such as dates". If you use it in Koha, this information isn't visible in the OPAC. -- You are receiving this mail because: You are watching all bug changes.

1 35

[Bug 24261] New: Google openID Authethication drops requested url
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '24

02 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24261 Bug ID: 24261 Summary: Google openID Authethication drops requested url Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: mihai.bojonca(a)tcmi.edu QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org Hi everyone, i think this is a bug, we have setup access to catalog after login, we use 2 authentication methods, username and password or google openid, when a patron opens a direct link to an item and authenticates with username and password they get to the item itself however with openid they get redirected to the opac main page -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5