Mini Mods - [OzzModz] Email Admin For Expiring Subscriptions

Another mod brought to you by,


This mod will allow admins to get emails for their users paid subscriptions that are about to expire. This is a cron job, and it will sent the specified email addresses the email between 2 - 3 days before the subscription expires. This should allow you to perhaps entice the member somehow to renew their subscription. Because they may have not got the mail notifying them that it is about to expire.

The email title, as well as the message that is sent is phrased, so you can translate it to your language.

It is a simple installation upload the contents of the UPLOAD folder, then import the product XML, ozzmodz_sub_expiry

You can edit the options under the settings, [OzzModz] Email Admin For Expiring Subscriptions Settings

Complete Feature List

• Option to disable the mod completely.
• Option to set which emails to send the email to when a users paid subscription is about to expire.

Frequently Asked Questions.

Q. Why do I need such a thing, you ask?

A. Some admins might like to know before hand that a users paid subscription is going to expire.

Q. Can I send it to multiple email addresses??

A. Yes you can.

-------------------------------------------------------------------------------------------

If you like this mod please hit the button to the right ---->

Please remember to click the, button to the right if you installed the mod ---->

What does 'Marking As Installed' do ?

* It helps you to stay on top of updates - members who have installed modifications will be notified whenever new updates are available.

* For security issues - vbulletin.org will contact all members who have installed a modification whenever a security issue is brought to their attention.

* Marking a modification as installed also helps me know how many people are using my work, giving me extra incentive to provide more features and new modifications.

I appreciate the support!
-------------------------------------------------------------------------------------------

* History (Changelog) *
-------------------------
v1.0.0 (January 8, 2015)
- Initial public release.

[ozzy47]

Originally Posted by TheLastSuperman

*Idea

If possible, have option to allow admin to specify receiving email of subscriptions not renewed after X days of expiring - this way they know who has not renewed by said set # of days since subscription is marked as expired. Edit: This will allow the admin to reach out to them and see why they didn't renew and possibly work something out or give them a discount to regain their subscription.

Actually now that I think about it, is the subscription information retained in the subscriptionlog table after it expires? I don't use them, so I do not know for sure.

[TheLastSuperman]

Isn't that what status in that table is used for?

Edit: Why does that seem like grammar in a half shell ^

PHP Code:

AND status = 1 


[ozzy47]

This is the lines of code that runs on the cron.

if (is_array($subobj->subscriptioncache))
{
    foreach ($subobj->subscriptioncache as $key => $subscription)
    {
        // disable people :)
        $subscribers = $vbulletin->db->query_read("
            SELECT userid
            FROM " . TABLE_PREFIX . "subscriptionlog
            WHERE subscriptionid = $subscription[subscriptionid]
                AND expirydate <= " . TIMENOW . "
                AND status = 1
        ");

        while ($subscriber = $vbulletin->db->fetch_array($subscribers))
        {
            $subobj->delete_user_subscription($subscription['subscriptionid'], $subscriber['userid'], -1, true);
        }
    }

So if I read that right, it deletes the subscription.

[TheLastSuperman]

I read the same... so then perhaps add a field to your mod, when it emails them it adds their userid and subscription type then query said table every 10 days or so via cron, if their userid is present it emails admin or something like that still just spitting out ideas. One way to work around the deletion of subs and also retain prior sub info in a sense but like I said twas just an idea up to you IF you want to go through the trouble.

[ozzy47]

Perhaps, if their is enough interest. but it seems like a lot of trouble to go through. IMO the records should not be deleted anyway, they should stay in the DB untill I of course want to thin out the table, then I should be able to run a cron, to delete subscriptions older than X.

To bad they did not think of it when they built the system.

[CharlieDelta]

I like the idea proposed by Superman. :up:

[ozzy47]

Cool, that's two.

[Fields]

Damn, can you read my mind? I've been waiting for months for this, thank you very much ozzy

[ozzy47]

I know something like this has been asked for quite a few times over the years, so I figured why not.

Thanks for marking as installed.

[ozzy47]

Originally Posted by TheLastSuperman

I read the same... so then perhaps add a field to your mod, when it emails them it adds their userid and subscription type then query said table every 10 days or so via cron, if their userid is present it emails admin or something like that still just spitting out ideas. One way to work around the deletion of subs and also retain prior sub info in a sense but like I said twas just an idea up to you IF you want to go through the trouble.

I just made a subscription expire, and it seems to just update the DB and set status to 0

So could someone that actually runs paid subscriptions check their DB and see if it holds all the expired ones?