https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23260
Oliver Behnke <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #248 from Oliver Behnke <[email protected]> --- Sorry if I'm late to the party but after deploying this I noticed that the claim "new cronjob anonymize_last_borrowers.pl, with its behavior governed by the new system preferences AnonymizeLastBorrower" doesn't really hold up. If 'AnonymizeLastBorrower' is explicitly set to "Don't anonymize" the cronjob will return with status 1 (an error) and send an email warning about needing to enable 'AnonymizeLastBorrower'. That effectively renders the setting useless as I have to comment out the cronjob itself to fully disable (and silence) the feature. What I'd like to see: the cronjob shouldn't error out on "Don't anonymize" such that the setting alone is enough to fully manage the feature. Librarians shouldn't have to mess with the cronjob list itself. Thanks -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list -- [email protected] To unsubscribe send an email to [email protected] website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
