November 2019 - Koha-bugs - lists.koha-community.org

[Bug 22522] New: ILL API breaks with updated Mojolicious version
by bugzilla-daemon＠bugs.koha-community.org 30 Jun '20

30 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22522 Bug ID: 22522 Summary: ILL API breaks with updated Mojolicious version Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: jose-mario.monteiro-santos(a)inlibro.com CC: andrew.isherwood(a)ptfs-europe.com, philippe.blouin(a)inlibro.com Target Milestone: --- When we tried to setup the ILL module using FreeForm as its backend, the ILL requests page in our staff client would not load any of the requests. We would get an error message saying that there was a problem with missing content in the Datable. Upon investigation, we discovered that the calls made to the API were returning "Malformed query" errors. When validating the query, Auth.pm checks for authorized parameters in openapi.op_spec, which wasn't defined anywhere in our case. After a quick discussion with Andrew Isherwood on IRC, we downgraded Mojolicious (from 8.02 to 7.21), JSON::Validator (from 3.02 to 0.97) and Mojolicious::Plugin::OpenAPI (from 2.08 to 1.15) and everything worked. Isn't this problematic ? If these modules aren't installed or don't meet the minimum version required by Koha, cpan will install the most recent versions and the API won't work. While this was experienced with the ILL module, I assume that other API calls can and will break in the same way. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 60

[Bug 20194] New: Display items.ccode as well as both biblioitems.itemtype and items.itype in circulation screens
by bugzilla-daemon＠bugs.koha-community.org 29 Jun '20

29 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20194 Bug ID: 20194 Summary: Display items.ccode as well as both biblioitems.itemtype and items.itype in circulation screens Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: gaetan.boisson(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com At the moment in circulation screens only one "item type" is displayed, biblioitems.itemtype or items.itype, depending on the item-level_itypes system preference. It is however possible for libraries to use both, biblioitems.itemtype to qualify the record, and items.itype to qualify the item itself. In such a scenario only one of the two will be displayed on the circulation screen. It is also possible for libraries to use items.ccode to further refine the description of their items, but this information is not displayed on circulation screens. This enhancement will make all this information more visible in circulation. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 34

[Bug 16528] New: Add ability to parallel process fines to fines.pl
by bugzilla-daemon＠bugs.koha-community.org 29 Jun '20

29 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16528 Bug ID: 16528 Summary: Add ability to parallel process fines to fines.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org On very large sites with thousands of overdue items, fines.pl may take an incredibly long time to complete. It may be possible to speed up fines.pl by allowing it to fork children that run in parallel. -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 24109] New: Elasticsearch - Advanced search limit by shelving location uses AND instead of OR
by bugzilla-daemon＠bugs.koha-community.org 26 Jun '20

26 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24109 Bug ID: 24109 Summary: Elasticsearch - Advanced search limit by shelving location uses AND instead of OR Change sponsored?: --- Product: Koha Version: 19.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: mkstephens(a)lancasterseminary.edu When performing an advanced catalog search, the limits for item type and collection are formed into a query string with OR, while the limits for shelving location are formed into the query string with AND. This prevents searching multiple locations at once and is also confusing since the behavior is different from the other limit tabs and is accompanied by the same instruction, "Limit to any of the following." Steps to replicate: 1. In the advanced catalog search, select two limits on the item types tab. Perform search. Note the search query was constructed with OR. 2. Return to the advanced catalog search and clear fields. Select two limits on the shelving location tab. Perform search. Note the search query was constructed with AND. 3. Return to the advanced catalog search and clear fields. Select two limits on the collections tab. Perform search. Note the search query was constructed with OR. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 11

[Bug 19588] New: There is no ILL requests history
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '20

25 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19588 Bug ID: 19588 Summary: There is no ILL requests history Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: In Discussion 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 Blocks: 7317 When a request is deleted, the row is removed from illrequests. Is that expected? Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7317 [Bug 7317] Add an Interlibrary Loan Module to Circulation and OPAC -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 23309] New: Can't add new subfields to bibliographic frameworks
by bugzilla-daemon＠bugs.koha-community.org 24 Jun '20

