|
TEDxMontreal
|
August 23, 2016 at 2:03 pm
Hi,
I’ve been having some difficulty with the messaging system lately and this same problem has cropped up twice in the last couple days.
I set up an version v4.9.4.p of EE a couple weeks ago, and everything was working smoothly as I was setting up our events and tickets, plus test submissions were generating and sending the appropriate emails. It suddenly stopped sending emails on Sunday evening, where messages were getting stuck in the Generation queue. I searched through some of the forum topics here for solutions, and ended up updating my version of EE to the latest release v4.9.8.p before doing some more tests. This mornings test submissions went smoothly, but I recently noticed that my latest messages are stuck in Queue Generation yet again.
From one of the other forum posts I learned about wp-crontrol, which I installed and inspected the cron events. That’s where I discovered both yesterday, and today after the new install, that both of the messaging cron hooks have disappeared:
AHEE__EE_Messages_Scheduler__sending and
AHEE__EE_Messages_Scheduler__generation
After I did this mornings plugin update, I checked cron events and they were in the list, so I know they disappeared sometime in the last hour or so.
I did also check that wp_cron() is enabled, and in searching for other solutions found someone who mentioned that I could also set the alternate_wp_cron to true, which I also did using this line of code
define(‘ALTERNATE_WP_CRON’, true);
So I have no idea where to go from here. Can someone help?
|
|
Melissa Jones
|
August 23, 2016 at 11:14 pm
Seem to be having the same problem all of a sudden as well. Had created a “custom message” then deleted it. Not sure if that triggered the problem or is inconsequential.
|
|
Melissa Jones
|
August 23, 2016 at 11:20 pm
Switching message settings to “on the same request” solves the problem for now – since the emails are generating “instantly” as opposed to being queued. But would prefer the other option.
|
|
TEDxMontreal
|
August 24, 2016 at 8:29 am
Helpful to know that I’m not the only one having problems. I hadn’t actually tried switching the message settings to ‘on the same request’ but I might try that.
In the meantime, I have a update. I just updates my WordPress to version 4.6 just to make sure there wasn’t something in the previous release that might have been part of the problem. Now the platform and plugins are up to date.
I also de-activeated EE, and re-activated it which forced the cron events to reappear in the list
AHEE__EE_Messages_Scheduler__sending and
AHEE__EE_Messages_Scheduler__generation
but now that I’m checking my Cron events again, they are no longer listed in the scheduler and I’m starting to get really frustrated.
Is there someone on the Event Espresso support team that might be able to shed some light on why the event schedulers would disappear unexpectedly? Have you seen this issue come up before, and if so is there any way I can fix it without having to re-activate EE the next time it happens? We want to start selling tickets to our event soon and this is preventing us from launching sales.
|
|
Tony
|
August 24, 2016 at 9:16 am
Helpful to know that I’m not the only one having problems. I hadn’t actually tried switching the message settings to ‘on the same request’ but I might try that.
Setting the option to use ‘On the same request’ basically switches EE back to the ‘old’ system and doesn’t use WP_CRON anymore which means it should work.
Is there someone on the Event Espresso support team that might be able to shed some light on why the event schedulers would disappear unexpectedly? Have you seen this issue come up before, and if so is there any way I can fix it without having to re-activate EE the next time it happens?
This is not something we have seen before and will need to investigate further.
Do either of you have any ‘optimization’ plugins installed on the site? Can you provide a list of installed plugins?
Which hosting company are you both using?
|
|
Josh
|
August 24, 2016 at 9:31 am
What’s probably happening is there’s a fatal error (or an out of memory error) while executing the cron, which will prevent WordPress from to rescheduling the next cron. So in your case, when you activate EE the crons are there, but after they or one of the later crons are run, they’re not getting rescheduled. You can check your PHP error logs for any fatal errors, and also bump up the amount of memory available to WordPress.
You can increase the amount of memory available for WordPress by following this guide:
http://codex.wordpress.org/Editing_wp-config.php#Increasing_memory_allocated_to_PHP
You can use an [FTP client][1] and [a text editor][2] to edit the site’s wp-config.php file:
[1]: http://codex.wordpress.org/FTP_Clients
[2]: http://codex.wordpress.org/Editing_Files#Acceptable_External_Editors
You also have the option to not use crons at all, by switching the message settings to Send messages On the same request.
|
|
TEDxMontreal
|
August 24, 2016 at 9:48 am
Thanks Josh, I checked my servers PHP error log on Monday the first time this happened and I didn’t see any errors logged there, but I can check the logs again to see if anything is logged in there now.
I’ll go through the codex guide to see if I can increase the amount of memory available to WordPress and will also try the option of sending messages on the same request.
And Tony to answer some of your questions as well, I have one optimization plugin installed on our production site, WP Smush, but here’s a list of all the plugins I have installed to give you some context:
Advanced Custom Fields
Advanced Custom Fields: Repeater Field
Custom Post Type UI
GM Block Bots
Polylang
WP Admin Bar Removal
WP Crontrol
WP Smush
Then I have the EE core + all some addons installe:
Event Espresso – Barcode Scanner (EE 4.6.0+)
Event Espresso – MailChimp (EE4.4.5+)
Event Espresso – People Addon (EE 4.5+)
Event Espresso – Promotions (EE 4.8+)
Event Espresso – Stripe Gateway (EE 4.6.0+)
Event Espresso – Ticketing (EE 4+)
Event Espresso – WP Users (EE4.6+)
The production site is also hosted on InMotion. I do also have a staging site where I test out updates before launching them on the production server, and the setup is identical to this one. That site is hosted on A Small Orange, but the EE core has only been up there since Monday and I haven’t seen this issue come up on that site yet.
|
|
TEDxMontreal
|
August 24, 2016 at 9:55 am
Josh, I just checked the error log on my InMotion server, and there aren’t any errors in there this time around.
|
|
Josh
|
August 24, 2016 at 10:23 am
If it was a WordPress generated error it wouldn’t necessarily be captured in the server’s error logs. Instead, you’d need to set WordPress to debug mode, and you can disable error display so the errors are only written to /wp-content/debug.log.
See this section of the codex for more info on how to set up error logging for WordPress:
https://codex.wordpress.org/Debugging_in_WordPress#Example_wp-config.php_for_Debugging
|
|
TEDxMontreal
|
August 24, 2016 at 4:05 pm
Ah I hadn’t thought about turning on debug mode. I’ll have a look at that codex as well in the meantime.
|
