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

[Bug 24634] New: Support display of changelog files for plugins
by bugzilla-daemon＠bugs.koha-community.org 26 Aug '22

26 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24634 Bug ID: 24634 Summary: Support display of changelog files for plugins Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Plugin architecture Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Well maintained plugins should include a changelog file in their package. We should support displaying this changelog from the plugin management pages. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 24635] New: Support display of readme files for plugins
by bugzilla-daemon＠bugs.koha-community.org 26 Aug '22

26 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24635 Bug ID: 24635 Summary: Support display of readme files for plugins Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Plugin architecture Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: koha-bugs(a)lists.koha-community.org, testopia(a)bugs.koha-community.org Depends on: 23975, 24634 Well maintained plugins should include a readme file in their package. We should support displaying this readme from the plugin management pages. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23975 [Bug 23975] Add ability to search and install plugins from GitHub https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24634 [Bug 24634] Support display of changelog files for plugins -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 31462] New: add a way to batch edit items without displaying all the items in a table
by bugzilla-daemon＠bugs.koha-community.org 26 Aug '22

26 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31462 Bug ID: 31462 Summary: add a way to batch edit items without displaying all the items in a table Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When you are batch editing a lot of items, the second screen of batchMod.pl can take a long time to display the list of all items. Sometimes it raises an HTTP error. It should be possible to choose to not display this list. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 31146] New: Minor UI problem in recalls history in OPAC
by bugzilla-daemon＠bugs.koha-community.org 26 Aug '22

26 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31146 Bug ID: 31146 Summary: Minor UI problem in recalls history in OPAC 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: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org This is very minor, but I figured it might make an easy fix for someone... When recalls are turned on, the patron has access to their recalls history in their online account. If the OPAC is multilingual, the language switcher is right under the recalls history table, rather than being at the bottom of the page where it normally is. To test: 1) Install another language and enable it in the OPACLanguages system preference 2) Also make sure opaclanguagesdisplay is set to Allow 3) Make sure OpacLangSelectorMode is set to display the switch in the footer (either top and bottom or footer only) 4) Turn on recalls 4.1) In Administration > Global system preferences, enable UseRecalls 4.2) Add recalls permissions in your circulation rules 5) In the OPAC, log in as a patron 6) Find a record with checked out items and place a recall 7) Go to your account --> Note that the language switch is at the bottom left of the screen 8) Click on any tab in the patron's account --> Note that the language switch is at the bottom left of the screen 9) Click on 'Your recalls history' --> Note that the language switch is right under the recalls history table -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 31134] New: t/Ediorder.t tests failing on 22.05.02
by bugzilla-daemon＠bugs.koha-community.org 26 Aug '22

26 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31134 Bug ID: 31134 Summary: t/Ediorder.t tests failing on 22.05.02 Change sponsored?: --- Product: Koha Version: 22.05 Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org Bug 30135 might have introduced a flaw in the tests - when we try to install Koha 22.05.02 and run t/ediorder.t, it fails with this output: vagrant@kohadevbox:kohaclone((v22.05.02))$ sudo koha-shell kohadev kohadev-koha@kohadevbox:/home/vagrant/kohaclone$ prove t/Ediorder.t t/Ediorder.t .. 1/13 Use of uninitialized value $lsq_field in hash element at /home/vagrant/kohaclone/Koha/Edifact/Order.pm line 563. Use of uninitialized value $lsq_field in hash element at /home/vagrant/kohaclone/Koha/Edifact/Order.pm line 563. t/Ediorder.t .. 11/13 # Failed test 'Single Gir field OK' # at t/Ediorder.t line 104. # got: 'GIR+001+BUDGET:LFN+BRANCH:LLO+TYPE:LST+CALL:LSM' # expected: 'GIR+001+BUDGET:LFN+BRANCH:LLO+TYPE:LST+LOCATION:LSQ+CALL:LSM' Use of uninitialized value $lsq_field in hash element at /home/vagrant/kohaclone/Koha/Edifact/Order.pm line 563. Use of uninitialized value $lsq_field in hash element at /home/vagrant/kohaclone/Koha/Edifact/Order.pm line 563. $VAR1 = 'GIR+001+BUDGET:LFN+BRANCH:LLO+TYPE:LST+CALL:LSM+S_I:LVT'; $VAR2 = 'GIR+002+BUDGET:LFN+BRANCH:LLO+TYPE:LST+CALL:LSM+S_I:LVT'; Use of uninitialized value $got in string eq at (eval in cmp_ok) t/Ediorder.t line 119. # Failed test 'First part of split Gir field OK' # at t/Ediorder.t line 119. # got: undef # expected: 'GIR+002+BUDGET:LFN+BRANCH:LLO+TYPE:LST+LOCATION:LSQ+CALL:LSM' Use of uninitialized value $got in string eq at (eval in cmp_ok) t/Ediorder.t line 125. # Failed test 'Second part of split GIR field OK' # at t/Ediorder.t line 125. # got: undef # expected: 'GIR+002+S_I:LVT' # Looks like you failed 3 tests of 13. t/Ediorder.t .. Dubious, test returned 3 (wstat 768, 0x300) Failed 3/13 subtests Test Summary Report ------------------- t/Ediorder.t (Wstat: 768 Tests: 13 Failed: 3) Failed tests: 11-13 Non-zero exit status: 3 Files=1, Tests=13, 2 wallclock secs ( 0.02 usr 0.00 sys + 1.40 cusr 0.10 csys = 1.52 CPU) Result: FAIL -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 31467] New: Holds to pull page does not return the 'first patron' with the top priority hold
by bugzilla-daemon＠bugs.koha-community.org 26 Aug '22

