Product Cancellation/Expiration Options
In DAP 4.4, we have added a new feature to the hourly dap cron where once every day (it’s hardcoded to run ONCE between 10:00 PM – 11:00 PM PDT) the cron will look for users whose access expired that day.
You can configure the Cancellation Options in DAP Products page -> Cancellation & Expiration tab.
Then based on these settings, the DAP Hourly Cron will check if the current time is between 10:00 – 11:00 pm PDT (Server time), and if yes, it will take a look at each product, pick up the ‘Expiration Action’ setting for that product, then get a list of ALL users whose access to that product has expired and apply the ‘Expiration Action‘ to that user->product record in DAP users -> manage page.
The reason the dap cron checks the current time and runs the ‘expiration job’ only once a day is because running it too often will burden your server/resources as this job needs to pick up all products and then apply the cancellation rule to all users whose access has expired.
The main thing is to make sure it only runs once.. does not matter if that’s between 10 – 11 or 11 – 12 etc. We just picked the time to be between 10 – 11 PM (server time).
1) No Action
User’s access will auto-expire at the end of current recurring cycle. If the user re-signs, they will start from where they left off instead of starting over at day 1.
Infact this is how all older versions of dap already work.If a user cancelled access to a subscription product before and say that the same user now wants to start back after a couple of months break.
If you have selected NO ACTION as this product’s expiration setting (in dap products page -> cancellation & expiration tab),
then when the user re-signs, they will start their dripping from where they left off and will not start fresh again from day 1.
Say a user’s access start date is 10/01/2012 and access end date is 10/30/2012, when the cron runs on 10/31/2012
and finds the user’s access has expired, it wont do anything.
If the same user resigns on 11/30/2012, their access start date will be what it was before (10/01/2012) but their new access end date will be 10/31/2012 + 30 days (instead of 11/30/2012+30 days). User’s access to product will remain expired. You will have to set post-expiry access to “Y” in dap setup->config page for access to paid for content.
See this for more details: http://www.digitalaccesspass.com/forums/threads/741-Subscription-Cancellation
2) Remove From Product
If selected, dap will automatically find users whose access to this product has expired and remove user’s access to product completely for those users.
You will need this setting to prevent access for expired users. User will completely lose access to product.
If the user signs up again, they will start over like a new member.3) Set end date to previous day.
Automatically move the expired user’s access start and end day (set the access end date to the previous date).
When the cron wakes up and runs this job once daily, it will keep moving the user’s access start / end date
forward in such a way that user’s access will remain expired but the access end date will not be stuck somewhere in past,
it would be always set to the previous date (from current date).Say a user’s access start date is 10/01/2012 and access end date is 10/30/2012, when the cron runs on 10/31/2012
and finds the user’s access has expired, it will set the access end date to previous date.. so first time when
the cron runs after the user’s access expires, nothing will happen, access end date will remain 10/30,
but when cron runs on 11/1, it will now move the access end date to previous date so the new access start date will be 10/02/2012
but end date will be 10/31/2012 (the access start / end block is moved forward).So if the cancelled user re-signs, the user’s access will not remain expired as their access will be extended from the access end date
to a date in future and the dripping will continue from where they left off. You would probably want to use this setting if you are on DAP 4.4.