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

[Bug 8338] Fines not cleared with dropbox mode
by bugzilla-daemon＠bugs.koha-community.org 23 May '20

23 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8338 --- Comment #26 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- I was ready to pass QA, but tests fail (pass with master): kohadev-koha@kohadevbox:/home/vagrant/kohaclone$ prove t/db_dependent/Circulation.t t/db_dependent/Circulation.t .. 29/48 _FixOverduesOnReturn(233, Koha::Item=HASH(0x55c8b6955450)->itemnumber...) failed! at /home/vagrant/kohaclone/C4/Circulation.pm line 2056. t/db_dependent/Circulation.t .. 45/48 # No tests run! # Failed test 'No tests run for subtest "Test Backdating of Returns"' # at t/db_dependent/Circulation.t line 3930. Can't call method "amountoutstanding" on an undefined value at t/db_dependent/Circulation.t line 3928. # Looks like your test exited with 255 just after 46. t/db_dependent/Circulation.t .. Dubious, test returned 255 (wstat 65280, 0xff00) Failed 3/48 subtests Test Summary Report ------------------- t/db_dependent/Circulation.t (Wstat: 65280 Tests: 46 Failed: 1) Failed test: 46 Non-zero exit status: 255 Parse errors: Bad plan. You planned 48 tests but ran 46. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 21727] New: Add Koha::Account::update_debit
by bugzilla-daemon＠bugs.koha-community.org 23 May '20

23 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21727 Bug ID: 21727 Summary: Add Koha::Account::update_debit 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 There should be a high-level method for update existing debits, similar to Koha::Account::add_credit and Koha::Account::add_debit It will handle updating the line, and adding an offset. Envisaged use case is for debit amendments and fine increments. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 62

[Bug 8338] Fines not cleared with dropbox mode
by bugzilla-daemon＠bugs.koha-community.org 23 May '20

23 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8338 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=25596 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8338] Fines not cleared with dropbox mode
by bugzilla-daemon＠bugs.koha-community.org 23 May '20

23 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8338 --- Comment #25 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- I wonder if you have seen bug 13044 - we discussed how to merge the book drop with the specify return date feature. Test case 1 makes perfect sense to me: | 3 | NULL | 2 | OVERDUE_DECREASE | -0.100000 | 2020-05-23 13:09:43 Test case 2 is a bit confusing: What we see: 1 Manual debit (something I added for testing) 2 Overdue fine from first test 3 Decrease from returning it with book drop mode 4 Me paying off 4.00 to get over the fine limit (be able to checkout out again) 5 Creating another overdue (same item!) 6 Paying the overdue off 7 Now I see what Andrew means: Manual Credit and OVERDUE_DECREASE seem to be both the result of me using returning the item with book drop. I now have a credit of .10 on the account, which matches the amount 'overpaid'. I think it makes sense to me as it is linked to the accountlines entry 'Overpayment refund'. +----+-----------+----------+------------------+-----------+---------------------+ | id | credit_id | debit_id | type | amount | created_on | +----+-----------+----------+------------------+-----------+---------------------+ | 1 | NULL | 1 | Manual Debit | 4.000000 | 2020-05-22 11:20:08 | | 2 | NULL | 2 | OVERDUE | 2.300000 | 2020-05-23 13:06:48 | | 3 | NULL | 2 | OVERDUE_DECREASE | -0.100000 | 2020-05-23 13:09:43 | | 4 | 3 | 1 | Payment | -4.000000 | 2020-05-23 13:13:21 | | 5 | NULL | 4 | OVERDUE | 0.500000 | 2020-05-23 13:13:52 | | 6 | 5 | 4 | Payment | -0.500000 | 2020-05-23 13:14:02 | | 7 | 6 | NULL | Manual Credit | -0.100000 | 2020-05-23 13:14:24 | | 8 | NULL | 4 | OVERDUE_DECREASE | -0.100000 | 2020-05-23 13:14:24 | +----+-----------+----------+------------------+-----------+---------------------+ NOTE: Am I the only one getting confused by our mix of descriptions (with false capitalization) and codes in these tables? Also "Overpayment refund" is not translatable :( -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 25594] New: Jancok
by bugzilla-daemon＠bugs.koha-community.org 23 May '20

