January 2023 - Koha-bugs - lists.koha-community.org

[Bug 32612] New: Koha background worker should log to the worker-error.log
by bugzilla-daemon＠bugs.koha-community.org 23 Feb '23

23 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32612 Bug ID: 32612 Summary: Koha background worker should log to the worker-error.log Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 66

[Bug 17987] New: Changing PatronSelfRegistrationDefaultCategory to a dropdown menu syspref
by bugzilla-daemon＠bugs.koha-community.org 23 Feb '23

23 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17987 Bug ID: 17987 Summary: Changing PatronSelfRegistrationDefaultCategory to a dropdown menu syspref Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleishaamohia(a)hotmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Rather than a free text syspref where a user can easily put in a category that doesn't exist. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 31017] New: Add type field for vendors
by bugzilla-daemon＠bugs.koha-community.org 23 Feb '23

23 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31017 Bug ID: 31017 Summary: Add type field for vendors 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Some libraries have many vendors, and they serve different purposes e.g. booksellers vs donors vs electronic resource providers It would be nice to have a way to differentiate these types for reporting (and eventually for searching) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 50

[Bug 29870] New: Notice not delivered by default smtp server
by bugzilla-daemon＠bugs.koha-community.org 23 Feb '23

23 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29870 Bug ID: 29870 Summary: Notice not delivered by default smtp server 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: gveranis(a)dataly.gr QA Contact: testopia(a)bugs.koha-community.org When you have one default smtp server configuration at koha_conf.xml (we called 'A' ) and another smtp server (we called 'B') at administration UI with two libraries that one of them is set it to default and the other set it to the smtp server 'B' then when the process_message_queue.pl is executing in order to send notices, users from library with the default server not receiving anything , but the users from library with the 'B' smtp server receive everything. The configurations between the two smtp servers A and B are the same, just one time we have passed as default on xml and the other as smtp server from UI , it seems that from UI the functions etc is working better that to get values for the object from xml. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 32490] New: When there's a broken spec, Mojolicious fails to capture the error properly
by bugzilla-daemon＠bugs.koha-community.org 23 Feb '23

23 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32490 Bug ID: 32490 Summary: When there's a broken spec, Mojolicious fails to capture the error properly Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com CC: tomascohen(a)gmail.com At some point we broke mojolious's built in error processing code. Instead of a useful stack track we now get a bunch of internal Mojo error code instead and nothing useful to point at the actual underlying problem. >> The application raised the following error: Can't use an undefined value as an ARRAY reference at template mojo/debug.html.ep line 288. Context: 283: </div> 284: <div class="tap tap-border-top">tap for more</div> 285: </div> 286: </div> 287: <div class="row"> 288: % if (@{app->log->history}) { 289: % my $log = join '', map { scalar app->log->format->(@$_) } @{app->log->history}; 290: <pre class="mojo-terminal"><code class="nohighlight"><%= $log %></code></pre> 291: % } 292: % else { 293: <div class="alert alert-warning wide" role="alert"> Traceback (most recent call first): File "template mojo/debug.html.ep", line 288, in "Mojo::Template::Sandbox::6bff7bf20514502e6c04c41933771297" . . . internal mojo stuff File "/usr/bin/starman", line 38, in "main" and the StackTrace middleware couldn't catch its stack trace, possibly because your application overrides $SIG{__DIE__} by itself, preventing the middleware from working correctly. Remove the offending code or module that does it: known examples are CGI::Carp and Carp::Always. For example I traced this back a little in the server logs where it points to Koha::Logger not implimenting the 'history' method. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 31333] New: Allow the ability to make purchase suggestions to be set by borrower type
by bugzilla-daemon＠bugs.koha-community.org 22 Feb '23

22 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31333 Bug ID: 31333 Summary: Allow the ability to make purchase suggestions to be set by borrower type Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: rkuiper(a)roundrocktexas.gov QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com We are planning to create levels of membership at our library and we would like to prevent some borrower types from placing purchase suggestions. Currently, the system preference for purchase suggestions is 'Allow' or 'Don't Allow' for all borrower types. We would like to set the ability to place purchase suggestion for each borrow type. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 60

[Bug 31475] New: Group system preferences for suggestions on OPAC tab under new heading
by bugzilla-daemon＠bugs.koha-community.org 22 Feb '23

22 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31475 Bug ID: 31475 Summary: Group system preferences for suggestions on OPAC tab under new heading Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com There are quite a few of suggestion related preferences under different headings on the OPAC tab. It would be nice if they appeared as a group under one heading. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 28138] New: Add system preference to make the payment type required
by bugzilla-daemon＠bugs.koha-community.org 22 Feb '23

22 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28138 Bug ID: 28138 Summary: Add system preference to make the payment type required Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org The payment type is already required when using the cash register feature, but some users want to force selecting a payment type even when cash registers are not used -- You are receiving this mail because: You are watching all bug changes.

1 31

[Bug 30563] New: Add system preference to make the cash register field required when collecting a payment
by bugzilla-daemon＠bugs.koha-community.org 22 Feb '23

22 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30563 Bug ID: 30563 Summary: Add system preference to make the cash register field required when collecting a payment Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Patrons Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Currently, the cash register field is required only if the CASH payment type is selected. Some users want to make it required no matter which payment type is selected. -- You are receiving this mail because: You are watching all bug changes.

1 13

[Bug 32054] New: GetImportRecordMatches returns the wrong match when passed 'best only'
by bugzilla-daemon＠bugs.koha-community.org 22 Feb '23

22 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32054 Bug ID: 32054 Summary: GetImportRecordMatches returns the wrong match when passed 'best only' Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The routine orders by score/biblionumber desc - it limits to the first match when 'best only' is passed. With bug 22785 we introduced a 'chosen' field to allow the best, or no match, be chosen We need to honor this when getting the matches This causes order imports to choose the wrong match -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23