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

[Bug 31068] New: Context for translation: Print (verb) vs. Print (noun)
by bugzilla-daemon＠bugs.koha-community.org 26 Aug '22

26 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31068 Bug ID: 31068 Summary: Context for translation: Print (verb) vs. Print (noun) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr In English, the word "print" is the same whether it is a verb (to print something) or a noun (a print of something). In French, these two have different spellings, "Imprimer" or "Imprimé" (almost the same, and pronounced the same, but when one is used instead of the other, it hurts my eyes!) When the word is in a sentence, it's not too difficult to translate, but in cases where the string to translate is simply "Print", it is often used in different cases (noun or verb). Here are the strings where "Print" is alone #: koha-tmpl/intranet-tmpl/prog/en/modules/basket/basket.tt:61 #: koha-tmpl/intranet-tmpl/prog/en/modules/members/boraccount.tt:109 #: koha-tmpl/intranet-tmpl/prog/en/modules/members/boraccount.tt:111 #: koha-tmpl/intranet-tmpl/prog/en/modules/serials/routing-preview-slip.tt:39 #: koha-tmpl/intranet-tmpl/prog/en/modules/tools/letter.tt:479 #: koha-tmpl/intranet-tmpl/prog/en/modules/tools/overduerules.tt:98 #: koha-tmpl/intranet-tmpl/prog/en/includes/cat-toolbar.inc:171 #: koha-tmpl/intranet-tmpl/prog/en/includes/columns_settings.inc:5 #: koha-tmpl/intranet-tmpl/prog/en/includes/modals/cashup_summary.inc:29 #: koha-tmpl/intranet-tmpl/prog/en/includes/str/tinymce_i18n.inc:2 #, c-format msgid "Print" msgstr "Imprimer" #: koha-tmpl/intranet-tmpl/prog/en/modules/circ/returns.tt:118 #: koha-tmpl/intranet-tmpl/prog/en/includes/members-toolbar.inc:22 #, c-format msgid "Print " msgstr "Imprimer " In the following pages, it is meant as a verb ("Print" button): basket.tt boraccount.tt routing-preview-slip.tt cat-toolbar.inc columns_settings.inc cashup_summary.inc tinymce_i18n.inc returns.tt members-toolbar.inc In the following pages, it is meant as a noun (type of message transport type, as opposed to email or sms): letter.tt overduerules.tt I propose to add some context where the meaning is the type of message transport. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 31153] New: Search bar not visible on recalls history page
by bugzilla-daemon＠bugs.koha-community.org 26 Aug '22

26 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31153 Bug ID: 31153 Summary: Search bar not visible on recalls history page Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When accessing the 'Recalls history' tab in a patron's file in the staff interface, the section where the Koha logo and search bar are disappears. To test: 1) Turn on recalls 1.1) In Administration > Global system preferences, enable UseRecalls 1.2) Add recalls permissions in your circulation rules 2) In the OPAC, log in as a patron 3) Find a record with checked out items and place a recall 4) In the staff interface, go to the patron's account 5) Click on any tab on the left in the patron's account (e.g. Holds history) --> Note that the Koha logo and search bar is at the top of the page between the module menu and the breadcrumbs 6) Click on the 'Recalls history' tab --> Note that the Koha logo and search bar disappear -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 20

[Bug 26751] New: Fatal exception if only one repo defined
by bugzilla-daemon＠bugs.koha-community.org 26 Aug '22

26 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26751 Bug ID: 26751 Summary: Fatal exception if only one repo defined Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Plugin architecture Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org It seems that it always expects an array. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 22

[Bug 24633] New: Add support for gitlab searching of plugins
by bugzilla-daemon＠bugs.koha-community.org 26 Aug '22

26 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24633 Bug ID: 24633 Summary: Add support for gitlab searching of 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 As the title says, add support for gitlab to the work started in bug 23975 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 48

[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 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 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

[Bug 30108] New: Allow making hold dates required
by bugzilla-daemon＠bugs.koha-community.org 25 Aug '22

25 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30108 Bug ID: 30108 Summary: Allow making hold dates required 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: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Make it possible that the two hold dates on opac-reserve (starts on and not needed after) are mandatory. Enable OPACAllowHoldDateInFuture to see the first one. A new pref could include the various (4) combinations. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 32