DISABLE_WP_CRON intentionally set to 'true'

Thanks for the feedback!

I’m not so sure that hiding it is a good idea. I guess I could change this particular message so it doesn’t appear as a bright red error, but as an informational message instead (similar to the “Post updated” message), and any real errors (eg. problems with HTTP connections) would continue to be displayed as an error.

Perhaps an ‘X’ to hide the message, or check if internal crons are outstanding/waiting to be executed? Either way, it’s not necessary as I previously mentioned ??

Hey guys just piping in here… We have the same issue on WP Engine hosting when using WP Engine’s Alternate Cron. More info https://wpengine.com/support/wp-cron-wordpress-scheduling/

Just like @cryptodechange’s use-case, the DISABLE_WP_CRON constant is intentionally set to true.

I would definitely not hide the message, but perhaps a ‘yes I know, don’t bug me about it’ option? Or an advanced setting in the plugin to disable that notice?

This now displays a less scary blue notice instead of the bright red error message.

We also set the DISABLE_WP_CRON constant to true, intentionally of course.

A “hide” option for this WP_Cron warning would be nice. This can be saved similar to how other modules or plugins save notification states (as a simple user_meta flag in the db).

As you may be aware, scheduled tasks run dependent on traffic to your site. For critical background tasks that need to run regardless of traffic, the normal alternative is to setup a real cronjob and having it run https://www.example.com/wp-cron.php?doing_wp_cron at needed intervals.

For example:

* * * * * wget -q -O - https://www.example.com/wp-cron.php?doing_wp_cron

… will run that job once per minute.

In our case we need to query an external server for company memo’s and trigger push notifications to mobile devices as the memo’s came in. If a memo is pushed out after working hours and no one is using the WordPress site, the memo notifications weren’t being sent until some traffic was generated. This could be two days later if we’re talking about a weekend!

The current WordPress mechanism to schedule tasks, although nifty, has it’s limitations. Using an actual cronjob solves this issue. But now there is a warning in the admin which doesn’t go away. There should be at least a hide option.

Just my two cents.