23 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25594 Bug ID: 25594 Summary: Jancok Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: bugs.koha-community.org Assignee: koha-bugs(a)lists.koha-community.org Reporter: lanang.gaming06(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 105306 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=105306&action=e… We noob -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 7029] Searching : fuzzy and stemming
by bugzilla-daemon＠bugs.koha-community.org 23 May '20

23 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7029 --- Comment #12 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- This is from: /etc/zebradb/etc/word-phrase-utf.chr Seeing if there is a difference between ICU and grs would also be interesting. -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 7029] Searching : fuzzy and stemming
by bugzilla-daemon＠bugs.koha-community.org 23 May '20

23 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7029 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|searching : fuzzy et |Searching : fuzzy and |steming |stemming --- Comment #11 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- I think it might actually be something else at play here: chine and chiene i = ie + auto-truncate pain and paien + auto-truncate Can you check if turning of QueryAutoTruncate? Thinking about something like this: 18 equivalent iíìîịĩĭįǐȉȋ 19 equivalent ï(ie) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug. You are the QA Contact for the bug.

1 0

[Bug 7957] Routing lists: manage several routing list for each subscription, and export them as CSV
by bugzilla-daemon＠bugs.koha-community.org 23 May '20

23 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7957 --- Comment #92 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- (In reply to David Cook from comment #91) > (In reply to Katrin Fischer from comment #82) > > Multiple routing lists per subscription. > > What is the purpose/use of having multiple routing lists per subscription? I think there are different use case. Some libraries don't want to use x subscriptions, while they still receive x issues for one. So having differnt routing lists could go on multiple issues of the same subscription. In other cases libraries might want to keep the lists shorter / more anonymous, thus using different ones. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 9872] Logs explode with messages when adding a new order in acquisitions
by bugzilla-daemon＠bugs.koha-community.org 23 May '20

23 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9872 --- Comment #2 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- Hi Aleisha, I just tried. I used the ACQ framework that is now standard, so that step in the test plan is on longer necessary: Use of uninitialized value $value in string eq at /home/vagrant/kohaclone/acqui/neworderempty.pl line 229. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 236. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 237. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 238. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 245. Use of uninitialized value $value in string eq at /home/vagrant/kohaclone/acqui/neworderempty.pl line 229. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 236. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 237. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 238. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 245. Use of uninitialized value $value in string eq at /home/vagrant/kohaclone/acqui/neworderempty.pl line 229. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 236. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 237. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 238. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 245. Use of uninitialized value $value in string eq at /home/vagrant/kohaclone/acqui/neworderempty.pl line 229. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 236. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 237. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 238. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 245. Use of uninitialized value $value in string eq at /home/vagrant/kohaclone/acqui/neworderempty.pl line 229. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 236. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 237. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 238. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 245. Use of uninitialized value $value in string eq at /home/vagrant/kohaclone/acqui/neworderempty.pl line 229. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 236. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 237. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 238. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 245. Use of uninitialized value $value in string eq at /home/vagrant/kohaclone/acqui/neworderempty.pl line 229. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 236. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 237. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 238. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 245. Use of uninitialized value $value in string eq at /home/vagrant/kohaclone/acqui/neworderempty.pl line 229. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 236. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 237. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 238. Use of uninitialized value $value in substitution (s///) at /home/vagrant/kohaclone/acqui/neworderempty.pl line 245. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14648] Batch remove reserve items
by bugzilla-daemon＠bugs.koha-community.org 23 May '20

23 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14648 --- Comment #6 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- Sounds perfect, thank you! -- You are receiving this mail because: You are watching all bug changes.

1 0