Try this instead: $gloabl $myxclass; $myxclass = new Xwidget(); add_action( ‘xxx_followers’, array(&$myxclass, “cron_addB” ) ); or add_action(‘xxx_followers’, “init_xclass_and_cron”); function init_xclass_and_cron() { $myxclass = new Xwidget(); $myxclass->cron_addB(); }
You have to schedule your event in a hook, for example in after_setup_theme or wp actions: add_filter(‘cron_schedules’,’my_cron_definer’); function my_cron_definer($schedules){ $schedules[‘twomin’] = array( ‘interval’=> 120, ‘display’=> __(‘Once Every 2 Minutes’) ); return $schedules; } add_action(‘my_periodic_action’,’my_periodic_function’); function my_periodic_function(){ mail(’[email protected]’,’Test!’, ‘Test Message’); } add_action( ‘wp’, ‘wpse8170_setup_events’ ); // or add_action( ‘after_setup_theme’, ‘wpse8170_setup_events’ ); function wpse8170_setup_events() { if ( … Read more
For Q1 – One for each path / site. Each site has its own cron (jobs) internally. So, it is possible to fine-tune the frequency. For example, a low-traffic site may not have lots of cron jobs. So, the cron could be executed less frequently than a site that requires frequent updates. For Q2 – … Read more
Cron tasks don’t directly affect page load besides the 0.01s timeout (of course, they do affect server load, so they can impact page load indirectly). My hunch is that your PHP config is the issue. The cron tasks run like any other web request, and they’re subject to PHP’s max_execution_time INI setting. If this is … Read more
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