In wp-includes/default-filters.php we can find a callback registration: // WP Cron if ( !defined( ‘DOING_CRON’ ) ) add_action( ‘init’, ‘wp_cron’ ); If we go the function wp_cron() now, we see this: $schedules = wp_get_schedules(); foreach ( $crons as $timestamp => $cronhooks ) { if ( $timestamp > $gmt_time ) break; foreach ( (array) $cronhooks as … Read more
The answer is apparently YES, I should worry. After some research, I’ve found that the warning seems to be related to misconfigurations on the server that WordPress is hosted on (ie. a problem with my server, not WordPress). Common misconfigurations: Server doesn’t have DNS, and so it can’t figure out who “example.com” is, even though … Read more
Short answer – Nope. Any page request initializes the scheduled queue. It’s just an initialize request. Wp-cron request is a standalone request. so requesting URL /somepage you just initialize request to /wp-cron.php However – If cron event doesn’t work really well (it’s has 1000 db queries e.g. or its requesting a some really long-to-respond resource), … Read more
There is no downside for running WP CRON using the server’s cron jobs. In fact this is the recommended practice. According to Official WordPress Plugin Development Document: WP-Cron does not run continuously, which can be an issue if there are critical tasks that must run on time. There is an easy solution for this. Simply … Read more
Why don’t you just create a cron job, make a database dump and look where the info about the cron job is kept? That’s what I did. As suspected, WordPress 3.5.1 keeps its cron jobs in the {wp}_options table under the name ‘cron’. SELECT * FROM `wp_options` WHERE `option_name` LIKE ‘%cron%’ Or through functions.php: $cron_jobs … Read more