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

[Bug 25042] New: Koha::Schema::Result::Reserve redefines item and biblio rs
by bugzilla-daemon＠bugs.koha-community.org 08 Apr '20

08 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25042 Bug ID: 25042 Summary: Koha::Schema::Result::Reserve redefines item and biblio rs Change sponsored?: --- Product: Koha Version: unspecified 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: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 11703 From: commit 82275fa2db63b7d2358897aad72b845a73cb8bda Bug 11703 - Convert checkouts table to ajax datatable It adds 2 belongs_to, item and biblio. But they already exist (as the FKs exist) +__PACKAGE__->belongs_to( + "item", + "Koha::Schema::Result::Item", + { itemnumber => "itemnumber" }, + { + is_deferrable => 1, + join_type => "LEFT", + on_delete => "CASCADE", + on_update => "CASCADE", + }, +); +__PACKAGE__->belongs_to( + "biblio", + "Koha::Schema::Result::Biblio", + { biblionumber => "biblionumber" }, + { + is_deferrable => 1, + join_type => "LEFT", + on_delete => "CASCADE", + on_update => "CASCADE", + }, +); This code needs to be removed. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11703 [Bug 11703] Convert checkouts table to ajax datatable -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 15668] Add column configuration to the items table in staff detail pages
by bugzilla-daemon＠bugs.koha-community.org 08 Apr '20

08 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15668 --- Comment #15 from Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> --- (In reply to Lucas Gass from comment #14) > Jonathan, > > Because that what I see was done in opac-detail.tt. Would you recommend that > we not use it? IIRC it should be used when the order of the columns is dynamic, for instance. It would have required less change to not use it in your case. But now it's done, so I don't think it should be a problem. I thought you had a (real) reason to use it :) -- You are receiving this mail because: You are watching all bug changes.

1 0

[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 08 Apr '20

08 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 25077] New: Kabur Gans
by bugzilla-daemon＠bugs.koha-community.org 07 Apr '20

07 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25077 Bug ID: 25077 Summary: Kabur Gans Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: About Assignee: koha-bugs(a)lists.koha-community.org Reporter: kabur667(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 102504 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=102504&action=e… Kaburgans Kabur Gans -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 25075] New: Revenge
by bugzilla-daemon＠bugs.koha-community.org 07 Apr '20

07 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25075 Bug ID: 25075 Summary: Revenge Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Browser compatibility Assignee: oleonard(a)myacpl.org Reporter: fikridiyanto52(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 102495 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=102495&action=e… Revenge -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 25073] New: Pepeq
by bugzilla-daemon＠bugs.koha-community.org 07 Apr '20

07 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25073 Bug ID: 25073 Summary: Pepeq Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: dhittamvan60(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 102472 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=102472&action=e… Ppq -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 14237] allow bibs to be added to course without items
by bugzilla-daemon＠bugs.koha-community.org 07 Apr '20

07 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14237 emily(a)palnet.info changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |emily(a)palnet.info --- Comment #5 from emily(a)palnet.info --- I just wanted to say this is still a relevant issue. With more books being published electronically, the need for a barcode isn't really relevant so it would be nice to be able to add to a course reserve without having to apply barcodes to items that otherwise don't really need them. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 24067] New: Refactor REST API allow-owner authorization logic
by bugzilla-daemon＠bugs.koha-community.org 07 Apr '20

07 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24067 Bug ID: 24067 Summary: Refactor REST API allow-owner authorization logic Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST api Assignee: koha-bugs(a)lists.koha-community.org Reporter: lari.taskula(a)hypernova.fi It is possible to authorize patron an access to their own resources by defining "allow-owner" under x-koha-authorization block in endpoint's OpenAPI specification. Currently the logic for this type of authorization is centralized under Koha::REST::V1::Auth::check_object_ownership with some messy, hard to understand and possibly at some point in future even insecure logic. A better and more flexible solution is to have each REST API controller handle the "allow-owner" authorization on their own. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 14697] Extend and enhance "Claims returned" lost status
by bugzilla-daemon＠bugs.koha-community.org 07 Apr '20

07 Apr '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14697 --- Comment #82 from Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> --- (In reply to Jonathan Druart from comment #80) > Also, there are several strings in checkouts.js that is not translatable. Reported on bug 24783. -- You are receiving this mail because: You are watching all bug changes.

1 0