Context Navigation

Changes between Initial Version and Version 1 of Ticket #24160, comment 22

initial	v1
2	2
3	3	* When `wp-cron.php` is accessed with a direct POST request, either as a result of `spawn_cron()` or as a result of a real server cron job requesting it, `wp-load.php` is included and then any pending cron events are iterated and run. This means actions such as `init` and `wp_loaded` have finished executing by the point where the cron events are run.
4		* With `ALTERNATE_WP_CRON` in use, the `wp_cron` function that's hooked into `init` does an `include_once( 'wp-cron.php' )` which then iterates and runs pending cron events after flushing a redirect header to the client.
	4	* With `ALTERNATE_WP_CRON` in use, the `wp_cron()` function that's hooked into `init` does an `include_once( 'wp-cron.php' )` which then iterates and runs pending cron events after flushing a redirect header to the client.
5	5
6	6	This means with `ALTERNATE_WP_CRON` in use, cron events run within the `init` hook on priority 10. Without it in use, they run after the `wp_loaded` action has fired.