January 2023 - Koha-bugs - lists.koha-community.org

[Bug 27629] New: Filter invoices by library in invoices.pl
by bugzilla-daemon＠bugs.koha-community.org 23 Jan '23

23 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27629 Bug ID: 27629 Summary: Filter invoices by library in invoices.pl Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P4 Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: dch(a)interleaf.ie QA Contact: testopia(a)bugs.koha-community.org Filter invoices by library doesn't work in invoices.pl Some invoices will be listed but not all the applicable invoices. An easy way to reproduce this problem is to list all the invoices within a date range, make a note of the invoices for one particular library, now filter your list by that library and you will notice that all the invoices you expect are listed. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 10662] Build OAI-PMH Harvesting Client
by bugzilla-daemon＠bugs.koha-community.org 23 Jan '23

23 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10662 --- Comment #319 from David Cook <dcook(a)prosentient.com.au> --- (In reply to Koha Team University Lyon 3 from comment #318) > We would like to use an existing OAI-PMH harvester and 2 of them seem to be > good candidates : > - Catmandu harverster > - HTTP::OAI::HARVESTER module > > Both are in perl. At the moment, we thought that the second could be a > better choice because it's more up to date and we don't necessarily need to > use Catmandu. Currently, we're still stuck using HTTP::OAI 3.27 from 2011 in Koha for OAI-PMH server functionality. Bug 17704 is looking at trying to get a later version of HTTP::OAI working with Koha, but it's been open for about 6 years now. (HTTP::OAI was also a dead project for a few years but it was resurrected in 2017 by one of the Catmandu authors. On that note, I think it is a good idea to avoid Catmandu.) One problem with HTTP::OAI that I encountered back in 2016 was that it needed to parse the entire XML response into a DOM Document tree rather than processing the XML response while it parsed it. This usually isn't a problem because most repositories use resumptionToken elements and limit responses to approximately 100 records. But LIBRIS in Sweden would stream the entire response back without resumptionToken elements, so 1 XML response could contain the entire catalogue's worth of records. That said, in theory the HTTP::OAI module uses event-driven SAX XML parsing, so it shouldn't be building a DOM Document tree from the response. Maybe the dev environment I was using in 2016 didn't have the correct SAX parser dependencies, so it was using a DOM-based parser in lieu of the SAX parser unintentionally. Plus, I suppose we could say that the Koha OAI-PMH harvester doesn't support OAI-PMH repositories that don't use resumptionToken elements for flow control. Or, since HTTP::OAI is no longer dead, that issue can always be pursued with the current maintainer. So overall... HTTP::OAI is probably the way to go. Just wanted to add a warning about my past experience with it. > What we would like is to use all the import tools already existing in Koha > (XSLT, Record matching rules, MARC modification templates, Stage marc for > import, Manage MARC overlay rules). > > We would like to add a OAI-PMH setting (like Z39-50 / SRU) in the staff > interface with URL, SET, XML Format, authentication login, biblio/authority > records, deleted records handling, email for logs, XSLT file, encoding, > items handling, profile import. Sounds like a plan. I suspect it will involve a lot of testing. It might be worthwhile to break some of that functionality out into separate tickets, so that the whole patch set doesn't need to be re-tested for minor fixes outside the core harvester functionality. > Every harvesting would be scheduled only via the cronjobs. That should make it easy to implement and test. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 27639] New: Add debit_type endpoints
by bugzilla-daemon＠bugs.koha-community.org 23 Jan '23

23 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27639 Bug ID: 27639 Summary: Add debit_type endpoints 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: martin.renvoize(a)ptfs-europe.com We could do with having access to the list of debit_types from the API -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 31337] New: Lack of notes field for all methods of paying fines
by bugzilla-daemon＠bugs.koha-community.org 23 Jan '23

23 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31337 Bug ID: 31337 Summary: Lack of notes field for all methods of paying fines Change sponsored?: --- Product: Koha Version: 21.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: daniel.jordan(a)nottinghamcollege.ac.uk QA Contact: testopia(a)bugs.koha-community.org Right now there are quite a few ways to deal with fines in a user's Accounting tab, but not all of them provide a means of adding a note alongside it. The 'Pay selected' and 'Write off selected' buttons do, but the 'pay' and 'write-off' buttons next to individual fine occurrences don't. Both take the user through to new screens where they can specify the amount being paid and the payment type, but only the former two options have a notes field as well. Could we look into having this functionality on all of these methods? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 27711] New: Add categories to Public Lists in the OPAC
by bugzilla-daemon＠bugs.koha-community.org 23 Jan '23

23 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27711 Bug ID: 27711 Summary: Add categories to Public Lists in the OPAC Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: e0464747(a)cmaisonneuve.qc.ca QA Contact: testopia(a)bugs.koha-community.org Created attachment 116897 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=116897&action=e… Exemple of the categories Hi, In the Saved Reports section (guided_reports.pl) of KOHA there is an interesting way to categorize every single report. It would be interesting if there could be something similar implemented in the Lists (opac-shelves.pl) section of the OPAC. I've added a screenshot of the desire addition. -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 27651] New: Warning of missing Bootstrap source map
by bugzilla-daemon＠bugs.koha-community.org 23 Jan '23

