https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30301

Matt Blenkinsop <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #181105|0                           |1
        is obsolete|                            |

--- Comment #24 from Matt Blenkinsop <[email protected]> ---
Created attachment 182155
  -->
https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=182155&action=edit
Bug 30301: Update cronjob to check for mandatory notice

The patches on this bug add the ability for staff members to set the patron
expiry notice as mandatory at the category level. When set, the cronjob will
automatically send an expiry notice regardless of existing messaging
preferences. If it is turned off, the old messaging preferences will still be
in place and actioned

Test plan:
1) Apply patch and run updatedatabase
2) In system preferences set MembershipExpiryDaysNotice to 5
3) Choose a patron and edit their expiry date to today's date, ensuring they
have a primary email set
4) Create a MEMBERSHIP_EXPIRY notice (content of the notice is irrelevant, just
needs to exist)
5) Run perl misc/cronjobs/membership_expiry.pl -c -v -before 10 -after 10
6) Check the patron's messages, there should be no expiry notice queued
7) Set the patron's category 'enforce expiry notice' field to Yes
8) Repeat step 5, there should be a notice queued
9) Set that patron's primary contact method to primary email and run step 5
again
10) There should be a notice queued for an email
11) Set the category level enforce expiry notice back to No
12) Choose a second patron and set an email address, expiry date to today and
set the patron expiry messaging preference for that patron to 'email'
13) Repeat step 5 - this time only one notice should be queued on the second
patron, no new notice should queue for the first
14) Re-set the category level option to Yes
15) Repeat step 5 - this time both patron's should have notices queued
16) Unset the category level option again, the behaviour should be the same as
step 13
17) Set the category level option back to Yes and check the patron messaign
preferences menus in both the OPAC and Staff client - the patron expiry option
should not be visible while the cateogry level enforcement is set to Yes

Signed-off-by: Hanna Leiker <[email protected]>

-- 
You are receiving this mail because:
You are watching all bug changes.
_______________________________________________
Koha-bugs mailing list
[email protected]
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Reply via email to