Finally, I discovered what was wrong: the webserver (a dedicated VPS) had a bad configuration of the hosted domain, so it was unable to “self contact” it, to call wp-cron.php . I fixed it and now every scheduled job works, including this one 🙂
This is an old question, but hopefully this helps someone facing the same issue. We can use wp_get_schedule( $hook ) to retrieve the cron schedule for the hook. Then we can use wp_get_schedules() to retrieve the supported cron recurrences. Find the correct array value and return it. /** * Retrieve Cron interval for hook. * … Read more
The _get_cron_array() function gets the ‘cron’ option out of the database. The cron option contains an array consisting of a series of unix-timestamps and action hooks. So, when the timestamp is reached, then the action hook is called. The timestamp of 1465529020 is the equivalent of June 10th, 2016, at 3:23am in UTC time. The … Read more
WP-Cron is not intended to be that precise, and should not be used if you have to have things scheduled at specific times. WP-Cron is a “best effort” scheduling mechanism, and it cannot guarantee run timing like a real cron system can. If you need precision of this nature, the only real answer is to … Read more
This is what normal query run by wp_get_associated_nav_menu_items() looks like: SELECT wp_posts.* FROM wp_posts INNER JOIN wp_postmeta ON ( wp_posts.id = wp_postmeta.post_id ) WHERE 1 = 1 AND wp_posts.post_type=”nav_menu_item” AND (( wp_posts.post_status <> ‘trash’ AND wp_posts.post_status <> ‘auto-draft’ )) AND (( wp_postmeta.meta_key = ‘_menu_item_object_id’ AND Cast(wp_postmeta.meta_value AS CHAR) = ‘3111’ )) GROUP BY wp_posts.id ORDER … Read more
Edit: wp_next_scheduled() returns the timestamp of the next scheduled job of a specified wp-cron job-arguments pair. Please note that this differs slightly in functionality to the answer below, in that you have to provide the arguments passed to cron job’s callback (if it has any). The original answer would provide the time of the next … Read more
This is the intended use of the WP_CRON_LOCK_TIMEOUT constant. When WordPress is loaded, it checks to see if a cron job is running (if cron is locked). If cron is not locked, it will try to create a lock – if the lock timeout has not been reached, no lock can be acquired and cron … Read more
Yes, delete_expired_transients is a cron event that runs once per day and the function delete_expired_transients() is automatically called when the cron event runs — see wp-includes/default-filters.php. So you do not need to call the function manually like you did in your my_custom_fn() function. And if you use a plugin like WP Crontrol, you can easily … Read more
I was working with wp_cron last week in a plugin and we have a fight and are no longer on speaking terms, but for reference this is what I do; 1) – set the scheduled cron event on register_activation_hook 2) – remove the scheduled cron event on register_deactivation_hook If you are concerned that your scheduled … Read more
Looking at the file documentation inside wp-cron.php it seems it’s absolutely possible to just call $ php wp-cron.php: /** * A pseudo-CRON daemon for scheduling WordPress tasks * * WP Cron is triggered when the site receives a visit. In the scenario * where a site may not receive enough visits to execute scheduled tasks … Read more