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

[Bug 30832] New: bulkmarcimport.pl don´t find .mrc file uploaded
by bugzilla-daemon＠bugs.koha-community.org 18 Jun '23

18 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30832 Bug ID: 30832 Summary: bulkmarcimport.pl don´t find .mrc file uploaded Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: paliotti(a)mdp.edu.ar QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 30818] New: REST API: Why does a wrong column name still cause a general 500 while validating exhaustively?
by bugzilla-daemon＠bugs.koha-community.org 18 Jun '23

18 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30818 Bug ID: 30818 Summary: REST API: Why does a wrong column name still cause a general 500 while validating exhaustively? 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: m.de.rooy(a)rijksmuseum.nl CC: tomascohen(a)gmail.com This might just be a dumb question: While testing 30790 and tweaking the test a bit, I found this: my $api_filter = encode_json({'isbn' => '123', 'xx1' => 'a2' }); $t->get_ok("//$userid:$password@/api/v1/biblios?q=$api_filter"); I am sending xx1 to Koha/REST/V1/Biblios, sub list. To my surprise, this doesnt trigger an error that says xx1 is not a valid biblio column. It appears that this query is just sent to DBIx. It crashes and the Exceptions module returns 500 Something went wrong. How is that possible? I stumble over all kinds of validation, extracting and merging parameters etc. etc. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 30804] New: Optionally show information on existing items in order form
by bugzilla-daemon＠bugs.koha-community.org 18 Jun '23

18 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30804 Bug ID: 30804 Summary: Optionally show information on existing items in order form Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Some libraries would like to see information about existing items when creating an order line for an existing record. This would be especially helpful for multi-branch libraries that would like to coordinate their acquisitions. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 30983] New: Uneeded use of C4::Auth in Koha::REST::V1::Checkouts
by bugzilla-daemon＠bugs.koha-community.org 18 Jun '23

18 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30983 Bug ID: 30983 Summary: Uneeded use of C4::Auth in Koha::REST::V1::Checkouts Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 17003 Koha::REST::V1::Checkouts use C4::Auth but don't need it Since commit 0404ecec4b619ebe14ac262332870004bb88878c Bug 17003: Adapt to OpenAPI Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17003 [Bug 17003] Add API route to get checkout's renewability -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 31008] New: Long-terms support version of Koha
by bugzilla-daemon＠bugs.koha-community.org 18 Jun '23

18 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31008 Bug ID: 31008 Summary: Long-terms support version of Koha Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Installation and upgrade (web-based installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Adding a "long-term support" release of Koha supported by the Koha Community. This would be in addition to current 18-months to two-year release support (stable, old stable, and old old stable). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 10

[Bug 31010] New: BatchRevert does not deal with indexation correctly
by bugzilla-daemon＠bugs.koha-community.org 18 Jun '23

18 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31010 Bug ID: 31010 Summary: BatchRevert does not deal with indexation correctly 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org This bug came up during QA of bug 30822, we're not yet properly handling the batchRevert indexing jobs. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 31015] New: Remove option to clear pickup location selects on multi-holds page
by bugzilla-daemon＠bugs.koha-community.org 18 Jun '23

18 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31015 Bug ID: 31015 Summary: Remove option to clear pickup location selects on multi-holds page Change sponsored?: --- Product: Koha Version: 21.11 Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: jrobb(a)sekls.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com When placing multiple holds at once, the various selects for pickup location have a little X at the far right next to the dropdown arrow. Clicking the X clears the field and allows for holds to be created with null pickup locations. We discovered the hard way that things like the holds queue completely break when there are null pickup locations lurking about. It also seems to prevent the holds tab on the patron account from loading. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 31022] New: 400/404 actually returns 500
by bugzilla-daemon＠bugs.koha-community.org 18 Jun '23

18 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31022 Bug ID: 31022 Summary: 400/404 actually returns 500 Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart+koha(a)gmail.com CC: martin.renvoize(a)ptfs-europe.com, tomascohen(a)gmail.com Not sure if I am missing something, but I don't manage to get a 400 with the syntax we are using all around our REST API code. return $c->render( status => 400, openapi => { error => "this is an error" } ); I am getting a 500 with, in Koha logs: [{"message":"Missing property.","path":"\/body\/errors"}] So yes, it is working with: return $c->render( status => 400, openapi => { errors => [ {message => 'this is an error'}] } ); But it's not at all what we are doing in our REST API module. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 31070] New: [DOCS] Did you mean? section needs an update
by bugzilla-daemon＠bugs.koha-community.org 18 Jun '23

18 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31070 Bug ID: 31070 Summary: [DOCS] Did you mean? section needs an update Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org The Did you mean? section in the administration chapter needs an update (https://koha-community.org/manual/22.05/en/html/administration.html#did-you…) Updates required include: - Updated screenshots - Remove important note about it only working in the OPAC - Add information about the LibrisSpellCheck plugin Related changes to the searching preferences page: - Punctuation and spelling - Link to administration > did you mean section Other changes: - Check whether any update to the OPAC page is required -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 31089] New: viewlog.pl needs better reference point for compare
by bugzilla-daemon＠bugs.koha-community.org 18 Jun '23

18 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31089 Bug ID: 31089 Summary: viewlog.pl needs better reference point for compare Change sponsored?: --- Product: Koha Version: 21.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org Currently, viewlog.pl runs comparisons another log. This is okay if you have a previous entry in the log to compare it to (if your logs haven't been cleaned up or a good log exists before the change). It would be better, if the log had a copy of info before the change, and after. If that is the only log entry you select to compare, it will show you a before and after and highlight the changes. If you select a second log entry, then it would show you a comparison between the two entries. This would make the compare feature infinitely more useful. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1