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

[Bug 14825] Accounts Rewrite Omnibus
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '19

27 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14825 Martin Renvoize <martin.renvoize(a)ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |22421 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22421 [Bug 22421] accountlines.issue_id is missing a foreign key constraint -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14593] Send notifications for pending moderation staff actions
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '19

27 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14593 Oliver Behnke <oliver.behnke(a)aei.mpg.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Send notifications for |Send notifications for |pending staff actions |pending moderation staff |(moderation, suggestions) |actions -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 14593] Send notifications for pending staff actions (moderation, suggestions)
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '19

27 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14593 --- Comment #2 from Oliver Behnke <oliver.behnke(a)aei.mpg.de> --- Ok, so now that purchase suggestions are covered (bug 5770) let's use this bug report for the lack of moderation notifications. Since tags and comments are both moderation tasks I reckon we should keep that feature request in one ticket (this one). I'll update the title accordingly. Cheers -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 7088] Cannot renew items on hold even with override
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '19

27 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7088 Martin Renvoize <martin.renvoize(a)ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Failed QA |Signed Off CC| |martin.renvoize@ptfs-europe | |.com -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8775] Add collection code to lost report
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '19

27 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8775 Séverine Queune <severine.queune(a)bulac.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |severine.queune(a)bulac.fr --- Comment #3 from Séverine Queune <severine.queune(a)bulac.fr> --- Hi Owen, On /cgi-bin/koha/admin/columns_settings.pl page, 'collection code' is not present in 'id=lostitems-table', is it normal ? Except that point , behaviour is correct on items lost report, and the column can be hibben using the "Comulns" button on the /cgi-bin/koha/reports/itemslost.pl page. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 21247] New: Cannot add more than one emoji across the entire database as a tag
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '19

27 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21247 Bug ID: 21247 Summary: Cannot add more than one emoji across the entire database as a tag Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: liz(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Well I suppose that's not really fair - you can add them but you can only see the first one in the approval list, and on the detail/results pages. To replicate: Add a tag, such as 😍 to a biblio in the OPAC try to add another emoji, such as 🎶 In my 18.05, this won't work and the second tag is never inserted into tags_approval, though it is inserted into tags_all. It seems to be mysteriously approved as under the first emoji added, as well. I checked the DB encoding, it seemed correct. The database I was testing with was an upgraded one, 3.20 -> 18.05.02 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 10659] Upgrade jQuery star ratings plugin
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '19

26 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10659 Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jonathan.druart(a)bugs.koha-c | |ommunity.org --- Comment #29 from Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> --- I am getting the following line in the Koha logs on hitting opac-search.pl, I guess it comes from here. File not found : lib/jquery/plugins/jquery.rating.js at /home/vagrant/kohaclone/Koha/Template/Plugin/Asset.pm line 83. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 1993] Task Scheduler Needs Re-write
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '19

26 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=1993 Kyle M Hall <kyle(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tomascohen(a)gmail.com -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14385] Extend OpacHiddenItems to allow specifying exempt borrower categories
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '19

26 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14385 Tomás Cohen Arazi <tomascohen(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |22420 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22420 [Bug 22420] Tag cloud feature broken -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 21065] New: Data in accountoffsets and accountlines is deleted with the patron leaving gaps in financial reports
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '19

26 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21065 Bug ID: 21065 Summary: Data in accountoffsets and accountlines is deleted with the patron leaving gaps in financial reports 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com The tables accountoffsets and accountlines are both "cleaned up" when a patron is deleted by using FK constraints. This is a problem because 1) The patrons have a "right to be forgotten" with GDPR and you can't refuse to delete them if their fines are paid etc. 2) Especially for partial payments and in other cases the data in accountlines and accountoffsets is neded to create reliable reports for statistics, but also for financial reports. It's not possible to determine from other tables like statistics and action_logs what fines are linked to which payment which doesn't allow to create reports by fine/fee type and similar. Instead of deleting the info, we should really just anonymize it. -- CREATE TABLE `accountoffsets` ( `borrowernumber` int(11) NOT NULL DEFAULT '0', `accountno` smallint(6) NOT NULL DEFAULT '0', `offsetaccount` smallint(6) NOT NULL DEFAULT '0', `offsetamount` decimal(28,6) DEFAULT NULL, `timestamp` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, KEY `accountoffsets_ibfk_1` (`borrowernumber`), CONSTRAINT `accountoffsets_ibfk_1` FOREIGN KEY (`borrowernumber`) REFERENCES `borrowers` (`borrowernumber`) ON DELETE CASCADE ON UPDATE CASCADE ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; CREATE TABLE `accountlines` ( `accountlines_id` int(11) NOT NULL AUTO_INCREMENT, `issue_id` int(11) DEFAULT NULL, `borrowernumber` int(11) NOT NULL DEFAULT '0', `accountno` smallint(6) NOT NULL DEFAULT '0', `itemnumber` int(11) DEFAULT NULL, `date` date DEFAULT NULL, `amount` decimal(28,6) DEFAULT NULL, `description` mediumtext COLLATE utf8_unicode_ci, `dispute` mediumtext COLLATE utf8_unicode_ci, `accounttype` varchar(5) COLLATE utf8_unicode_ci DEFAULT NULL, `amountoutstanding` decimal(28,6) DEFAULT NULL, `lastincrement` decimal(28,6) DEFAULT NULL, `timestamp` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, `notify_id` int(11) NOT NULL DEFAULT '0', `notify_level` int(2) NOT NULL DEFAULT '0', `note` text COLLATE utf8_unicode_ci, `manager_id` int(11) DEFAULT NULL, PRIMARY KEY (`accountlines_id`), KEY `acctsborridx` (`borrowernumber`), KEY `timeidx` (`timestamp`), KEY `itemnumber` (`itemnumber`), CONSTRAINT `accountlines_ibfk_1` FOREIGN KEY (`borrowernumber`) REFERENCES `borrowers` (`borrowernumber`) ON DELETE CASCADE ON UPDATE CASCADE, CONSTRAINT `accountlines_ibfk_2` FOREIGN KEY (`itemnumber`) REFERENCES `items` (`itemnumber`) ON DELETE SET NULL ON UPDATE SET NULL ) ENGINE=InnoDB AUTO_INCREMENT=4666 DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 41