Home › Forums › Newsletter Plugin Support › Weird problem with delivery engine stopping, cron working
- This topic has 13 replies, 2 voices, and was last updated 9 years, 4 months ago by essemme.
October 31, 2013 at 12:45 pm #9643
first of all, great plugin!
I’m having a strange problem with the delivery engine. It could be related to my setup or some plugin incompatibility.
I’ll be glad to dig into the code, just needing some directions and suggestions.
Here is the problem:
Context: it is a multisite install, the plugin is not network activated – it is active only on the main site.
The delivery engine is not started. “trigger now” doesn’t change this. (just sends a batch of email messages if a newsletter is sending)
The cron system works. Diagnostics (from newsletter plugin and diagnostic plugin) confirms this. Other planned tasks are working (daily rss import, post category expiry, etc).
“newsletter” cron job is correctly listed. But diagnostics shows no events / jobs are planned.
Disabling and re-enabling the newsletter plugin seems to fix this for a while (minutes, hours, don’t know). But then the delivery engine stops again (cron ok, newsletter job listed, but no future events planned)
Other: using w3 total cache. But wp-cron.php is set to be ignored (not cached).
Another (previously used) newsletter plugin is installed but not active (in any site).
Wordfence security plugin installed (should not interfere with this, who knows).
Where should I start looking.. (i do know php, and played a bit with wp conding, but i’m far from expert on this), or any other info I could provide to make the issue clearer?
Is anybody else experiencing this problem?
Thank you very much!October 31, 2013 at 12:52 pm #9645
Hi, strange to have the delivery engine completely stopped. Can you install the diagnostic plugin (on my downloads area, free) that will list all the jobs and their status? It would be helpful if you can send me a screen shot of the “cron” panel of that plugin.
The plugin DOES NOT interfere with wordpress.October 31, 2013 at 12:52 pm #9646
By the way, I forgot to mention: wordpress 3.7.1, newsletter plugin 3.4.0October 31, 2013 at 12:59 pm #9647
Thank you, that was fast!
Yes, I did already install “diagnostic” – it’s the one telling me no events are planned.
Just re-enabled the plugin, so it’s working right now , i’ll take the screenshot later when (if!) it stops againOctober 31, 2013 at 2:01 pm #9649
In the diagnostic panel, first table, there is the schedule named “newsletter”?October 31, 2013 at 2:10 pm #9651
In Schedule, yes. Not in events, belowOctober 31, 2013 at 3:59 pm #9653
Ok, it stopped.
manually triggered, still stopped
Forn diagnostic -> cron panel:
(“newsletter” cron job is in schedule. But there are no more related events)
I confirm: Re-enabling the plugin restarts the delivery engine (events)October 31, 2013 at 4:02 pm #9655
Uhm, are maybe remote images blocked?
I’ll send the screenshot by email. Or edit using links onlyOctober 31, 2013 at 5:29 pm #9658
So it means that once executed it is removed, like if the schedule disappears (hence WordPress is not able to reschedule it), this is very strange.
Usually the scheduled task is not rescheduled if during the cron job the times table is not correctly compiled (eg, when something blocks newsletter while adding its own schedule).
I’ll change the diagnostic plugin to track down the schedule table while wordpress is doing the cron.October 31, 2013 at 7:13 pm #9659
This seems very useful!
Hope it will give hint’s on what’s conflicting (or what’s going on in this case)October 31, 2013 at 11:44 pm #9660
Hi, on diagnostic plugin under “hooks”, seek for “cron_schedules”: what is listed on that row?October 31, 2013 at 11:45 pm #9661
They are evernote images, only you probably can see it. I got an access denied error.November 1, 2013 at 12:39 am #9662
Hi essemme, would you like to contact me via email@example.com so I can send you an updated version of diagnostic plugin with some instructions?November 1, 2013 at 11:27 am #9664
1. hooks -> cron_schedules:
2 and 3: images: whoops, those were supposed to be the shared ones, the links should be public – i’ll check.
Great, i’ll drop an email message
- You must be logged in to reply to this topic.