24 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23309 Bug ID: 23309 Summary: Can't add new subfields to bibliographic frameworks Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com When I try to add a new a new subfield to a tag in the bibliographic MARC frameworks, it doesn't save. Tested on a sandbox, found this in the logs: DBD::mysql::st execute failed: Incorrect integer value: '' for column 'hidden' at row 1 [for Statement " insert into marc_subfield_structure (tagfield,tagsubfield,liblibrarian,libopac,repeatable,mandatory,kohafield,tab,seealso,authorised_value,authtypecode,value_builder,hidden,isurl,frameworkcode, link,defaultvalue,maxlength) values (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?) " with ParamValues: 0="922", 1="n", 2="k", 3="k", 4=0, 5=0, 6="", 7="-1", 8=undef, 9="", 10="", 11="", 12="", 13=0, 14="", 15="", 16="", 17="9999"] at /kohadevbox/koha/admin/marc_subfields_structure.pl line 316. DBD::mysql::st execute failed: Incorrect integer value: '' for column 'hidden' at row 1 [for Statement " insert into marc_subfield_structure (tagfield,tagsubfield,liblibrarian,libopac,repeatable,mandatory,kohafield,tab,seealso,authorised_value,authtypecode,value_builder,hidden,isurl,frameworkcode, link,defaultvalue,maxlength) values (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?) " with ParamValues: 0="941", 1="k", 2="k", 3="k", 4=0, 5=0, 6="", 7="-1", 8=undef, 9="", 10="", 11="", 12="", 13=0, 14="", 15="", 16="", 17="9999"] at /kohadevbox/koha/admin/marc_subfields_structure.pl line 316. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 39

[Bug 17232] New: Subfield default values are not ported when creating a new framework from an old one
by bugzilla-daemon＠bugs.koha-community.org 24 Jun '20

24 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17232 Bug ID: 17232 Summary: Subfield default values are not ported when creating a new framework from an old one Change sponsored?: --- Product: Koha Version: 16.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: joachim.ganseman(a)ehb.be QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When creating a new bibliographic MARC21 framework from an old one, any default values set for subfields in the old framework are not ported to the newly created framework. They have to be reset. To reproduce: - Set a default value in an existing bibliographic MARC21 framework, e.g. 040$a to your institution's MARC code. - Create a new framework based on that one - Create a new record using that new framework: the default value is not set. - Upon checking the database table marc_subfield_structure (e.g. WHERE tagfield = 40 and tagsubfield = 'a'), notice there is no defaultvalue set in that subfield in the new framework. This issue occurs in a package install of version 16.05 on Debian. -- You are receiving this mail because: You are watching all bug changes.

1 21

[Bug 22571] New: Bug in Perl module "Koha::SimpleMARC::field_equals"
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '20

23 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22571 Bug ID: 22571 Summary: Bug in Perl module "Koha::SimpleMARC::field_equals" Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: mik(a)adminkuhn.ch QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- After successfully creating a MARC modification template in Koha menu "Tools > Batch record modification" with the following action: Add new field 041$a with value ger if 008 matches RegEx m/^...................................ger..$/ the action is run over a given record and Koha says that the bibliographic record has successfully been modified - but in fact nothing has changed, thus no new MARC 041$a is created. According to Jonathan Druart (in mailinglist "Koha", 21.03.2019 17:12) this is a bug in Perl module "Koha::SimpleMARC::field_equals". -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21

[Bug 23825] New: Object.t is failing - Exception not caught
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '20

23 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23825 Bug ID: 23825 Summary: Object.t is failing - Exception not caught Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Something weird here: kohadev-koha@kohadevbox:/home/vagrant/kohaclone$ prove t/db_dependent/Koha/Object.t t/db_dependent/Koha/Object.t .. 3/11 # Failed test 'Exception thrown correctly' # at t/db_dependent/Koha/Object.t line 359. # expecting: Koha::Exceptions::Object::BadValue # found: DBIx::Class::Exception (DBIx::Class::Storage::DBI::_dbh_execute(): Incorrect datetime value: 'wrong_value' for column `koha_kohadev`.`borrowers`.`lastseen` at row 1 at /home/vagrant/kohaclone/Koha/Object.pm line 156 # ) # Looks like you failed 1 test of 1. # Failed test 'Bad value tests' # at t/db_dependent/Koha/Object.t line 363. # Looks like you failed 1 test of 16. Not on Jenkins It's the following exception's message that is not caught correctly by the regex: DBIx::Class::Storage::DBI::_dbh_execute(): Incorrect datetime value: 'wrong_value' for column `koha_kohadev`.`borrowers`.`lastseen` at row 1 at /home/vagrant/kohaclone/Koha/Object.pm line 156 Note the backticks. -- You are receiving this mail because: You are watching all bug changes.

1 47

[Bug 22539] New: Fines charged on back-dated checkin when item has been renewed
by bugzilla-daemon＠bugs.koha-community.org 22 Jun '20

22 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22539 Bug ID: 22539 Summary: Fines charged on back-dated checkin when item has been renewed Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- In a certain niche situation, a patron can end up with an unexpected fine due to renewing a book just prior to returning it. Here's the situation: - Patron has a book due on a Saturday and doesn't return it - On Sunday, the library is closed - Early Sunday morning, the fines cron generates an accruing fine on the item - Patron puts the item in the bookdrop on Sunday - Patron renews the item via the OPAC on Sunday - At renewal, the fine changes from FU to F - Monday morning, the item is checked in via bookdrop mode, which back-dates the checkin to Saturday According to the old_issues table, the item was checked in before any fine was charged, but the fine remains on the patron's account. If the patron had not renewed the item, the fine would have remained FU and would have been forgiven on checkin. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 50