Reminder emails for coming EOT/payment

[clavaque]

We can try to tackle it together one gateway at a time, starting with PayPal.

[jaswrks]

Thanks! Moving this to the "Future Release" milestone; i.e. the release after the next.

[jaswrks]

@clavaque Volunteered to assist on this one.

[jaswrks]

Moving this to the "Distant Release" Milestone.

[clavaque]

@jaswsinc I've been working on this last night.

The simplest version of this feature would use usermeta's s2member_auto_eot_time when it's available, and send an email n days before. More than one email would be possible.

After an email is sent it'll be logged as such in a usermeta entry, and before sending an email that entry would be checked to see if it wasn't sent already.

There could be a scheduled job that checks often all s2member_auto_eot_time rows and the sent emails log, to see if new ones need to be sent.

Another approach, that I like better, is to have a schedule for emails to be sent. Their times could be calculated as soon as an s2member_auto_eot_time is set for the user, and added to the schedule.

The wp_cron schedule could be used, or a new table for these could be created. The wp_cron schedule would be simpler to implement for now.

The s2Member Pro update should include a script that runs once to add any missing emails from the wp_cron schedule.

So we're working with s2member_auto_eot_time, and all running subscriptions wouldn't have that set before they end. Buy-nows are easy, though.

For ongoing subscriptions, in the future we could add API calls that find out the details for it, and we calculate when the next payment would happen, schedule the email to remind about the coming payment.

[clavaque]

It seems not all places where s2member_auto_eot_time is added/updated/removed have a hook we can use to schedule its emails. I guess once/twice daily all s2member_auto_eot_time rows could be checked for additions/updates/removals.

If one got added, then its emails would get scheduled. If one got updated, it's emails would need to be rescheduled. If one got removed, its emails would need to be unscheduled.

That is more work, though, it'd be best if we can find how to update the schedule at the same time the s2member_auto_eot_time is touched. Well, they're all done inside of s2Member, so I guess we don't need hooks, we can just call the EOT email scheduler ourselves wherever needed.

[clavaque]

-- Find in Files: (add|update|delete)_user_.+s2member_auto_eot_time in *.php --
"s2member-pro\includes\classes\imports-in.inc.php"(204,37)
"s2member-pro\includes\classes\imports-in.inc.php"(265,21)
"s2member-pro\includes\classes\imports-in.inc.php"(320,33)
"s2member-pro\includes\classes\remote-ops-in.inc.php"(304,10)
"s2member-pro\includes\classes\gateways\authnet\authnet-checkout-in.inc.php"(280,21)
"s2member-pro\includes\classes\gateways\authnet\authnet-checkout-in.inc.php"(490,24)
"s2member-pro\includes\classes\gateways\authnet\authnet-checkout-in.inc.php"(514,24)
"s2member\includes\classes\auto-eots.inc.php"(122,15)
"s2member\includes\classes\auto-eots.inc.php"(167,19)
"s2member\includes\classes\paypal-notify-in-subscr-modify-w-level.inc.php"(124,15)
"s2member\includes\classes\paypal-notify-in-subscr-or-rp-cancellation-w-level.inc.php"(81,17)
"s2member\includes\classes\paypal-notify-in-subscr-or-rp-eots-w-level.inc.php"(137,21)
"s2member\includes\classes\paypal-notify-in-subscr-or-rp-eots-w-level.inc.php"(263,19)
"s2member\includes\classes\paypal-notify-in-subscr-or-rp-eots-w-level.inc.php"(285,17)
"s2member\includes\classes\paypal-notify-in-subscr-or-wa-w-level.inc.php"(145,19)
"s2member\includes\classes\paypal-notify-in-subscr-or-wa-w-level.inc.php"(149,75)
"s2member\includes\classes\paypal-return-in-subscr-modify-w-level.inc.php"(131,15)
"s2member\includes\classes\paypal-return-in-subscr-or-wa-w-level.inc.php"(178,18)
"s2member\includes\classes\registrations.inc.php"(578,17)
"s2member\includes\classes\registrations.inc.php"(742,17)
"s2member\includes\classes\registrations.inc.php"(874,17)
"s2member\includes\classes\user-deletions.inc.php"(127,9)
"s2member\includes\classes\users-list-in.inc.php"(458,14)
23 occurrences have been found in 13 files.