My recommendation would be to set up a wrapper for fetch_feed(). Call the wrapper function through WordPress’ cron and you shouldn’t have an issue. So something like: function schedule_fetch_feeds() { if ( ! wp_next_scheduled( ‘cron_fetch’ ) ) { wp_schedule_event( time(), ‘hourly’, ‘cron_fetch’, ‘http://blog1.url/feed’ ); wp_schedule_event( time(), ‘hourly’, ‘cron_fetch’, ‘http://blog2.url/feed’ ); } } function fetch_feed_on_cron( $url … Read more
Your option using WP internals would be to use the HTTP API along with wp schedule event Create a scheduled event, something like: register_activation_hook(__FILE__, ‘my_schedule’); add_action(‘execute_my_url’, ‘do_this_daily’); function my_schedule() { $timestamp = //some time you want it to run wp_schedule_event($timestamp, ‘daily’, ‘execute_my_url’); } function do_this_daily() { wp_remote_get( ‘../ =myvideoblog/mvb_main.php&action=processfeed&updatefeed=67’, $args); } This is a simple … Read more
Turns out I had to set the ALTERNATE_WP_CRON flag in wp-config.php to make this work: define(‘ALTERNATE_WP_CRON’, true);
Not sure what is the question, but the use of time() is wrong as it will give you at best the local time of the server and not the local time of the site which takes into consideration the time zone configuration of WordPress. The function that you should use is current_time.
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
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
Transients expire on their own. No need to unset them. And to call wp-cron manually is simple. Just define DISABLE_WP_CRON to true in the wp-config file to disable the normal cron spawning process. Then make your cron system hit wp-cron.php manually every so often to process pending jobs. There is no other special trick that … Read more
A transient is set to reflect the state of the cron, which gets deleted when all tasks complete. Any subsequent requests are ignored if that transient is found…
Use a file to write the events to. There are several drawbacks here; Filesystem permissions. When you deploy your app, you will have to take care to remember to give the webserver permission to write to the file. And to be extra sure, you’d have to write code which checks whether you can write to … Read more