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

[Bug 31206] New: Highlight logged in library in green in Circ History
by bugzilla-daemon＠bugs.koha-community.org 27 Sep '23

27 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31206 Bug ID: 31206 Summary: Highlight logged in library in green in Circ History Change sponsored?: --- Product: Koha Version: 21.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: madamyk(a)ckls.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com This is based on the same idea that was used in Bug 10902 (pushed to 21.11; https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10902) I think it might be helpful to have the same kind of highlighting feature in other areas of Koha for consortiums. Specifically, in this case, highlighting the logged-in library when looking at circ history. However, I'm not sure if this would be "too much of a good thing," i.e. if we started adding highlighting all over the place, is it going to be more of a problem than a solution? I'm open to input on this. :) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 22719] New: Suggestion Maintenance
by bugzilla-daemon＠bugs.koha-community.org 27 Sep '23

27 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22719 Bug ID: 22719 Summary: Suggestion Maintenance Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- There needs to be a way for Superlibrarians to see and manage all suggestions, besides switching current libraries. There also needs to be setting (maybe at the bottom of the page) for each library to choose how old of each category to hold on to, and what action to take: delete, nag via e-mail daily, etc. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 29716] New: [DOCS] Automated screenshots
by bugzilla-daemon＠bugs.koha-community.org 27 Sep '23

27 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29716 Bug ID: 29716 Summary: [DOCS] Automated screenshots Change sponsored?: --- Product: Koha Version: master Hardware: All URL: https://gitlab.com/davidnind/koha-automated-screenshot s OS: All Status: ASSIGNED Severity: enhancement Priority: P4 Component: Documentation Assignee: david(a)davidnind.com Reporter: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org See if we can automate the capture of as many screenshots as possible for the Koha documentation, in as many languages as possible. -- You are receiving this mail because: You are watching all bug changes.

1 8

[Bug 29992] New: Default Apache config should contain CGIPassAuth directive
by bugzilla-daemon＠bugs.koha-community.org 27 Sep '23

27 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29992 Bug ID: 29992 Summary: Default Apache config should contain CGIPassAuth directive Change sponsored?: --- Product: Koha Version: unspecified 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: andrew.isherwood(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org By default, authorization headers are stripped out by Apache and therefore do not reach the underlying CGI script. This causes problems when Koha is receiving API requests that contain them as the client just receives a 401 response, even if a valid token was provided. I propose we add the CGIPassAuth directive to the API Directory blocks. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 25948] New: Clean up apache protocols and ciphers
by bugzilla-daemon＠bugs.koha-community.org 27 Sep '23

27 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25948 Bug ID: 25948 Summary: Clean up apache protocols and ciphers Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Installation and upgrade (command-line installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: mtompset(a)hotmail.com QA Contact: testopia(a)bugs.koha-community.org SSLCipherSuite was truncated and different between the OPAC and Intranet sections. While cleaning that up, removed TLSv1 as it is supposed to be deprecated already. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 19014] New: Limit auto-renewal notice to item due immediately. Template Toolkit change ?
by bugzilla-daemon＠bugs.koha-community.org 26 Sep '23

26 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19014 Bug ID: 19014 Summary: Limit auto-renewal notice to item due immediately. Template Toolkit change? Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices 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 in 17.05: All copies of an item with auto-renewal enabled, reserved at the title level. Due dates of copies on loan include today, and various dates into the future, some many weeks ahead. When the auto-renewal job runs, Koha is sending an AUTO_RENEWAL email to ALL the users warning them ALL of renewal failure, using the [% ELSIF checkout.auto_renew_error == 'on_reserve' %] Desired functionality in 17.05: When the auto-renewal job runs, Koha should only send an AUTO_RENEWAL email to the user (or possibly users) whose copy is due back today, on the day the auto-renewal job runs. Other people who have copies on loan but which are not yet due back yet should not be contacted by the AUTO_RENEWAL email. Users contacted in this way are being very puzzled and confused. Could this be achieved by an edit to the condition in the template toolkit? So rather this: [% ELSIF checkout.auto_renew_error == 'on_reserve' %] This item has been reserved by another reader. … we have something like this: [% ELSIF checkout.auto_renew_error == 'on_reserve' && checkout.date_due %==today %] This item has been reserved by another reader. Would that work? Is a second condition permissible? How should it be worded? Ray Delahunty University of the Arts London -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 121

[Bug 28010] New: add plugin to modify record in "opac-detail.pl"
by bugzilla-daemon＠bugs.koha-community.org 26 Sep '23