26 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31467 Bug ID: 31467 Summary: Holds to pull page does not return the 'first patron' with the top priority hold Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: alexbuckley(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The functionality in bug 24488 of showing the correct 'first patron' details no longer always works. --- Here is an example of the current 'Holds to pull' page behaviour on master where one biblio has two biblio-level holds on it: +------------+--------------+------------+----------------+----------+---------+-------------+---------------------+ | reserve_id | biblionumber | itemnumber | borrowernumber | priority | suspend | reservedate | timestamp | +------------+--------------+------------+----------------+----------+---------+-------------+---------------------+ | 17704 | 26454 | NULL | 8450 | 1 | 0 | 2022-08-25 | 2022-08-25 15:16:34 | | 17705 | 26454 | NULL | 6998 | 2 | 0 | 2022-08-25 | 2022-08-25 15:17:22 | +------------+--------------+------------+----------------+----------+---------+-------------+---------------------+ The 'Holds to pull' page should display borrower 8450 as the 'First patron', as they have a priority of 1. But it incorrectly displays borrower 6998, instead. The 'Holds to pull' page should display the 'First patron' based on who has the top priority hold. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 31466] New: t/00-check-atomic-updates.t always fails if atomic update exists
by bugzilla-daemon＠bugs.koha-community.org 26 Aug '22

26 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31466 Bug ID: 31466 Summary: t/00-check-atomic-updates.t always fails if atomic update exists Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: blocker Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org Bug 31108 fixed the test to make it run, but now it fails if there is ever a file in the atomic updates directory. The test is unlike( $f, qr/.*pl$/, "check for unhandled atomic updates: $f" ); Which means the test passes if the atomic update filename DOES NOT MATCH the format something.pl. However atomic update files always match that format, so the test always fails and blocks packages from building. -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 12225] SIP does not respect the "no block" flag
by bugzilla-daemon＠bugs.koha-community.org 25 Aug '22

25 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12225 --- Comment #32 from Tomás Cohen Arazi <tomascohen(a)gmail.com> --- Pushed to master for 22.11. Nice work everyone, thanks! -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 12225] SIP does not respect the "no block" flag
by bugzilla-daemon＠bugs.koha-community.org 25 Aug '22

25 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12225 Tomás Cohen Arazi <tomascohen(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Passed QA |Pushed to master Version(s)| |22.11.00 released in| | -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 30242] New: Allow changing Mojolicious log level
by bugzilla-daemon＠bugs.koha-community.org 25 Aug '22

25 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30242 Bug ID: 30242 Summary: Allow changing Mojolicious log level 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 Default Mojo log level is trace. I am seeing various debug API warnings in the plack-error.log where they do not even belong. We should add something like this in Koha::REST::V1->startup: my $level = C4::Context->config('mojo_log_level') || 'warn'; $self->log->level($level); And add the mojo_log_level to koha-conf.xml. Something like: <mojo_log_level>warn</mojo_log_level> Note that we should not have such debug warnings in production logs. The above lines do not yet move the Mojo warns to an api log btw. What do you think? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 19