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

[Bug 26190] New: Cannot close baskets when all lines have been cancelled
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '20

17 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26190 Bug ID: 26190 Summary: Cannot close baskets when all lines have been cancelled 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: r.delahunty(a)arts.ac.uk QA Contact: testopia(a)bugs.koha-community.org Current functionality: Using Koha 18.11 we are unable to close baskets once all order lines in the basket have been cancelled. We are having to leave baskets open, as if they’re still being worked on. Desired functionality: Allow baskets with all lines cancelled to be closed, and kept for reporting purposes. In the past, if the basket only contained one item ordered and cancelled, we have occasionally deleted the basket at fiscal year end (losing the acquisitions trail), but one of our main vendors has recently gone out of business and we have had to cancel a lot of orders, with all order lines in many baskets cancelled. This will mean we will have to delete the baskets too, maybe at next fiscal year close. Our policy has been to keep all acquisitions trails for a maximum of six years, in keeping with business finance guidance, and we want to keep cancellation information for the same number of years too if possible. (OK, there are no actual financial implications since the orders are cancelled but retention would be useful, allowing librarians to see what they had wanted but couldn’t get, in their book order reports). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 18051] New: Advanced Editor - Rancor - encoding issues with some sources
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '20

17 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18051 Bug ID: 18051 Summary: Advanced Editor - Rancor - encoding issues with some sources Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl This source for example: http://www.webclarity.info/registry/display?fileID=69 All displays fine from basic editor - rancor however causes garbled characters -- You are receiving this mail because: You are watching all bug changes.

1 22

[Bug 18050] New: Missing constraint foreign key on table aqbudget
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '20

17 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18050 Bug ID: 18050 Summary: Missing constraint foreign key on table aqbudget Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Database Assignee: gmcharlt(a)gmail.com Reporter: baptiste.wojtkowski(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org There is not foreign key constraint on the column budget_parent_id in the table aqbudget. It is so possible to delete a budget without deleting the associated fund. -- You are receiving this mail because: You are watching all bug changes.

1 46

[Bug 25549] New: Install plugin script/method should remove broken plugins
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '20

17 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25549 Bug ID: 25549 Summary: Install plugin script/method should remove broken plugins Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Plugin architecture Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org bug 23191 added a script to allow installation of plugins from the command line. There can be an issue when a plugin no longer compiles after an upgrade, Koha will not load, the script will not run either. We should repair the script so that it can remove plugin methods that no longer function or have been deleted. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 34

[Bug 20804] New: Sanitize input of timeout syspref
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '20

17 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20804 Bug ID: 20804 Summary: Sanitize input of timeout syspref Change sponsored?: --- Product: Koha Version: 17.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: pablo.bianchi(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com I naively change timeout syspref from default "1d" to "2h". I get logout immediatly, and after login again, at the first clic I was logged out again, with any user, even with koha_instance. plack-error.log Use of uninitialized value $lasttime in numeric lt (<) at /usr/share/koha/lib/C4/Auth.pm line 1425. Argument "2h" isn't numeric in subtraction (-) at /usr/share/koha/lib/C4/Auth.pm line 1425. Argument "2h" isn't numeric in subtraction (-) at /usr/share/koha/lib/C4/Auth.pm line 862. I was back again with via sql update (value='1d') and flushing memcached. I suggest: - Don't been possible to input an invalid input on timeout (well, on any, but for the moment on this one). m/^[0-9]*[dD]?$/ - This syspref (maybe others also) shouldn't apply to koha_instance user (God shouldn't be able to microwave a burrito so hot he himself couldn't eat it). Would be great 30m and 2h for minutes and hours, but that should be other bug. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 25

[Bug 26191] New: Relocate track_login call in Auth.pm (see 22543)
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '20

17 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26191 Bug ID: 26191 Summary: Relocate track_login call in Auth.pm (see 22543) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org >From bug 22543 comment30: (In reply to Jonathan Druart from comment #29) > 2. This code has been put before track_login_daily, is that expected? No. The track call should be done before. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 25511] New: Add --force option to update_dbix_class_files.pl
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '20

17 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25511 Bug ID: 25511 Summary: Add --force option to update_dbix_class_files.pl Change sponsored?: --- Product: Koha Version: 19.11 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Sometimes, if you know what you are doing, you may want to force a schema overwrite regardless of whether the hashes report there are changes above the fold. In these cases, we should expose said functionality via a --force option on the script. WARNING: Use this at your own risk.. it's helpful if you are maintaining a fork or in other such cases. You should always attempt to run the script without force first and only resort to using force if that fails. It is also very much worthwhile checking the diff after running with force to ensure you have not resulted in any unexpected changes. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 26232] New: undefined fine grace period kills koha
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '20

17 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26232 Bug ID: 26232 Summary: undefined fine grace period kills koha Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: didier.gautheron(a)biblibre.com Reporter: didier.gautheron(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Staff can create smart rules with empty (undefined) grace period, but then koha returns an internal error in : DateTime::Duration::new('DateTime::Duration', 'days', undef) called at /kohadevbox/koha/C4/Circulation.pm line 2395 C4::Circulation::_calculate_new_debar_dt(HASH(0x564b11658e58)', 'HASH(0x564b11836c28)', 'DateTime=HASH(0x564b1164d688)', 'DateTime=HASH(0x564b116787d0)') called at /kohadevbox/koha/C4/Circulation.pm line 2451 -- You are receiving this mail because: You are watching all bug changes.

1 19

[Bug 26018] New: Not all subfields for the following tags are in the same tab (or marked 'ignored')
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '20

17 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26018 Bug ID: 26018 Summary: Not all subfields for the following tags are in the same tab (or marked 'ignored') Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: MARC Bibliographic data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: psmukhopadhyay(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org In a fresh install of Koha 20.05.01.000 the 'MARC bibliographic framework test' fails in one point reporting that "Not all subfields for the following tags are in the same tab (or marked 'ignored')" for all preloaded formats (Default to VR). In every case invariably the culprit is subfield 2 of the below mentioned tags - 240(1,2) | 700 (1,7) | 710 (1,7) | 711 (1,7) | 730 (1,7) | 758 (1,7) | 800 (1,8) | 810 (1,8) | 811 (1,8) | 830 (1,8). The numbers within parenthesis indicate tabs are in use. It only occurs in case of a fresh installation of 20.05.01 loaded with default formats (Default, AR, BKS, CF, IR, KT, SER, SR, VR), not with the upgradations of 18.x or 19.x to 20.05.01 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 26148] New: OpenLibrary "Preview" link target is unclear to patrons
by bugzilla-daemon＠bugs.koha-community.org 16 Nov '20

16 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26148 Bug ID: 26148 Summary: OpenLibrary "Preview" link target is unclear to patrons Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org When you have OpenLibraryCovers turned on, there will be a "Preview" link showing below the cover that leads to the Open Library page of the title. I think we should make clear in the wording that the link is an external link that will lead you outside the library catalog and it should also open in a new tab. To test: - Activate OpenLibraryCovers - Search (in sample data) for: 0140423826 -- You are receiving this mail because: You are watching all bug changes.

1 10