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

[Bug 15683] New: Inconsistent population of lastreneweddate between AddRenewal and AddIssue
by bugzilla-daemon＠bugs.koha-community.org 12 May '21

12 May '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15683 Bug ID: 15683 Summary: Inconsistent population of lastreneweddate between AddRenewal and AddIssue Change sponsored?: --- Product: Koha Version: 3.20 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When lastreneweddate is populated via C4::Circulation::AddRenewal, it is added as a date, whereas C4::Circulation::AddIssue stores it as DateTime, i.e. hours, minutes and seconds are populated. Because of hourly loans, I think that it only makes sense to store lastreneweddate as a full datetime. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 24154] New: No indication that Default checkout, hold and return policy are set if values are blank
by bugzilla-daemon＠bugs.koha-community.org 12 May '21

12 May '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24154 Bug ID: 24154 Summary: No indication that Default checkout, hold and return policy are set if values are blank Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major 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 - Visit Admin->Circulation rules 2 - Go to a specific branch 3 - Clear all the boxes in Default checkout, hold and return policy and save 4 - No visible indication that anything is set 5 - Check the DB, (SELECT * FROM circulation_rules WHERE branchcode='BRANCH') 6 - Note there are rules 7 - Unset the rules, no visible change 8 - Check the D, rules are cleared -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 28

[Bug 26518] New: Adding a record can succeed even if adding the biblioitem fails
by bugzilla-daemon＠bugs.koha-community.org 12 May '21

12 May '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26518 Bug ID: 26518 Summary: Adding a record can succeed even if adding the biblioitem fails Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl We can end up creating biblios in the catalog that are malformed To test: 1 - Add new record with field 010: ThisisgoingtobetoomanycharactersfortheLCCNfield 2 - Check the logs, note the error about failure to create biblioitem: DBD::mysql::st execute failed: Data too long for column 'lccn' at row 1 [for Statement "INSERT INTO biblioitems SET biblionumber = ?, volume = ?, number = ?, itemtype = ?, isbn = ?, issn = ?, publicationyear = ?, publishercode = ?, volumedate = ?, volumedesc = ?, collectiontitle = ?, collectionissn = ?, collectionvolume= ?, editionstatement= ?, editionresponsibility = ?, illus = ?, pages = ?, notes = ?, size = ?, place = ?, lccn = ?, url = ?, cn_source = ?, cn_class = ?, cn_item = ?, cn_suffix = ?, cn_sort = ?, totalissues = ?, ean = ?, agerestriction = ? " with ParamValues: 0='1681', 1=undef, 2=undef, 3=undef, 4=undef, 5=undef, 6=undef, 7=undef, 8=undef, 9=undef, 10=undef, 11=undef, 12=undef, 13=undef, 14=undef, 15=undef, 16=undef, 17=undef, 18=undef, 19=undef, 20="This is the ongest field i can think of", 21=undef, 22=undef, 23=undef, 24=undef, 25=undef, 26='', 27=undef, 28=undef, 29=undef] at /kohadevbox/koha/C4/Biblio.pm line 2926. ERROR in _koha_add_biblioitem INSERT INTO biblioitems SET 3 - Record saves successfully otherwise 4 - Attempt to add an item: Can't call method "biblioitemnumber" on an undefined value at /kohadevbox/koha/Koha/Item.pm line 83. at /kohadevbox/koha/Koha/Item.pm line 82 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 45

[Bug 17590] New: Exporting reports as CSV with 'delimiter' SysPref set to 'tabulation' creates files with 't' as separator
by bugzilla-daemon＠bugs.koha-community.org 12 May '21

12 May '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17590 Bug ID: 17590 Summary: Exporting reports as CSV with 'delimiter' SysPref set to 'tabulation' creates files with 't' as separator Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: gmcharlt(a)gmail.com Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org We need to translate 'tabulation' to "\t" before creating our file with Text::CSV -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 20904] New: Warns from Circulation/Chargelostitem.t
by bugzilla-daemon＠bugs.koha-community.org 12 May '21

