My send intervals are all set to null in the queue and when I manually change it to "1" it works fine. Is there a setting I am missing here to update all of the subscribers to receive the updates "as soon as possible" instead of never?

Comments

salvis’s picture

I'm not sure what you mean.

This seems to be an odd left-over from your 5.x-1.9 installation (which has been unsupported for over two years).

Go to admin/settings/subscriptions/intervals — you should see entries like

1|as soon as possible
10800|every three hours
86400|daily

There should be no "0" entry.

wildmtsky’s picture

Thanks for the reply. I actually removed every table related to the old subscription module. I do see what you are talking about in the settings interval, however, when I go to the actual tables in phpmyadmin, all of the pending emails have an interval set to null. But I have actually set the interval to be 1. Does this make sense? Should I get screenshots?

wildmtsky’s picture

I dug a little deeper and found that in the subscriptions table everyone has a send interval of null. Is the send interval a new field in this version?

salvis’s picture

Somehow your installation is messed up.

If you've removed all the old tables you've started from scratch and I'd suggest you do this again. Disable the Subscriptions modules and then uninstall them (don't just delete tables!). Then enable them again. This should get you up and running.

wildmtsky’s picture

Thanks.... I just did an update query in mysql and made all of the send intervals "1". Worked just fine. All emails successful.

Thanks for your help!

salvis’s picture

But what happens when you create new subscriptions? Do they get the proper value?

Be careful with the values in {subscriptions_user}: the -2 record is the site default and the other records should probably have -1, which means 'use the site default'.

wildmtsky’s picture

good to know! Thanks!

salvis’s picture

Status: Active » Fixed

Feel free to reopen if we need to pursue this further.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.