June 2022 - Koha-bugs - lists.koha-community.org

[Bug 25032] New: Generic unhandled exception handling
by bugzilla-daemon＠bugs.koha-community.org 01 Feb '23

01 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25032 Bug ID: 25032 Summary: Generic unhandled exception handling 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: tomascohen(a)gmail.com The idea is to clean things in the controllers and provide a reliable way to control the logging of unhandled exceptions for debugging. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 59

[Bug 29595] New: missing Content-Type / HTTP 415 check for POST requests to /api/v1/patrons
by bugzilla-daemon＠bugs.koha-community.org 01 Feb '23

01 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29595 Bug ID: 29595 Summary: missing Content-Type / HTTP 415 check for POST requests to /api/v1/patrons Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: divinity76(a)gmail.com if you send a POST request to /api/v1/patrons with the header Content-Type: application/x-www-form-urlencoded which is a default header for curl and libcurl with POST requests, by the way, then Koha will try to parse it as a JSON, which leads to questions like this https://stackoverflow.com/questions/68106741/post-koha-patrons-to-koha-lms-… and responses like this ``` { //Here is missing some code. "errors": [{ "message": "Missing property.", "path": "/body/address" }, { "message": "Missing property.", "path": "/body/category_id" }, { "message": "Missing property.", "path": "/body/city" }, { "message": "Missing property.", "path": "/body/library_id" }, { "message": "Missing property.", "path": "/body/surname" }], "status": 400 } ``` while HTTP 400 is a pretty good response, the correct response for unsupported Content-Type is actually >HTTP/1.1 415 Unsupported Media Type and the error message could be something like { "errors": [{ "message": "request body must be application/json" }], ] -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 27064] New: Transferring an item with a hold allows the user to set a hold waiting without transferring to the correct branch
by bugzilla-daemon＠bugs.koha-community.org 01 Feb '23

01 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27064 Bug ID: 27064 Summary: Transferring an item with a hold allows the user to set a hold waiting without transferring to the correct branch Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com To recreate: 1 - Place a hold for delivery at Library B 2 - Sign in at Library A 3 - Browse to Circulation->Transfers 4 - Attempt to transfer an item on the title with the hold to Library B 5 - You get a notice that hold was found (missing patron/branch info) 6 - You have the option to set the hold waiting - click it 7 - The transfer is generated and marked completed 8 - The hold is marked as waiting, but the item is still at Library A and no transfer is active 9 - The patron is notified that the hold is waiting -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 80

[Bug 25854] New: Ability to add multiple guarantors affected ability to make guarantor fields mandatory
by bugzilla-daemon＠bugs.koha-community.org 31 Jan '23

31 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25854 Bug ID: 25854 Summary: Ability to add multiple guarantors affected ability to make guarantor fields mandatory Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com bug 14570 made the non-member guarantor fields visible on all patrons prior to this adding fields like 'contactname' to the BorrowerMandatoryFields system preference had the effect of making guarantors mandatory for child accounts only. Now adding those fields makes them required for all patron types, but does not make adding an actual guarantor mandatory. We need to restore a method of making guarantors mandatory for some patron types. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 27272] New: Move C4::Items::GetItemsInfo to Koha namespace
by bugzilla-daemon＠bugs.koha-community.org 31 Jan '23

31 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27272 Bug ID: 27272 Summary: Move C4::Items::GetItemsInfo to Koha namespace Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 266

[Bug 15797] New: C4::Koha::GetKohaImageurlFromAuthorisedValues is no longer in use
by bugzilla-daemon＠bugs.koha-community.org 30 Jan '23

30 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15797 Bug ID: 15797 Summary: C4::Koha::GetKohaImageurlFromAuthorisedValues is no longer in use Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement 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 Blocks: 15779 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15779 [Bug 15779] Remove unnecessary parts of C4::Koha -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 17252] New: Koha::AuthorisedValues - Remove GetAuthorisedValueByCode
by bugzilla-daemon＠bugs.koha-community.org 30 Jan '23

30 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17252 Bug ID: 17252 Summary: Koha::AuthorisedValues - Remove GetAuthorisedValueByCode Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement 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 21

[Bug 30520] New: Command line stage and import broken since 21.11.
by bugzilla-daemon＠bugs.koha-community.org 30 Jan '23

30 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30520 Bug ID: 30520 Summary: Command line stage and import broken since 21.11. Change sponsored?: --- Product: Koha Version: 21.11 Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: andreas.jonsson(a)kreablo.se QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz As part of the work done for bug 14957, a change was made where it is assumed the import is made by a logged in user, and crashes if there isn't one. Specifically, this change causes the problem: https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=126754&action=d… This affects the command line tools stage_file.pl and commit_file.pl, when using the --match flag to match and replace existing records. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 39

[Bug 26703] New: We should reconsider best practice for our title elements
by bugzilla-daemon＠bugs.koha-community.org 27 Jan '23

27 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26703 Bug ID: 26703 Summary: We should reconsider best practice for our title elements 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Many of our <title> elements contain the whole breadcrumb path to the current page. Unfortunately this often results in a very long title which doesn't fit well in browser tab titles and sometimes is even concatenated on hover. In a quick bit of research I did, I found that the recommendation seems to be to limit the title element to 70 characters max and to start with the most relevant information and end with the generic branding. I'm thinking, reverse the breadcrumb, only use a couple of slots from it, then add the generic library branding after. For example: Edit < $reportname : Koha $searchstring : Koha -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 160

[Bug 27001] New: Z39.50 column configuration is missing columns
by bugzilla-daemon＠bugs.koha-community.org 27 Jan '23

27 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27001 Bug ID: 27001 Summary: Z39.50 column configuration is missing columns Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: barbara.johnson(a)bedfordtx.gov QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl The columns displayed for Z39.50 results differs when creating a new record vs. searching for a record when already in the Advanced Cataloging Editor. When done this way there are three additional columns - subtitle, ISSN and Published. These should be added to the Z39.50 column configuration so that libraries can choose to show/hide and toggle them. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3