|
David
|
November 10, 2016 at 11:08 am
I’m seeing the following warning from EE4 “Event Espresso has detected that wp_cron is disabled. It’s important that wp_cron is enabled because Event Espresso depends on wp_cron for critical scheduled tasks.
Since it’s possible that your site may have an alternative task scheduler set up, we strongly suggest that you inform the website host, or developer that set up the site, about this issue.”
I’ve spoke with Godaddy support and they’ve indicated that wp_cron is enabled in their environment, but it is not ‘rewriteable’. Will this be a problem and if so is there a workaround?
thanks.
|
|
Josh
|
November 10, 2016 at 2:19 pm
That may be a problem for any functions of your site that need a rewrite-able wp_cron (I’m really not sure what makes for a rewrite able wp_cron, but that surely makes sense to someone at Godaddy).
There is a workaround for the Messages component of Event Espresso for sites that have a restricted wp_cron function though: You can go to Event Espresso > Messages > Settings and change the setting to send messages on the same request.
|
|
David
|
November 10, 2016 at 5:15 pm
Thanks and question. If I’m currently receiving emails from the site when a registration occurs, does that mean that wp_cron (in whatever state that Godaddy has indicated) is working with EE4 and it’s OK to leave that setting at ‘on a separate request’?
|
|
Josh
|
November 10, 2016 at 5:27 pm
Yeah what they might have done is set up an alternative to wp_cron. So anything that normally relies on wp_cron will end up having the scheduled tasks passed on to the alternative, and that’s totally fine.
|
|
David
|
November 10, 2016 at 5:34 pm
thanks again for the help. consider this topic resolved.
|
