https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43908 Bug ID: 43908 Summary: Cleanup database should not report on patron lock unsubscribed, anonymize and delete when system preferences are blank Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs@lists.koha-community.org Reporter: andrew@bywatersolutions.com QA Contact: testopia@bugs.koha-community.org CC: jake.deery@openfifth.co.uk, robin@catalyst.net.nz Depends on: 43549 Target Milestone: --- The system preferences UnsubscribeReflectionDelay, PatronAnonymizeDelay, and PatronRemovalDelay prompt the cleanup_database cron to lock, anonymize, and delete after they've refused consent following the PrivacyPolicyConsent syspref. When UnsubscribeReflectionDelay, PatronAnonymizeDelay, and/or PatronRemovalDelay are blank, their corresponding actions are not taken. But running cleanup_databse with the --verbose flag while these sysprefs are null returns the message: Start lock unsubscribed, anonymize and delete 0 patrons would have been locked 0 patrons would have been anonymized 0 patrons would have been deleted The cron should check if these sysprefs have values and only report on the actions it actually took. Note that a value of 0 in any of these sysprefs causes patrons to be locked/anonymized/deleted with no delay, so we should make sure that we find values of 0 when checking the sysprefs. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43549 [Bug 43549] Convert misc/cronjobs/cleanup_database.pl to the Getopt::Long::Descriptive convention (see bug 43546) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.