https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23260
Wainui Witika-Park <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] | |et.nz --- Comment #249 from Wainui Witika-Park <[email protected]> --- (In reply to Oliver Behnke from comment #248) > 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 We have a customer that has noticed this issue too -- 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/
