From c5c8a114dbdc05ab2cf0e5dddfdd146ec9cebaa8 Mon Sep 17 00:00:00 2001 From: Martin Renvoize Date: Fri, 13 Oct 2023 09:22:06 +0100 Subject: [PATCH] Bug 35001: (folllow-up) Tiny addition to cronjob help This patch adds a tiny addendum to the -active documentation returned by the membership_expiry cronjob to clarify what constitutes as an active patron and hint at the new TrackLastPatronActivityTriggers system preference. Signed-off-by: Martin Renvoize --- misc/cronjobs/membership_expiry.pl | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/misc/cronjobs/membership_expiry.pl b/misc/cronjobs/membership_expiry.pl index 697572e0704..ea6bd958a32 100755 --- a/misc/cronjobs/membership_expiry.pl +++ b/misc/cronjobs/membership_expiry.pl @@ -96,11 +96,17 @@ Optional parameter to use another renewal notice than the default: MEMBERSHIP_RE Optional parameter to include active patrons only (active within passed number of months). +Active patrons are those who have not expired, been anonymized or taken any of the actions +defined in the TrackLastPatronActivityTriggers system preference. + =item B<-inactive> Optional parameter to include inactive patrons only (inactive within passed number of months). This allows you to e.g. send expiry warnings only to inactive patrons. +Active patrons are those who have not expired, been anonymized or taken any of the actions +defined in the TrackLastPatronActivityTriggers system preference. + =item B<-renew> Optional parameter to automatically renew patrons instead of sending them an expiry notice. -- 2.41.0