12 May '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20904 Bug ID: 20904 Summary: Warns from Circulation/Chargelostitem.t Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org Test passes, but warns need attention DBIx::Class::Storage::DBI::select_single(): Query returned more than one row. SQL that returns multiple rows is DEPRECATED for ->find and ->single at /usr/share/koha/devclone/Koha/Objects.pm line 191 DBIx::Class::Storage::DBI::select_single(): Query returned more than one row. SQL that returns multiple rows is DEPRECATED for ->find and ->single at /usr/share/koha/devclone/Koha/Objects.pm line 191 t/db_dependent/Circulation/Chargelostitem.t ............. ok -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 27025] New: jQuery testing with specific user
by bugzilla-daemon＠bugs.koha-community.org 11 May '21

11 May '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27025 Bug ID: 27025 Summary: jQuery testing with specific user Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com I have been able to apply jQuery that only applies to a specific user that is logged in. I would propose that Koha would use similar techniques and create a jQuery test field that only applies to Koha if a specific user is logged in. This would be completely separate from the usual jQuery that is applied, but applied along with the usual jQuery, for testing purposes. It would have no affect on other users in a production environment, but allow for admin to test new jQuery before applying to the regular jQuery. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 16486] New: Display the TIME a fine was collected/written off
by bugzilla-daemon＠bugs.koha-community.org 11 May '21

11 May '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16486 Bug ID: 16486 Summary: Display the TIME a fine was collected/written off Change sponsored?: --- Product: Koha Version: 3.20 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: theod(a)lib.auth.gr QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com In many cases it would be very useful to be able to know the time a fine was collected/written off (in addition to the date). So ideally, the TIME could be shown next to the date in the Fines->Account tab. (This would make sense in almost all cases except maybe in Accruing fines). Alternatively, a text could be added to the description column. For example, "Payment, thanks" could become "Payment on 15/09/2015 14:30, thanks", "Writeoff" could become "Written off on 15/09/2015 14:30", etc -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 93

[Bug 27246] New: Remove apache only code from C4::Context BEGIN
by bugzilla-daemon＠bugs.koha-community.org 11 May '21

11 May '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27246 Bug ID: 27246 Summary: Remove apache only code from C4::Context BEGIN Change sponsored?: --- Product: Koha Version: unspecified 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 17

[Bug 26645] New: t/Koha/Script.t is failing randomly
by bugzilla-daemon＠bugs.koha-community.org 11 May '21

11 May '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26645 Bug ID: 26645 Summary: t/Koha/Script.t is failing randomly Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal 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 Blocks: 25551 First time we see this one I think Koha_Master_D11 #103 14:41:47 koha_1 | # Failed test 'Exception found' 14:41:47 koha_1 | # at t/Koha/Script.t line 67. 14:41:47 koha_1 | # '' 14:41:47 koha_1 | # doesn't match '(?^u:Unable to acquire the lock.*)' 14:41:50 koha_1 | # Looks like you failed 1 test of 3. 14:41:50 koha_1 | 14:41:50 koha_1 | # Failed test 'lock_exec() tests' 14:41:50 koha_1 | # at t/Koha/Script.t line 85. 14:41:50 koha_1 | # Looks like you failed 1 test of 4. 14:41:50 koha_1 | [12:41:50] t/Koha/Script.t Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25551 [Bug 25551] [OMNIBUS] Some tests are failing randomly -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 25557] New: Column config table in Acquisitions Order Does not Match the Acq table in Baskets
by bugzilla-daemon＠bugs.koha-community.org 10 May '21

10 May '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25557 Bug ID: 25557 Summary: Column config table in Acquisitions Order Does not Match the Acq table in Baskets Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Tools Assignee: lucas(a)bywatersolutions.com Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The actual way that the Acq table appears in the basket view (basket.pl), 1.Basket # 2. Order information 3. RRP Tax Exc 4. Actual Cost Exc 5. Budgeted Cost Tax Exc 6. RRP Tax Included 7. Actual Cost Tax Inc 8. Budgeted Cost Tax Inc 9. Replacement Price 10. Quantity But in the column config table 1.Basket # 2. Order Info 3. RRP tax Exc 4. Ecost Exc (Actual Exc) 5. RRP tax Included 6. Ecost Tax Included (Actual Inc) 7. Replacement Prie 8. Quantity 9. Total Tax Excluded 10. Total Tax Included We will need to change the column configuration to match the table so it is easy to hide the correct columns. -- You are receiving this mail because: You are watching all bug changes.

1 24