The filter accepts an array of non-default cron schedules in arrays (an array of arrays). The outer array has a key that is the name of the schedule (for example, ‘weekly’). The value is an array with two keys, one is ‘interval’ and the other is ‘display’.
The ‘interval’ is a number in seconds of when the cron job shall run. So, for a hourly schedule, the ‘interval’ value would be 3600 or 60*60. For for a weekly schedule, the ‘interval’ value would be 60*60*24*7 or 604800.
The ‘display’ is the description of the non-default cron schedules. For the ‘weekly’ key, the ‘display’ may be __(‘Once Weekly’).
Why is this important?
When scheduling your own actions to run using the WordPress Cron service, you have to specify which interval WordPress should use. WordPress has its own, limited, default set of intervals, or “schedules”, including ‘hourly’, ‘twicedaily’, and ‘daily’. This filter allows you to add your own intervals to the default set.
For your plugin, you will be passed an array, you can easily add a weekly schedule by doing something like:
function my_add_weekly( $schedules ) {
// add a 'weekly' schedule to the existing set
$schedules['weekly'] = array(
'interval' => 604800,
'display' => __('Once Weekly')
);
return $schedules;
}
add_filter( 'cron_schedules', 'my_add_weekly' );
Adding multiple intervals works similarly:
function my_add_intervals($schedules) {
// add a 'weekly' interval
$schedules['weekly'] = array(
'interval' => 604800,
'display' => __('Once Weekly')
);
$schedules['monthly'] = array(
'interval' => 2635200,
'display' => __('Once a month')
);
return $schedules;
}
add_filter( 'cron_schedules', 'my_add_intervals');
Be sure to add your schedule to the passed array, as shown in the example. If you simply return only your own schedule array then you will potentially delete schedules created by other plugins.
Add a custom cron schedule for every 5 minutes:
As a handy tip to save your time, I’d suggest to always hook to
cron_schedules
filter inside a major action that runs on each page load. Likeinit
orwp_loaded
. And also hook to that filter before your code using the custom schedule.For example:
This approach guarantees that your custom schedule is always registered before it is used in
wp_schedule_event
function. And saves you from nasty"invalid_schedule":"Event schedule does not exist."
error.Cheers :)
custom cron schedule for every 10 & 15 Seconds
Add a user-defined interval value:
Using functinal approach
Using class based approach