23 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27651 Bug ID: 27651 Summary: Warning of missing Bootstrap source map Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: andrew.isherwood(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Chrome Dev Tools is warning of a missing Bootstrap source map in the OPAC: DevTools failed to load SourceMap: Could not load content for https://xxxxx/opac-tmpl/bootstrap/lib/bootstrap/js/bootstrap.bundle.min.js.…: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE (The xxxxx replaced the actual OPAC domain) I wouldn't have thought we would want to be referencing source maps in production, but I don't know if Bootstrap does that by default or whether we should be using a production build that doesn't reference it. -- You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 27658] New: processes are overloaded and the page does not work
by bugzilla-daemon＠bugs.koha-community.org 23 Jan '23

23 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27658 Bug ID: 27658 Summary: processes are overloaded and the page does not work Change sponsored?: --- Product: Project Infrastructure Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Project website Assignee: wizzyrea(a)gmail.com Reporter: federicoantoniopaiz(a)gmail.com processes are overloaded and the page does not work plack-error.log Error while loading /etc/koha/plack.psgi: Can't load application from file "/usr/share/koha/api/v1/app.pl": Possibly a typo in schema? Could not find "/patron_id_pp" in "parameters/patron.json#/patron_id_pp" (parameters/patron.json#/patron_id_pp) at /usr/local/share/perl/5.26.1/JSON/Validator.pm line 419. JSON::Validator::_resolve_ref(JSON::Validator::OpenAPI::Mojolicious=HASH(0x55b4c85dd398), "parameters/patron.json#/patron_id_pp", Mojo::URL=HASH(0x55b4c8769df8), HASH(0x55b4c83c5e48)) called at /usr/local/share/perl/5.26.1/JSON/Validator/OpenAPI/Mojolicious.pm line 465 JSON::Validator::OpenAPI::Mojolicious::_resolve_ref(JSON::Validator::OpenAPI::Mojolicious=HASH(0x55b4c85dd398), "parameters/patron.json#/patron_id_pp", Mojo::URL=HASH(0x55b4c8769df8), HASH(0x55b4c83c5e48)) called at /usr/local/share/perl/5.26.1/JSON/Validator.pm line 305 JSON::Validator::_find_and_resolve_refs(JSON::Validator::OpenAPI::Mojolicious=HASH(0x55b4c85dd398), Mojo::URL=HASH(0x55b4c866cb90), HASH(0x55b4c85dd8d8)) called at /usr/local/share/perl/5.26.1/JSON/Validator.pm line 398 JSON::Validator::_resolve(JSON::Validator::OpenAPI::Mojolicious=HASH(0x55b4c85dd398), HASH(0x55b4c85dd8d8)) called at /usr/local/share/perl/5.26.1/JSON/Validator/OpenAPI/Mojolicious.pm line 39 JSON::Validator::OpenAPI::Mojolicious::load_and_validate_schema(JSON::Validator::OpenAPI::Mojolicious=HASH(0x55b4c85dd398), Mojo::Home=SCALAR(0x55b4c75530f8), HASH(0x55b4c85dd5f0)) called at /usr/share/koha/lib/Koha/REST/V1.pm line 61 Koha::REST::V1::startup(Koha::REST::V1=HASH(0x55b4c7552f78)) called at /usr/local/share/perl/5.26.1/Mojolicious.pm line 170 Mojolicious::new("Koha::REST::V1") called at /usr/local/share/perl/5.26.1/Mojo/Server.pm line 17 Mojo::Server::build_app(Mojo::Server=HASH(0x55b4c74ff290), "Koha::REST::V1") called at /usr/local/share/perl/5.26.1/Mojolicious/Commands.pm line 79 Mojolicious::Commands::start_app("Mojolicious::Commands", "Koha::REST::V1") called at /usr/share/koha/api/v1/app.pl line 21 require /usr/share/koha/api/v1/app.pl called at (eval 366) line 1 eval 'package Mojo::Server::Sandbox::e02d8dd2b7bd893f6bb5f5d2b2b726fa; require $path' called at /usr/local/share/perl/5.26.1/Mojo/Server.pm line 54 Mojo::Server::load_app(Mojo::Server::PSGI=HASH(0x55b4c74f8728), "/usr/share/koha/api/v1/app.pl") called at /etc/koha/plack.psgi line 65 Plack::Sandbox::_2fetc_2fkoha_2fplack_2epsgi::__ANON__() called at /usr/share/perl5/Plack/Builder.pm line 118 Plack::Builder::builder(CODE(0x55b4c16a2b58)) called at /etc/koha/plack.psgi line 67 require /etc/koha/plack.psgi called at (eval 15) line 3 eval 'package Plack::Sandbox::_2fetc_2fkoha_2fplack_2epsgi; { my $app = do $_file; if ( !$app && ( my $error = $@ || $! )) { die $error; } $app; } ' called at /usr/share/perl5/Plack/Util.pm line 120 Plack::Util::_load_sandbox("/etc/koha/plack.psgi") called at /usr/share/perl5/Plack/Util.pm line 136 Plack::Util::load_psgi("/etc/koha/plack.psgi") called at /usr/share/perl5/Plack/Runner.pm line 179 Plack::Runner::__ANON__() called at /usr/share/perl5/Plack/Runner.pm line 24 Plack::Runner::__ANON__() called at /usr/share/perl5/Plack/Runner.pm line 24 Plack::Runner::__ANON__() called at /usr/share/perl5/Starman/Server.pm line 174 Starman::Server::child_init_hook(Starman::Server=HASH(0x55b4c0f98a98)) called at /usr/share/perl5/Net/Server/PreFork.pm line 218 Net::Server::PreFork::run_child(Starman::Server=HASH(0x55b4c0f98a98)) called at /usr/share/perl5/Net/Server/PreFork.pm line 183 Net::Server::PreFork::run_n_children(Starman::Server=HASH(0x55b4c0f98a98), 1) called at /usr/share/perl5/Net/Server/PreFork.pm line 373 Net::Server::PreFork::coordinate_children(Starman::Server=HASH(0x55b4c0f98a98)) called at /usr/share/perl5/Net/Server/PreFork.pm line 292 Net::Server::PreFork::run_parent(Starman::Server=HASH(0x55b4c0f98a98)) called at /usr/share/perl5/Starman/Server.pm line 164 Starman::Server::run_parent(Starman::Server=HASH(0x55b4c0f98a98)) called at /usr/share/perl5/Net/Server/PreFork.pm line 109 Net::Server::PreFork::loop(Starman::Server=HASH(0x55b4c0f98a98)) called at /usr/share/perl5/Net/Server.pm line 58 Net::Server::run(Starman::Server=HASH(0x55b4c0f98a98), "port", ARRAY(0x55b4c162b110), "host", "*", "proto", "tcp", "serialize", ...) called at /usr/share/perl5/Starman/Server.pm line 106 Starman::Server::run(Starman::Server=HASH(0x55b4c0f98a98), CODE(0x55b4c0f98960), HASH(0x55b4c0f98720)) called at /usr/share/perl5/Plack/Handler/Starman.pm line 25 Plack::Handler::Starman::run(Plack::Handler::Starman=HASH(0x55b4c0f98978), CODE(0x55b4c0f98960)) called at /usr/share/perl5/Plack/Loader/Delayed.pm line 20 Plack::Loader::Delayed::run(Plack::Loader::Delayed=HASH(0x55b4c0e4c378), Plack::Handler::Starman=HASH(0x55b4c0f98978)) called at /usr/share/perl5/Plack/Runner.pm line 277 Plack::Runner::run(Plack::Runner=HASH(0x55b4c0dee790)) called at /usr/bin/starman line 38 Compilation failed in require at (eval 366) line 1. Child process 5586 exited with status 255 -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 27662] New: Error 500 when mailing list
by bugzilla-daemon＠bugs.koha-community.org 23 Jan '23

23 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27662 Bug ID: 27662 Summary: Error 500 when mailing list Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Lists Assignee: koha-bugs(a)lists.koha-community.org Reporter: jcautomatizacion(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Created attachment 116577 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=116577&action=e… Capture error Good day, When trying to send a list by mail I get this message: "Sorry, the page you requested is not available Error 500 "; can you help me know why this is happening? I am using Koha 20.05 Have a terrific day -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 27

[Bug 27664] New: pickupNotInHoldGroup is too generic
by bugzilla-daemon＠bugs.koha-community.org 23 Jan '23

23 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27664 Bug ID: 27664 Summary: pickupNotInHoldGroup is too generic Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com There are actually two codepaths that yield an output of 'pickupNotInHoldGroup' in C4::Reserves::CanItemBeReserved: - The passed pickup location doesn't match the patron's hold group - The passed pickup location doesn't match the item's hold group We could return different error codes and provide better feedback to the end user. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 27666] New: Fix typo in error message on addorderiso2709.pl
by bugzilla-daemon＠bugs.koha-community.org 23 Jan '23

23 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27666 Bug ID: 27666 Summary: Fix typo in error message on addorderiso2709.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org 1 - have a marc record you know will match something in your system using ISBN 2 - In acquisitons, create a basket, click Add to basket, select From a new file 3 - stage your marc record, select Do not look for matching records 4 - confirm that your staging results include "Did not check for matches with existing records in catalog" 5 - click Add staged files to basket 6 - this takes you to addorderiso2709.pl 7 - check the box next to your title. Confirm you don't see any message about matches 8 - confirm Matching dropdown defaults to Title and Author. Do not change it 9 - give your order a price and fund, click Save, get message "No record have been imported because they all match an existing record in your catalog." That message should read "No record(s) ..." or otherwise account for the possibility of a batch of 1. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2