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

[Bug 20364] New: Show languages from MARC21 field 041 in intranet
by bugzilla-daemon＠bugs.koha-community.org 08 Apr '20

08 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20364 Bug ID: 20364 Summary: Show languages from MARC21 field 041 in intranet Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: pasi.kallinen(a)joensuu.fi QA Contact: testopia(a)bugs.koha-community.org The encoded languages from MARC21 field 041 are not shown anywhere. These are quite important for example DVD video material (subtitle languages). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 28

[Bug 24861] New: Unable to setPatronPasswordPublic using REST API
by bugzilla-daemon＠bugs.koha-community.org 07 Apr '20

07 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24861 Bug ID: 24861 Summary: Unable to setPatronPasswordPublic using REST API Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au I've tried POST /api/v1/public/patrons/{patron_id}/password with RESTPublicAPI enabled (using koha-testing-docker with Plack enabled), but I keep getting 401 errors. curl http://localhost:8080/api/v1/public/patrons/42/password -d '{"old_password":"OLD","password":"NEW","password_repeated":"NEW"}' {"error":"Authentication failure."} With RESTBasicAuth enabled and using the username and password for patron #42: curl -u <username:password> http://localhost:8080/api/v1/public/patrons/42/password -d '{"old_password":"OLD","password":"NEW","password_repeated":"NEW"}' {"error":"Authorization failure. Missing required permission(s).","required_permissions":null} Perhaps I'm doing something wrong but this looks like a bug to me? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11

[Bug 20359] New: Auto-Renew notice not able to pull branch information
by bugzilla-daemon＠bugs.koha-community.org 06 Apr '20

06 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20359 Bug ID: 20359 Summary: Auto-Renew notice not able to pull branch information 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Information from the branches table cannot be pulled into the AUTO_RENEW notice. This is an issue for libraries that want to include library contact information in their notices that will automatically update when values are changed in Koha or for multi-branch systems that want their notices to specify where the renewed item is from. To replicate: 1: Write an AUTO_RENEW notice including either <<branches.branchname>> or [% branch.branchname %] 2: Run the auto-renew cron with notices 3: Observe that branch info is not included in the notice -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 18110] New: Adds FR to the syspref AddressFormat
by bugzilla-daemon＠bugs.koha-community.org 06 Apr '20

06 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18110 Bug ID: 18110 Summary: Adds FR to the syspref AddressFormat Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: baptiste.wojtkowski(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 61

[Bug 24653] New: Failing tests in 19.05.x
by bugzilla-daemon＠bugs.koha-community.org 06 Apr '20

06 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24653 Bug ID: 24653 Summary: Failing tests in 19.05.x Change sponsored?: --- Product: Project Infrastructure Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Continuous Integration Assignee: tomascohen(a)gmail.com Reporter: lucas(a)bywatersolutions.com tests are failing in 19.05: -t/db_dependent/Koha/Charges/Fees.t -t/db_dependent/SIP/Transaction.t Something is not accounted for when there is no ALL/ALL circ rule. -- You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 25018] New: Jenkins is not running the test with $ENV{_} eq 'prove'
by bugzilla-daemon＠bugs.koha-community.org 06 Apr '20

06 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25018 Bug ID: 25018 Summary: Jenkins is not running the test with $ENV{_} eq 'prove' 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 In some tests we want to know if we are in a testing environment. When run the usual way, our trick works, the perl interpreter matches 'prove': $ENV{_} eq 'prove' In other situations, we have the KOHA_NO_TABLE_LOCKS environment variables, for the SendCirculationAlert race conditions (see bug 15854 and bug 18364). For unknown reasons, Jenkins runs the tests with /usr/bin/perl. -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 20674] New: One off report
by bugzilla-daemon＠bugs.koha-community.org 05 Apr '20

05 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20674 Bug ID: 20674 Summary: One off report Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: tlamannajr(a)chplnj.org QA Contact: testopia(a)bugs.koha-community.org Right now the only way to create and run a report is to save it to a list, but there are plenty of times I just need a one-off report and it's a bit of a pain to have to create and name a report then delete in when I'm done. This clutters up the reports list a lot. Not a massive problem, but I'm hoping we can streamline one off reports. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 24755] New: chance to define expiration hour for in-site loans
by bugzilla-daemon＠bugs.koha-community.org 05 Apr '20

05 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24755 Bug ID: 24755 Summary: chance to define expiration hour for in-site loans Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: hagud(a)orex.es QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com on reserves.expirationdate's mysql format is date, however I think it could be datetime I have identified that many koha's librries are cataloguing pc's, study rooms as in-ite loans, the students may hold this kind of material, but the hold expiration date is suitable for books, but not suitable at all for in-site loans. It should be great if we could define expiration days for home-loans and expiration hour for in-site loans It should be also great if we could define close hours to do not assign a date_due beyond the close date -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 24505] New: Print overdue notice with html gives message: "The following terms were not matched and replaced"
by bugzilla-daemon＠bugs.koha-community.org 05 Apr '20

05 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24505 Bug ID: 24505 Summary: Print overdue notice with html gives message: "The following terms were not matched and replaced" Change sponsored?: --- Product: Koha Version: 19.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: somesecretemail(a)mailinator.com QA Contact: testopia(a)bugs.koha-community.org In overdue notice for the option "print" we use a template containing html. After running the overdue_notices cron job: > sudo perl /usr/share/koha/bin/cronjobs/overdue_notices.pl -t -v -html /tmp a message is presented by the system "The following terms were not matched and replaced: html, div, etc...". It seems like the system confuses the "<< >>" enclosed text with the html components. Nothing from the template is added to the generated html file. This bug is exactly the same as this bug fixed in 2013: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10720 You can also find it well documented in the commit here: https://gitlab.deichman.no/digibib/Koha/commit/394be84dcd65a4569d0467bc12b9… -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 24504] New: branchtransfers.pl - Entering checked out item cause Internal Server Error
by bugzilla-daemon＠bugs.koha-community.org 05 Apr '20

05 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24504 Bug ID: 24504 Summary: branchtransfers.pl - Entering checked out item cause Internal Server Error Change sponsored?: --- Product: Koha Version: 19.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: fraktik(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Interestingly enough this is happening only first time (item get checked in and then this "Internal Server Error" blank page appears). If I get back to /cgi-bin/koha/circ/branchtransfers.pl and put the same barcode second time, the transfer is processed without any further error. Possible relation to the Bug 3536 - Checked In item requiring transfer does not consistently trigger transfer prompt (https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=3536) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4