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

[Bug 25310] New: Ability to centrally turn off sending/generating of HOLD notices
by bugzilla-daemon＠bugs.koha-community.org 02 Jun '20

02 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25310 Bug ID: 25310 Summary: Ability to centrally turn off sending/generating of HOLD notices 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org As libraries slowly start to reopen we've had this request a few times and there is not really a great way to do it at the moment. When you want to turn off HOLD notices globally you can: - Change the messaging settings for every patron. You can use the script, but you can't get back their individual settings easily and you need to go server side via SQL. - Empty out the Email template (requires you have a print one still set up). This appears to work, but is hacky. It would be nice, if there was a way to do this in the configuration. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 17532] New: koha-shell does not propagate the error code
by bugzilla-daemon＠bugs.koha-community.org 01 Jun '20

01 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17532 Bug ID: 17532 Summary: koha-shell does not propagate the error code Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 26

[Bug 20624] New: Allow switching off the OAuth2 client credentials grant
by bugzilla-daemon＠bugs.koha-community.org 01 Jun '20

01 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20624 Bug ID: 20624 Summary: Allow switching off the OAuth2 client credentials grant Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 43

[Bug 23250] New: koha-create generates broken mysql password
by bugzilla-daemon＠bugs.koha-community.org 29 May '20

29 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23250 Bug ID: 23250 Summary: koha-create generates broken mysql password Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: blocker Priority: P5 - low Component: Installation and upgrade (command-line installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: mirko(a)abunchofthings.net QA Contact: testopia(a)bugs.koha-community.org Using koha-create with latest master generates a broken mysql password in koha-conf.xml, like this > <pass>B6_uW%vW"__DB_PASS__`1l(Gm</pass> The problem does not appear when I revert the changes from bug 23090. This will make every new instance unusable. It's in the nightly, that means new devboxes will be broken too I guess. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 18330] New: REST API: Date-time handling
by bugzilla-daemon＠bugs.koha-community.org 29 May '20

29 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18330 Bug ID: 18330 Summary: REST API: Date-time handling Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: lari.taskula(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org Swagger2 wants dates and date-times as defined in RFC3339, https://xml2rfc.tools.ietf.org/public/rfc/html/rfc3339.html#anchor14 Make sure each object property has a format date or date-time defined where needed. We should include information on time zone and use an appropriate separator "T" between date and time, e.g.: 2017-03-24T14:00:00+02:00 2017-03-24T12:00:00Z -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 30

[Bug 18674] New: Show timezone for Perl and MySQL on the About Koha page
by bugzilla-daemon＠bugs.koha-community.org 28 May '20

28 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18674 Bug ID: 18674 Summary: Show timezone for Perl and MySQL on the About Koha page Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: About Assignee: nengard(a)gmail.com Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org With the pushing of Bug 18299, we no longer have a quick way of checking the timezone of the Perl and MySQL connection. We should add some code to the About Koha page to show this info. -- You are receiving this mail because: You are watching all bug changes.

1 33

[Bug 25133] New: Specify Due date changes from PM to AM if library has their TimeFormat set to 12hr
by bugzilla-daemon＠bugs.koha-community.org 28 May '20

28 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25133 Bug ID: 25133 Summary: Specify Due date changes from PM to AM if library has their TimeFormat set to 12hr Change sponsored?: --- Product: Koha Version: 19.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Prior to 19.05.08, when due date was specified in the checkout, the time in the box would show in 24hr format (e.g. 15:59) while the due date in the patron's checkouts would show in 12hr format (e.g. 3:59 PM) When using the specified due date in the same transaction, - check an item out and the box would remain with 15:59 while the due date would display 3:59 PM - check a second item out and the box would continue to display 15:59 and the due date 3:59 PM After 19.05.08, the format in the specify a due date box shows in 24hr format and the due date in 12hr format (in patron checkouts) as before. However, on the second transaction, the box converts to 3:59 AM and that time will be 3:59 AM on the patron's checkout. This process only occurs if the library is using the TimeFormat at 12 hours in the system preferences and not 24 hours in the TIme format. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 46

[Bug 19197] New: Lower case "or" results in broken ElasticSearch queries
by bugzilla-daemon＠bugs.koha-community.org 28 May '20

28 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19197 Bug ID: 19197 Summary: Lower case "or" results in broken ElasticSearch queries Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: glasklas(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org In some places a literal "or" is used to build search queries which probably works with Zebra, but not with ElasticSearch. Replacing theses occurrences fixes the problem in those cases. This is just a band aid, not addressing the real issue which is (I guess) that a query abstraction interface is needed, and zebra-specific syntax should not be used directly in search queries, but this will at least solve this particular issue. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 23322] New: Elasticsearch - Record matching fails when multiple keys exist
by bugzilla-daemon＠bugs.koha-community.org 28 May '20

28 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23322 Bug ID: 23322 Summary: Elasticsearch - Record matching fails when multiple keys exist Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com For a record with multipel matchpoints C4/Matcher.pm combines terms using 'or' however, ES expects 'OR' so the search fails To test: 0 - Set SearchEngine to ElasticSearch 1 - Import the example record (a version is included in sample data in devbox/testing docker so you can skip) 2 - Stage the attached example record 3 - Match using 'ISBN' rule 4 - No matches found -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 22536] New: Display problem in Holds to Pull report
by bugzilla-daemon＠bugs.koha-community.org 28 May '20

28 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22536 Bug ID: 22536 Summary: Display problem in Holds to Pull report Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: david.roberts(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Target Milestone: --- Created attachment 86732 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=86732&action=ed… Screenshot In 18.11, the holds to pull screen displays in the table when an bibliographic record has more than one copy (see attached screenshot). This seems to be related to the template: </td> <td>[% reserveloo.itemcallnumber | html %]</td> <td>[% reserveloo.copyno | html %]</td> <td>[% reserveloo.enumchron | html %]</td> <td> Removing the html part of the line fixes the problem, but isn't a very secure long-term solution. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17