26 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28010 Bug ID: 28010 Summary: add plugin to modify record in "opac-detail.pl" 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: koha(a)trust-box.at QA Contact: testopia(a)bugs.koha-community.org Created attachment 118560 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=118560&action=e… patch to opac-detail.pl I (guess I) need the abiltiy to change how records are beeing display in in opac-detail.pl Specifically I want to change the content of a record depending if a user is logged in or not for ebook renting So it would be great to have the ability to have a plugin hook there, something like 1 diff --git a/opac-detail.pl.orig b/opac-detail.pl 2 index e74cf4b..b46eb90 100755 3 --- a/opac-detail.pl.orig 4 +++ b/opac-detail.pl 5 @@ -217,6 +217,16 @@ if ( $xslfile ) { 6 $variables = { %$variables, %$plugin_variables }; 7 } 8 9 + $record = Koha::Plugins->call_apply( 10 + 'munge_record', 11 + $record, 12 + { 13 + patron => $patron, 14 + interface => 'opac', 15 + caller => 'opac-detail', 16 + } 17 + ); 18 + additionally I have a proposal to extend/modify the plugin system a little bit: I don't like the idea very much that the caller of a plugin has to take care of merging the results so the first step would be to add the ability that a plugin works recursively on a variable diff --git a/Plugins.pm.orig b/Plugins.pm index 11d44dc..71461de 100644 --- a/Plugins.pm.orig +++ b/Plugins.pm @@ -82,6 +82,35 @@ sub call { return @responses; } +=head2 call_apply + +Calls a plugin method for all enabled plugins, reworking on the same input and returning it. +ideally the caller of a plugin must not know how to merge the results +so maybe also implement a "merge" method in the plugin + + @responses = Koha::Plugins->call_apply($method, $work_var, @args) + +=cut + +sub call_apply { + my ($class, $method, $work_var, @args) = @_; + + if (C4::Context->config('enable_plugins')) { + my @plugins = $class->new({ enable_plugins => 1 })->GetPlugins({ method => $method }); + @plugins = grep { $_->can($method) } @plugins; + foreach my $plugin (@plugins) { + my $work_var = eval { $plugin->$method($work_var, @args) }; + if ($@) { + warn sprintf("Plugin error (%s): %s", $plugin->get_metadata->{name}, $@); + next; + } + } + + } + return $work_var; +} + + =head2 GetPlugins In another my idea would be to have an optional "merge" method for a certain type of plugins to avoid code like 206 207 my @plugin_responses = Koha::Plugins->call( 208 'opac_detail_xslt_variables', 209 { 210 biblio_id => $biblionumber, 211 lang => $lang, 212 patron_id => $borrowernumber 213 214 } 215 ); 216 for my $plugin_variables ( @plugin_responses ) { 217 $variables = { %$variables, %$plugin_variables }; 218 } 219 and be able to write something along the lines of 206 207 my $variables = Koha::Plugins->call( 208 'opac_detail_xslt_variables', + $variables, 209 { 210 biblio_id => $biblionumber, 211 lang => $lang, 212 patron_id => $borrowernumber 213 214 } 215 ); I hope I haven't packed to much into one issue, thanks a lot -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 26146] New: Patron duplicate matching - fuzzy matching?
by bugzilla-daemon＠bugs.koha-community.org 25 Sep '23

25 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26146 Bug ID: 26146 Summary: Patron duplicate matching - fuzzy matching? 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: sally.healey(a)cheshiresharedservices.gov.uk QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Koha doesn't have a middle name field so librarians may try to use the first name field to hold both first names and middle names. This means that Koha's duplicate patron feature doesn't work, e.g. Brian David Jones already exists on the system. Patron is added as Brian Jones. Koha doesn't find the duplicate patron, because it thinks "Brian" is different to "Brian David" OR Brian Jones already exists on the system. Patron is added as Brian David Jones. Koha doesn't find the duplicate patron, because it thinks "Brian David" is different to "Brian" Is it possible to have fuzzy matching on the first name field, so "Brian Jones" would match "Brian David Jones" and "Brian David Jones" would match "Brian Jones" ? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 22449] New: Improve Elastic search facet setting UI
by bugzilla-daemon＠bugs.koha-community.org 25 Sep '23

25 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22449 Bug ID: 22449 Summary: Improve Elastic search facet setting UI Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: josef.moravec(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- As discussed on bug 18235, the UI of facet settings should be improved - probably make it separate tab on elastic search admin page. -- You are receiving this mail because: You are watching all bug changes.

1 8

[Bug 26303] New: [OMNIBUS] Preparing for Perl 7
by bugzilla-daemon＠bugs.koha-community.org 25 Sep '23

25 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26303 Bug ID: 26303 Summary: [OMNIBUS] Preparing for Perl 7 Change sponsored?: --- Product: Koha Version: unspecified 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: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org https://www.perl.com/article/announcing-perl-7/ http://blogs.perl.org/users/brian_d_foy/2020/06/the-perl-7-tldr.html -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6