March 2019 - Koha-bugs - lists.koha-community.org

[Bug 15972] New: Make it possible to include additional title information in notices (such as 245$b)
by bugzilla-daemon＠bugs.koha-community.org 10 Jun '20

10 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15972 Bug ID: 15972 Summary: Make it possible to include additional title information in notices (such as 245$b) 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 For some titles the 245$a (MARC21) is not specific enough and it would be necessary to include the 245$b information in the notices, that is currently not mapped in the database. Apart from 245$b (remainder of title) other information like 245$n/$p for volumes would be nice to have. This was reported by a library using serial claims - where the title is often the same and the correct serial can only be identified with the help of additional information. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 22606] New: Memcached Issues after Upgrade
by bugzilla-daemon＠bugs.koha-community.org 08 Jun '20

08 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22606 Bug ID: 22606 Summary: Memcached Issues after Upgrade Change sponsored?: --- Product: Koha Version: 18.11 Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P5 - low Component: Installation and upgrade (command-line installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: mehmet.akgul(a)mirakil.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- After either upgrading to or directly installing Koha ver. 18.xx anytime I try to install a language pack, I get the following error: Connection to the memcached servers '_MEMCACHED_SERVERS_' failed. Are the unix socket permissions set properly? Is the host reachable? If you ignore this warning, you will face performance issues. Use of uninitialized value $pref_name in concatenation (.) or string at /usr/share/koha/misc/translator/LangInstaller.pm line 197. Use of uninitialized value $pref_name in concatenation (.) or string at /usr/share/koha/misc/translator/LangInstaller.pm line 239. On my /etc/apache2/sites-enabled/koha.conf I have set the following lines to opac and intranet, and on the about page it says memcached is running SetEnv MEMCACHED_SERVERS "127.0.0.1:11211" SetEnv MEMCACHED_NAMESPACE "koha" SetEnv MEMCACHED_SERVERS "127.0.0.1:11211" SetEnv MEMCACHED_NAMESPACE "koha-yonetim" I also can not use most of management module and opac module after the upgrade, like borrowing. Below is one such issue. Template process failed: undef error - DBIx::Class::Storage::DBI::_dbh_execute(): Table 'koha_koha.club_enrollments' doesn't exist at /usr/share/koha/lib/Koha/Objects.pm line 269 I had none of these issues in the previous versions. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 17854] New: Print Slip and Close button
by bugzilla-daemon＠bugs.koha-community.org 04 Jun '20

04 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17854 Bug ID: 17854 Summary: Print Slip and Close button 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Would like to see an enhancement on the clear screen (X) button on patron records. It would be great if it were replaced with a button with preference settings that would have the following options: Close Print Slip and Close Print Quick Slip and Close It would also be great if it could have a side action arrow giving you access to the other options that are not defaulted. This feature would help with staff closing accounts (clearing screen) when done, and making slip printing stand out a little better. It would also be a streamlined workflow. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 26

[Bug 22381] New: Wording on Calendar-related system preferences not standardized
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '20

03 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22381 Bug ID: 22381 Summary: Wording on Calendar-related system preferences not standardized Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Target Milestone: --- We've got four very similar system preferences with very different wording, which fosters confusion. ExcludeHolidaysFromMaxPickUpDelay is worded is "(Allow/Don't Allow) Closed days to be taken into account in reserves max pickup delay." OverdueNoticeCalendar is worded as "(Use Calendar/Ignore Calendar) when working out the period for overdue notices." useDaysMode is "Calculate the due date using (the calendar to skip days the library is closed/the calendar to push the due date to the next open day/circulation rules only)" finesCalendar is "Calculate fines based on days overdue (directly/not including days the library is closed." Standardizing wording across these four would make them all clearer as a group. If nothing else, I'd love to see the word "calendar" included somewhere in ExcludeHolidaysFromMaxPickUpDelay so it comes up in an easy search with the others. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 40

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