Closed (fixed)
Project:
Subscriptions
Version:
6.x-1.3
Component:
Miscellaneous
Priority:
Critical
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
15 Feb 2011 at 16:44 UTC
Updated:
17 Mar 2013 at 17:56 UTC
I have imported over 5,000 subscribers to our website a couple of months ago. We have been using the subscriptions module to notify them if a new blog entry is posted. Some subscribers complained they stopped receiving notifications from our website (I suspect that some might never receive). Is there anyway to help fix this problem. Attached show the configurations for every subscriber at our site.
Thanks
| Comment | File | Size | Author |
|---|---|---|---|
| subscriptions_configuraton.png | 19.47 KB | ssun |
Comments
Comment #1
salvisEnable logging on the Subscriptions Settings page. Find out what the cron job does and try to put that in relation to what you expect to happen.
Why do you enable Digest Mode? Especially if you set the interval to ASAP...
Comment #2
ssun commentedSalvis, thank you for your response. The logging on the Subscriptions Settings page has been enabled. At the cpanel, I set up a cron job to let the "cron.php" run every 5 minutes. Following your suggestion, I disabled the "Digest Mode" in mySQL database. How to "find out what the cron job does"? Thanks
Comment #3
salvisLook at the log (admin/reports/dblog).
A single cron run will not be able to send out 5000 mails, but you'll see how many it does send and how it manages to keep up.
Huh? I was talking about "Digest Mode" in the Subscriptions Settings.
Comment #4
ssun commentedThank you, Salvis. Yesterday, immediately after a new blog entry was posted, I used phpMyAdmin to monitor the subscriptions_queue table. As I mentioned in the initial message, I noticed that mail was sent to most users but skipping some users.
Because we have over 5,500 users in the database, so I could not disabled the "Digest Mode" on the the subscriptions setting page for each of them. In the "subscriptions_user" table in the database, I reset value of the "digest" field to "0" with one line of command.
Comment #5
salvisYes, that makes sense.
How did you notice that some were skipped?
Comment #6
salvisNo follow-up.