2007-08-17 06:33:52 -04:00
< ? php
2007-10-30 17:40:30 -04:00
/**
2008-08-12 17:21:11 -04:00
* A simple set of functions to check our version 1.0 update service .
2007-10-30 17:40:30 -04:00
*
* @ package WordPress
2008-09-18 13:32:18 -04:00
* @ since 2.3 . 0
2007-10-30 17:40:30 -04:00
*/
2007-08-17 06:33:52 -04:00
2007-10-30 17:40:30 -04:00
/**
2008-08-12 17:21:11 -04:00
* Check WordPress version against the newest version .
*
2008-08-01 01:00:07 -04:00
* The WordPress version , PHP version , and Locale is sent . Checks against the
* WordPress server at api . wordpress . org server . Will only check if WordPress
* isn ' t installing .
2007-10-30 17:40:30 -04:00
*
2008-08-27 02:45:13 -04:00
* @ since 2.3 . 0
Add missing doc blocks to `update.php`:
* `wp_version_check()`, `wp_update_plugins()`, and `wp_update_themes()` do not return meaningful responses, and their responses are never handled by core. As such, they shouldn't alternately return `void` or `false`. "Returning" in those functions is just "bailing"
* In the same functions, `version.php` doesn't need to load if `WP_INSTALLING` is defined - the function will immediately bail, the values will never be read, and the globals won't be reset. I have unified the approach in all 3 functions.
* When returning filtered `$locale`, there is no need to set the variable twice.
* In `_maybe_update_core()`, `isset()` can take multiple values to bail before the call to `time()`, if necessary. This is a micro-optimization to prevent PHP from hitting the OS unnecessarily.
See #32444.
Built from https://develop.svn.wordpress.org/trunk@32635
git-svn-id: http://core.svn.wordpress.org/trunk@32605 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2015-05-28 11:29:28 -04:00
* @ global string $wp_version Used to check against the newest WordPress version .
* @ global wpdb $wpdb
* @ global string $wp_local_package
2007-10-30 17:40:30 -04:00
*
2013-10-24 22:29:52 -04:00
* @ param array $extra_stats Extra statistics to report to the WordPress . org API .
Add missing doc blocks to `update.php`:
* `wp_version_check()`, `wp_update_plugins()`, and `wp_update_themes()` do not return meaningful responses, and their responses are never handled by core. As such, they shouldn't alternately return `void` or `false`. "Returning" in those functions is just "bailing"
* In the same functions, `version.php` doesn't need to load if `WP_INSTALLING` is defined - the function will immediately bail, the values will never be read, and the globals won't be reset. I have unified the approach in all 3 functions.
* When returning filtered `$locale`, there is no need to set the variable twice.
* In `_maybe_update_core()`, `isset()` can take multiple values to bail before the call to `time()`, if necessary. This is a micro-optimization to prevent PHP from hitting the OS unnecessarily.
See #32444.
Built from https://develop.svn.wordpress.org/trunk@32635
git-svn-id: http://core.svn.wordpress.org/trunk@32605 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2015-05-28 11:29:28 -04:00
* @ param bool $force_check Whether to bypass the transient cache and force a fresh update check . Defaults to false , true if $extra_stats is set .
2007-10-30 17:40:30 -04:00
*/
2013-11-14 22:04:10 -05:00
function wp_version_check ( $extra_stats = array (), $force_check = false ) {
Use `wp_installing()` instead of `WP_INSTALLING` constant.
The `WP_INSTALLING` constant is a flag that WordPress sets in a number of
places, telling the system that options should be fetched directly from the
database instead of from the cache, that WP should not ping wordpress.org for
updates, that the normal "not installed" checks should be bypassed, and so on.
A constant is generally necessary for this purpose, because the flag is
typically set before the WP bootstrap, meaning that WP functions are not yet
available. However, it is possible - notably, during `wpmu_create_blog()` -
for the "installing" flag to be set after WP has already loaded. In these
cases, `WP_INSTALLING` would be set for the remainder of the process, since
there's no way to change a constant once it's defined. This, in turn, polluted
later function calls that ought to have been outside the scope of site
creation, particularly the non-caching of option data. The problem was
particularly evident in the case of the automated tests, where `WP_INSTALLING`
was set the first time a site was created, and remained set for the rest of the
suite.
The new `wp_installing()` function allows developers to fetch the current
installation status (when called without any arguments) or to set the
installation status (when called with a boolean `true` or `false`). Use of
the `WP_INSTALLING` constant is still supported; `wp_installing()` will default
to `true` if the constant is defined during the bootstrap.
Props boonebgorges, jeremyfelt.
See #31130.
Built from https://develop.svn.wordpress.org/trunk@34828
git-svn-id: http://core.svn.wordpress.org/trunk@34793 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2015-10-05 11:06:28 -04:00
if ( wp_installing () ) {
2007-08-19 00:27:04 -04:00
return ;
Add missing doc blocks to `update.php`:
* `wp_version_check()`, `wp_update_plugins()`, and `wp_update_themes()` do not return meaningful responses, and their responses are never handled by core. As such, they shouldn't alternately return `void` or `false`. "Returning" in those functions is just "bailing"
* In the same functions, `version.php` doesn't need to load if `WP_INSTALLING` is defined - the function will immediately bail, the values will never be read, and the globals won't be reset. I have unified the approach in all 3 functions.
* When returning filtered `$locale`, there is no need to set the variable twice.
* In `_maybe_update_core()`, `isset()` can take multiple values to bail before the call to `time()`, if necessary. This is a micro-optimization to prevent PHP from hitting the OS unnecessarily.
See #32444.
Built from https://develop.svn.wordpress.org/trunk@32635
git-svn-id: http://core.svn.wordpress.org/trunk@32605 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2015-05-28 11:29:28 -04:00
}
2007-08-19 00:27:04 -04:00
2015-12-06 12:39:27 -05:00
global $wpdb , $wp_local_package ;
Add missing doc blocks to `update.php`:
* `wp_version_check()`, `wp_update_plugins()`, and `wp_update_themes()` do not return meaningful responses, and their responses are never handled by core. As such, they shouldn't alternately return `void` or `false`. "Returning" in those functions is just "bailing"
* In the same functions, `version.php` doesn't need to load if `WP_INSTALLING` is defined - the function will immediately bail, the values will never be read, and the globals won't be reset. I have unified the approach in all 3 functions.
* When returning filtered `$locale`, there is no need to set the variable twice.
* In `_maybe_update_core()`, `isset()` can take multiple values to bail before the call to `time()`, if necessary. This is a micro-optimization to prevent PHP from hitting the OS unnecessarily.
See #32444.
Built from https://develop.svn.wordpress.org/trunk@32635
git-svn-id: http://core.svn.wordpress.org/trunk@32605 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2015-05-28 11:29:28 -04:00
// include an unmodified $wp_version
include ( ABSPATH . WPINC . '/version.php' );
2007-08-17 06:33:52 -04:00
$php_version = phpversion ();
2007-09-03 19:19:20 -04:00
2010-01-08 15:49:55 -05:00
$current = get_site_transient ( 'update_core' );
2013-09-30 15:47:12 -04:00
$translations = wp_get_installed_translations ( 'core' );
2013-11-14 21:35:10 -05:00
// Invalidate the transient when $wp_version changes
if ( is_object ( $current ) && $wp_version != $current -> version_checked )
$current = false ;
2009-05-05 17:51:48 -04:00
if ( ! is_object ( $current ) ) {
2008-11-26 07:04:29 -05:00
$current = new stdClass ;
2009-05-05 17:51:48 -04:00
$current -> updates = array ();
$current -> version_checked = $wp_version ;
}
2008-11-26 07:04:29 -05:00
2013-11-14 22:04:10 -05:00
if ( ! empty ( $extra_stats ) )
$force_check = true ;
2012-01-05 14:49:47 -05:00
// Wait 60 seconds between multiple version check requests
$timeout = 60 ;
$time_not_changed = isset ( $current -> last_checked ) && $timeout > ( time () - $current -> last_checked );
Add missing doc blocks to `update.php`:
* `wp_version_check()`, `wp_update_plugins()`, and `wp_update_themes()` do not return meaningful responses, and their responses are never handled by core. As such, they shouldn't alternately return `void` or `false`. "Returning" in those functions is just "bailing"
* In the same functions, `version.php` doesn't need to load if `WP_INSTALLING` is defined - the function will immediately bail, the values will never be read, and the globals won't be reset. I have unified the approach in all 3 functions.
* When returning filtered `$locale`, there is no need to set the variable twice.
* In `_maybe_update_core()`, `isset()` can take multiple values to bail before the call to `time()`, if necessary. This is a micro-optimization to prevent PHP from hitting the OS unnecessarily.
See #32444.
Built from https://develop.svn.wordpress.org/trunk@32635
git-svn-id: http://core.svn.wordpress.org/trunk@32605 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2015-05-28 11:29:28 -04:00
if ( ! $force_check && $time_not_changed ) {
return ;
}
2012-01-05 14:49:47 -05:00
2013-10-06 11:31:09 -04:00
/**
* Filter the locale requested for WordPress core translations .
*
* @ since 2.8 . 0
*
* @ param string $locale Current locale .
*/
Add missing doc blocks to `update.php`:
* `wp_version_check()`, `wp_update_plugins()`, and `wp_update_themes()` do not return meaningful responses, and their responses are never handled by core. As such, they shouldn't alternately return `void` or `false`. "Returning" in those functions is just "bailing"
* In the same functions, `version.php` doesn't need to load if `WP_INSTALLING` is defined - the function will immediately bail, the values will never be read, and the globals won't be reset. I have unified the approach in all 3 functions.
* When returning filtered `$locale`, there is no need to set the variable twice.
* In `_maybe_update_core()`, `isset()` can take multiple values to bail before the call to `time()`, if necessary. This is a micro-optimization to prevent PHP from hitting the OS unnecessarily.
See #32444.
Built from https://develop.svn.wordpress.org/trunk@32635
git-svn-id: http://core.svn.wordpress.org/trunk@32605 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2015-05-28 11:29:28 -04:00
$locale = apply_filters ( 'core_version_check_locale' , get_locale () );
2007-08-17 06:33:52 -04:00
2008-11-26 06:48:05 -05:00
// Update last_checked for current to prevent multiple blocking requests if request hangs
$current -> last_checked = time ();
2010-01-08 15:49:55 -05:00
set_site_transient ( 'update_core' , $current );
2008-11-26 06:48:05 -05:00
2008-08-26 18:30:56 -04:00
if ( method_exists ( $wpdb , 'db_version' ) )
2009-12-09 07:00:55 -05:00
$mysql_version = preg_replace ( '/[^0-9.].*/' , '' , $wpdb -> db_version ());
2008-08-26 18:30:56 -04:00
else
$mysql_version = 'N/A' ;
2010-04-05 16:19:07 -04:00
2013-01-04 05:13:51 -05:00
if ( is_multisite () ) {
$user_count = get_user_count ();
$num_blogs = get_blog_count ();
$wp_install = network_site_url ();
2010-04-05 16:19:07 -04:00
$multisite_enabled = 1 ;
2010-11-29 00:27:01 -05:00
} else {
2013-01-04 05:13:51 -05:00
$user_count = count_users ();
2012-06-25 15:40:16 -04:00
$user_count = $user_count [ 'total_users' ];
2010-11-29 00:27:01 -05:00
$multisite_enabled = 0 ;
$num_blogs = 1 ;
$wp_install = home_url ( '/' );
2010-04-05 16:19:07 -04:00
}
2011-09-17 05:14:27 -04:00
$query = array (
2015-12-06 10:44:27 -05:00
'version' => $wp_version ,
'php' => $php_version ,
'locale' => $locale ,
'mysql' => $mysql_version ,
'local_package' => isset ( $wp_local_package ) ? $wp_local_package : '' ,
'blogs' => $num_blogs ,
'users' => $user_count ,
'multisite_enabled' => $multisite_enabled ,
'initial_db_version' => get_site_option ( 'initial_db_version' ),
2011-09-17 05:14:27 -04:00
);
2013-10-14 19:33:10 -04:00
$post_body = array (
2014-10-28 14:35:19 -04:00
'translations' => wp_json_encode ( $translations ),
2013-10-14 19:33:10 -04:00
);
2013-11-14 22:04:10 -05:00
if ( is_array ( $extra_stats ) )
2013-10-14 19:33:10 -04:00
$post_body = array_merge ( $post_body , $extra_stats );
2013-10-09 21:32:09 -04:00
2013-10-27 17:09:10 -04:00
$url = $http_url = 'http://api.wordpress.org/core/version-check/1.7/?' . http_build_query ( $query , null , '&' );
if ( $ssl = wp_http_supports ( array ( 'ssl' ) ) )
2013-09-02 23:22:10 -04:00
$url = set_url_scheme ( $url , 'https' );
2008-08-01 01:00:07 -04:00
2008-12-21 16:52:15 -05:00
$options = array (
2010-04-05 16:19:07 -04:00
'timeout' => ( ( defined ( 'DOING_CRON' ) && DOING_CRON ) ? 30 : 3 ),
'user-agent' => 'WordPress/' . $wp_version . '; ' . home_url ( '/' ),
'headers' => array (
'wp_install' => $wp_install ,
'wp_blog' => home_url ( '/' )
2013-09-30 15:47:12 -04:00
),
2013-10-14 19:33:10 -04:00
'body' => $post_body ,
2008-12-21 16:52:15 -05:00
);
2008-08-01 01:00:07 -04:00
2013-09-30 15:47:12 -04:00
$response = wp_remote_post ( $url , $options );
2013-10-27 17:09:10 -04:00
if ( $ssl && is_wp_error ( $response ) ) {
2014-04-15 20:38:14 -04:00
trigger_error ( __ ( 'An unexpected error occurred. Something may be wrong with WordPress.org or this server’s configuration. If you continue to have problems, please try the <a href="https://wordpress.org/support/">support forums</a>.' ) . ' ' . __ ( '(WordPress could not establish a secure connection to WordPress.org. Please contact your server administrator.)' ), headers_sent () || WP_DEBUG ? E_USER_WARNING : E_USER_NOTICE );
2013-10-27 17:09:10 -04:00
$response = wp_remote_post ( $http_url , $options );
}
2008-08-12 17:21:11 -04:00
Add missing doc blocks to `update.php`:
* `wp_version_check()`, `wp_update_plugins()`, and `wp_update_themes()` do not return meaningful responses, and their responses are never handled by core. As such, they shouldn't alternately return `void` or `false`. "Returning" in those functions is just "bailing"
* In the same functions, `version.php` doesn't need to load if `WP_INSTALLING` is defined - the function will immediately bail, the values will never be read, and the globals won't be reset. I have unified the approach in all 3 functions.
* When returning filtered `$locale`, there is no need to set the variable twice.
* In `_maybe_update_core()`, `isset()` can take multiple values to bail before the call to `time()`, if necessary. This is a micro-optimization to prevent PHP from hitting the OS unnecessarily.
See #32444.
Built from https://develop.svn.wordpress.org/trunk@32635
git-svn-id: http://core.svn.wordpress.org/trunk@32605 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2015-05-28 11:29:28 -04:00
if ( is_wp_error ( $response ) || 200 != wp_remote_retrieve_response_code ( $response ) ) {
return ;
}
2008-08-01 01:00:07 -04:00
2011-05-14 15:45:07 -04:00
$body = trim ( wp_remote_retrieve_body ( $response ) );
2013-09-02 23:22:10 -04:00
$body = json_decode ( $body , true );
2012-01-07 22:48:05 -05:00
Add missing doc blocks to `update.php`:
* `wp_version_check()`, `wp_update_plugins()`, and `wp_update_themes()` do not return meaningful responses, and their responses are never handled by core. As such, they shouldn't alternately return `void` or `false`. "Returning" in those functions is just "bailing"
* In the same functions, `version.php` doesn't need to load if `WP_INSTALLING` is defined - the function will immediately bail, the values will never be read, and the globals won't be reset. I have unified the approach in all 3 functions.
* When returning filtered `$locale`, there is no need to set the variable twice.
* In `_maybe_update_core()`, `isset()` can take multiple values to bail before the call to `time()`, if necessary. This is a micro-optimization to prevent PHP from hitting the OS unnecessarily.
See #32444.
Built from https://develop.svn.wordpress.org/trunk@32635
git-svn-id: http://core.svn.wordpress.org/trunk@32605 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2015-05-28 11:29:28 -04:00
if ( ! is_array ( $body ) || ! isset ( $body [ 'offers' ] ) ) {
return ;
}
2012-01-07 22:48:05 -05:00
2011-06-10 01:47:44 -04:00
$offers = $body [ 'offers' ];
foreach ( $offers as & $offer ) {
foreach ( $offer as $offer_key => $value ) {
if ( 'packages' == $offer_key )
2011-06-10 01:50:23 -04:00
$offer [ 'packages' ] = ( object ) array_intersect_key ( array_map ( 'esc_url' , $offer [ 'packages' ] ),
2013-09-29 20:21:09 -04:00
array_fill_keys ( array ( 'full' , 'no_content' , 'new_bundled' , 'partial' , 'rollback' ), '' ) );
2011-06-10 01:47:44 -04:00
elseif ( 'download' == $offer_key )
$offer [ 'download' ] = esc_url ( $value );
else
$offer [ $offer_key ] = esc_html ( $value );
}
2011-06-10 02:22:33 -04:00
$offer = ( object ) array_intersect_key ( $offer , array_fill_keys ( array ( 'response' , 'download' , 'locale' ,
2014-11-19 00:40:23 -05:00
'packages' , 'current' , 'version' , 'php_version' , 'mysql_version' , 'new_bundled' , 'partial_version' , 'notify_email' , 'support_email' , 'new_files' ), '' ) );
2008-10-31 14:51:06 -04:00
}
2008-11-04 12:12:03 -05:00
$updates = new stdClass ();
2011-06-10 01:47:44 -04:00
$updates -> updates = $offers ;
2008-11-04 12:12:03 -05:00
$updates -> last_checked = time ();
$updates -> version_checked = $wp_version ;
2013-09-30 15:47:12 -04:00
if ( isset ( $body [ 'translations' ] ) )
$updates -> translations = $body [ 'translations' ];
2014-04-14 22:23:16 -04:00
set_site_transient ( 'update_core' , $updates );
if ( ! empty ( $body [ 'ttl' ] ) ) {
$ttl = ( int ) $body [ 'ttl' ];
if ( $ttl && ( time () + $ttl < wp_next_scheduled ( 'wp_version_check' ) ) ) {
// Queue an event to re-run the update check in $ttl seconds.
wp_schedule_single_event ( time () + $ttl , 'wp_version_check' );
}
}
// Trigger a background updates check if running non-interactively, and we weren't called from the update handler.
if ( defined ( 'DOING_CRON' ) && DOING_CRON && ! doing_action ( 'wp_maybe_auto_update' ) ) {
do_action ( 'wp_maybe_auto_update' );
}
2007-08-17 06:33:52 -04:00
}
2008-07-11 18:04:03 -04:00
/**
2008-08-12 17:21:11 -04:00
* Check plugin versions against the latest versions hosted on WordPress . org .
2008-07-11 18:04:03 -04:00
*
2008-08-12 17:21:11 -04:00
* The WordPress version , PHP version , and Locale is sent along with a list of
* all plugins installed . Checks against the WordPress server at
2008-09-18 13:32:18 -04:00
* api . wordpress . org . Will only check if WordPress isn ' t installing .
2008-07-11 18:04:03 -04:00
*
2008-08-27 02:45:13 -04:00
* @ since 2.3 . 0
Add missing doc blocks to `update.php`:
* `wp_version_check()`, `wp_update_plugins()`, and `wp_update_themes()` do not return meaningful responses, and their responses are never handled by core. As such, they shouldn't alternately return `void` or `false`. "Returning" in those functions is just "bailing"
* In the same functions, `version.php` doesn't need to load if `WP_INSTALLING` is defined - the function will immediately bail, the values will never be read, and the globals won't be reset. I have unified the approach in all 3 functions.
* When returning filtered `$locale`, there is no need to set the variable twice.
* In `_maybe_update_core()`, `isset()` can take multiple values to bail before the call to `time()`, if necessary. This is a micro-optimization to prevent PHP from hitting the OS unnecessarily.
See #32444.
Built from https://develop.svn.wordpress.org/trunk@32635
git-svn-id: http://core.svn.wordpress.org/trunk@32605 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2015-05-28 11:29:28 -04:00
* @ global string $wp_version Used to notify the WordPress version .
2008-07-11 18:04:03 -04:00
*
2014-04-02 09:05:15 -04:00
* @ param array $extra_stats Extra statistics to report to the WordPress . org API .
2008-07-11 18:04:03 -04:00
*/
2014-04-02 09:05:15 -04:00
function wp_update_plugins ( $extra_stats = array () ) {
Use `wp_installing()` instead of `WP_INSTALLING` constant.
The `WP_INSTALLING` constant is a flag that WordPress sets in a number of
places, telling the system that options should be fetched directly from the
database instead of from the cache, that WP should not ping wordpress.org for
updates, that the normal "not installed" checks should be bypassed, and so on.
A constant is generally necessary for this purpose, because the flag is
typically set before the WP bootstrap, meaning that WP functions are not yet
available. However, it is possible - notably, during `wpmu_create_blog()` -
for the "installing" flag to be set after WP has already loaded. In these
cases, `WP_INSTALLING` would be set for the remainder of the process, since
there's no way to change a constant once it's defined. This, in turn, polluted
later function calls that ought to have been outside the scope of site
creation, particularly the non-caching of option data. The problem was
particularly evident in the case of the automated tests, where `WP_INSTALLING`
was set the first time a site was created, and remained set for the rest of the
suite.
The new `wp_installing()` function allows developers to fetch the current
installation status (when called without any arguments) or to set the
installation status (when called with a boolean `true` or `false`). Use of
the `WP_INSTALLING` constant is still supported; `wp_installing()` will default
to `true` if the constant is defined during the bootstrap.
Props boonebgorges, jeremyfelt.
See #31130.
Built from https://develop.svn.wordpress.org/trunk@34828
git-svn-id: http://core.svn.wordpress.org/trunk@34793 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2015-10-05 11:06:28 -04:00
if ( wp_installing () ) {
Add missing doc blocks to `update.php`:
* `wp_version_check()`, `wp_update_plugins()`, and `wp_update_themes()` do not return meaningful responses, and their responses are never handled by core. As such, they shouldn't alternately return `void` or `false`. "Returning" in those functions is just "bailing"
* In the same functions, `version.php` doesn't need to load if `WP_INSTALLING` is defined - the function will immediately bail, the values will never be read, and the globals won't be reset. I have unified the approach in all 3 functions.
* When returning filtered `$locale`, there is no need to set the variable twice.
* In `_maybe_update_core()`, `isset()` can take multiple values to bail before the call to `time()`, if necessary. This is a micro-optimization to prevent PHP from hitting the OS unnecessarily.
See #32444.
Built from https://develop.svn.wordpress.org/trunk@32635
git-svn-id: http://core.svn.wordpress.org/trunk@32605 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2015-05-28 11:29:28 -04:00
return ;
}
2008-07-11 18:04:03 -04:00
Add missing doc blocks to `update.php`:
* `wp_version_check()`, `wp_update_plugins()`, and `wp_update_themes()` do not return meaningful responses, and their responses are never handled by core. As such, they shouldn't alternately return `void` or `false`. "Returning" in those functions is just "bailing"
* In the same functions, `version.php` doesn't need to load if `WP_INSTALLING` is defined - the function will immediately bail, the values will never be read, and the globals won't be reset. I have unified the approach in all 3 functions.
* When returning filtered `$locale`, there is no need to set the variable twice.
* In `_maybe_update_core()`, `isset()` can take multiple values to bail before the call to `time()`, if necessary. This is a micro-optimization to prevent PHP from hitting the OS unnecessarily.
See #32444.
Built from https://develop.svn.wordpress.org/trunk@32635
git-svn-id: http://core.svn.wordpress.org/trunk@32605 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2015-05-28 11:29:28 -04:00
// include an unmodified $wp_version
include ( ABSPATH . WPINC . '/version.php' );
2008-07-11 18:04:03 -04:00
// If running blog-side, bail unless we've not checked in the last 12 hours
2008-08-01 00:26:32 -04:00
if ( ! function_exists ( 'get_plugins' ) )
2008-07-11 18:04:03 -04:00
require_once ( ABSPATH . 'wp-admin/includes/plugin.php' );
$plugins = get_plugins ();
2013-09-21 00:08:10 -04:00
$translations = wp_get_installed_translations ( 'plugins' );
2013-09-20 15:13:09 -04:00
2010-01-26 13:39:12 -05:00
$active = get_option ( 'active_plugins' , array () );
2010-01-08 15:49:55 -05:00
$current = get_site_transient ( 'update_plugins' );
2008-11-26 07:04:29 -05:00
if ( ! is_object ( $current ) )
$current = new stdClass ;
2008-07-11 18:04:03 -04:00
2008-12-18 12:23:20 -05:00
$new_option = new stdClass ;
2008-07-11 18:04:03 -04:00
$new_option -> last_checked = time ();
2012-01-05 14:49:47 -05:00
// Check for update on a different schedule, depending on the page.
switch ( current_filter () ) {
2013-09-22 22:08:10 -04:00
case 'upgrader_process_complete' :
$timeout = 0 ;
break ;
2012-01-05 14:49:47 -05:00
case 'load-update-core.php' :
2012-09-25 01:26:19 -04:00
$timeout = MINUTE_IN_SECONDS ;
2012-01-05 14:49:47 -05:00
break ;
case 'load-plugins.php' :
case 'load-update.php' :
2012-09-25 01:26:19 -04:00
$timeout = HOUR_IN_SECONDS ;
2012-01-05 14:49:47 -05:00
break ;
default :
2014-04-14 22:23:16 -04:00
if ( defined ( 'DOING_CRON' ) && DOING_CRON ) {
$timeout = 0 ;
} else {
$timeout = 12 * HOUR_IN_SECONDS ;
}
2011-11-16 02:23:15 -05:00
}
2012-02-27 14:46:52 -05:00
2012-01-05 14:49:47 -05:00
$time_not_changed = isset ( $current -> last_checked ) && $timeout > ( time () - $current -> last_checked );
2011-11-15 20:58:13 -05:00
2014-04-02 09:05:15 -04:00
if ( $time_not_changed && ! $extra_stats ) {
2012-01-05 14:49:47 -05:00
$plugin_changed = false ;
foreach ( $plugins as $file => $p ) {
$new_option -> checked [ $file ] = $p [ 'Version' ];
if ( ! isset ( $current -> checked [ $file ] ) || strval ( $current -> checked [ $file ]) !== strval ( $p [ 'Version' ]) )
2011-11-16 02:23:15 -05:00
$plugin_changed = true ;
2012-01-05 14:49:47 -05:00
}
if ( isset ( $current -> response ) && is_array ( $current -> response ) ) {
foreach ( $current -> response as $plugin_file => $update_details ) {
if ( ! isset ( $plugins [ $plugin_file ]) ) {
$plugin_changed = true ;
break ;
}
2011-11-16 02:23:15 -05:00
}
2008-07-16 17:53:32 -04:00
}
2012-01-05 14:49:47 -05:00
// Bail if we've checked recently and if nothing has changed
Add missing doc blocks to `update.php`:
* `wp_version_check()`, `wp_update_plugins()`, and `wp_update_themes()` do not return meaningful responses, and their responses are never handled by core. As such, they shouldn't alternately return `void` or `false`. "Returning" in those functions is just "bailing"
* In the same functions, `version.php` doesn't need to load if `WP_INSTALLING` is defined - the function will immediately bail, the values will never be read, and the globals won't be reset. I have unified the approach in all 3 functions.
* When returning filtered `$locale`, there is no need to set the variable twice.
* In `_maybe_update_core()`, `isset()` can take multiple values to bail before the call to `time()`, if necessary. This is a micro-optimization to prevent PHP from hitting the OS unnecessarily.
See #32444.
Built from https://develop.svn.wordpress.org/trunk@32635
git-svn-id: http://core.svn.wordpress.org/trunk@32605 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2015-05-28 11:29:28 -04:00
if ( ! $plugin_changed ) {
return ;
}
2012-01-05 14:49:47 -05:00
}
2011-11-16 02:23:15 -05:00
2008-11-26 06:48:05 -05:00
// Update last_checked for current to prevent multiple blocking requests if request hangs
$current -> last_checked = time ();
2010-01-08 15:49:55 -05:00
set_site_transient ( 'update_plugins' , $current );
2008-11-26 06:48:05 -05:00
2013-09-20 01:55:09 -04:00
$to_send = compact ( 'plugins' , 'active' );
2008-07-11 18:04:03 -04:00
2013-09-28 00:18:12 -04:00
/**
* Filter the locales requested for plugin translations .
*
* @ since 3.7 . 0
*
2013-10-06 11:31:09 -04:00
* @ param array $locales Plugin locale . Default is current locale of the site .
2013-09-28 00:18:12 -04:00
*/
Add missing doc blocks to `update.php`:
* `wp_version_check()`, `wp_update_plugins()`, and `wp_update_themes()` do not return meaningful responses, and their responses are never handled by core. As such, they shouldn't alternately return `void` or `false`. "Returning" in those functions is just "bailing"
* In the same functions, `version.php` doesn't need to load if `WP_INSTALLING` is defined - the function will immediately bail, the values will never be read, and the globals won't be reset. I have unified the approach in all 3 functions.
* When returning filtered `$locale`, there is no need to set the variable twice.
* In `_maybe_update_core()`, `isset()` can take multiple values to bail before the call to `time()`, if necessary. This is a micro-optimization to prevent PHP from hitting the OS unnecessarily.
See #32444.
Built from https://develop.svn.wordpress.org/trunk@32635
git-svn-id: http://core.svn.wordpress.org/trunk@32605 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2015-05-28 11:29:28 -04:00
$locales = apply_filters ( 'plugins_update_check_locales' , array ( get_locale () ) );
2013-09-28 00:18:12 -04:00
2014-06-19 19:21:16 -04:00
if ( defined ( 'DOING_CRON' ) && DOING_CRON ) {
$timeout = 30 ;
} else {
2014-06-23 10:31:14 -04:00
// Three seconds, plus one extra second for every 10 plugins
2014-06-24 12:06:14 -04:00
$timeout = 3 + ( int ) ( count ( $plugins ) / 10 );
2014-06-19 19:21:16 -04:00
}
2008-12-21 16:52:15 -05:00
$options = array (
2014-06-19 19:21:16 -04:00
'timeout' => $timeout ,
2013-09-21 00:08:10 -04:00
'body' => array (
2014-10-28 14:35:19 -04:00
'plugins' => wp_json_encode ( $to_send ),
'translations' => wp_json_encode ( $translations ),
'locale' => wp_json_encode ( $locales ),
'all' => wp_json_encode ( true ),
2013-09-21 00:08:10 -04:00
),
2008-12-21 16:52:15 -05:00
'user-agent' => 'WordPress/' . $wp_version . '; ' . get_bloginfo ( 'url' )
);
2008-08-12 17:21:11 -04:00
2014-04-02 09:13:15 -04:00
if ( $extra_stats ) {
2014-10-28 14:35:19 -04:00
$options [ 'body' ][ 'update_stats' ] = wp_json_encode ( $extra_stats );
2014-04-02 09:05:15 -04:00
}
2013-10-27 17:09:10 -04:00
$url = $http_url = 'http://api.wordpress.org/plugins/update-check/1.1/' ;
if ( $ssl = wp_http_supports ( array ( 'ssl' ) ) )
2013-09-09 03:54:11 -04:00
$url = set_url_scheme ( $url , 'https' );
$raw_response = wp_remote_post ( $url , $options );
2013-10-27 17:09:10 -04:00
if ( $ssl && is_wp_error ( $raw_response ) ) {
2014-04-15 20:38:14 -04:00
trigger_error ( __ ( 'An unexpected error occurred. Something may be wrong with WordPress.org or this server’s configuration. If you continue to have problems, please try the <a href="https://wordpress.org/support/">support forums</a>.' ) . ' ' . __ ( '(WordPress could not establish a secure connection to WordPress.org. Please contact your server administrator.)' ), headers_sent () || WP_DEBUG ? E_USER_WARNING : E_USER_NOTICE );
2013-10-27 17:09:10 -04:00
$raw_response = wp_remote_post ( $http_url , $options );
}
2008-08-12 17:21:11 -04:00
Add missing doc blocks to `update.php`:
* `wp_version_check()`, `wp_update_plugins()`, and `wp_update_themes()` do not return meaningful responses, and their responses are never handled by core. As such, they shouldn't alternately return `void` or `false`. "Returning" in those functions is just "bailing"
* In the same functions, `version.php` doesn't need to load if `WP_INSTALLING` is defined - the function will immediately bail, the values will never be read, and the globals won't be reset. I have unified the approach in all 3 functions.
* When returning filtered `$locale`, there is no need to set the variable twice.
* In `_maybe_update_core()`, `isset()` can take multiple values to bail before the call to `time()`, if necessary. This is a micro-optimization to prevent PHP from hitting the OS unnecessarily.
See #32444.
Built from https://develop.svn.wordpress.org/trunk@32635
git-svn-id: http://core.svn.wordpress.org/trunk@32605 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2015-05-28 11:29:28 -04:00
if ( is_wp_error ( $raw_response ) || 200 != wp_remote_retrieve_response_code ( $raw_response ) ) {
return ;
}
2008-07-11 18:04:03 -04:00
2013-09-21 00:08:10 -04:00
$response = json_decode ( wp_remote_retrieve_body ( $raw_response ), true );
foreach ( $response [ 'plugins' ] as & $plugin ) {
$plugin = ( object ) $plugin ;
}
unset ( $plugin );
2014-07-18 16:49:17 -04:00
foreach ( $response [ 'no_update' ] as & $plugin ) {
$plugin = ( object ) $plugin ;
}
unset ( $plugin );
2008-07-11 18:04:03 -04:00
2013-09-21 00:08:10 -04:00
if ( is_array ( $response ) ) {
$new_option -> response = $response [ 'plugins' ];
$new_option -> translations = $response [ 'translations' ];
2014-07-18 16:49:17 -04:00
// TODO: Perhaps better to store no_update in a separate transient with an expiry?
$new_option -> no_update = $response [ 'no_update' ];
2013-09-21 00:08:10 -04:00
} else {
2008-10-24 06:55:20 -04:00
$new_option -> response = array ();
2013-09-21 05:34:09 -04:00
$new_option -> translations = array ();
2014-07-18 16:49:17 -04:00
$new_option -> no_update = array ();
2013-09-21 00:08:10 -04:00
}
2008-07-11 18:04:03 -04:00
2010-01-08 15:49:55 -05:00
set_site_transient ( 'update_plugins' , $new_option );
2008-07-11 18:04:03 -04:00
}
2008-08-01 00:26:32 -04:00
2008-09-15 12:21:15 -04:00
/**
* Check theme versions against the latest versions hosted on WordPress . org .
*
2008-12-09 13:03:31 -05:00
* A list of all themes installed in sent to WP . Checks against the
2008-09-18 13:32:18 -04:00
* WordPress server at api . wordpress . org . Will only check if WordPress isn ' t
* installing .
2008-09-15 12:21:15 -04:00
*
* @ since 2.7 . 0
2011-01-06 04:06:55 -05:00
* @ uses $wp_version Used to notify the WordPress version .
2008-09-15 12:21:15 -04:00
*
2014-04-02 09:05:15 -04:00
* @ param array $extra_stats Extra statistics to report to the WordPress . org API .
2008-09-15 12:21:15 -04:00
*/
2014-04-02 09:05:15 -04:00
function wp_update_themes ( $extra_stats = array () ) {
Use `wp_installing()` instead of `WP_INSTALLING` constant.
The `WP_INSTALLING` constant is a flag that WordPress sets in a number of
places, telling the system that options should be fetched directly from the
database instead of from the cache, that WP should not ping wordpress.org for
updates, that the normal "not installed" checks should be bypassed, and so on.
A constant is generally necessary for this purpose, because the flag is
typically set before the WP bootstrap, meaning that WP functions are not yet
available. However, it is possible - notably, during `wpmu_create_blog()` -
for the "installing" flag to be set after WP has already loaded. In these
cases, `WP_INSTALLING` would be set for the remainder of the process, since
there's no way to change a constant once it's defined. This, in turn, polluted
later function calls that ought to have been outside the scope of site
creation, particularly the non-caching of option data. The problem was
particularly evident in the case of the automated tests, where `WP_INSTALLING`
was set the first time a site was created, and remained set for the rest of the
suite.
The new `wp_installing()` function allows developers to fetch the current
installation status (when called without any arguments) or to set the
installation status (when called with a boolean `true` or `false`). Use of
the `WP_INSTALLING` constant is still supported; `wp_installing()` will default
to `true` if the constant is defined during the bootstrap.
Props boonebgorges, jeremyfelt.
See #31130.
Built from https://develop.svn.wordpress.org/trunk@34828
git-svn-id: http://core.svn.wordpress.org/trunk@34793 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2015-10-05 11:06:28 -04:00
if ( wp_installing () ) {
Add missing doc blocks to `update.php`:
* `wp_version_check()`, `wp_update_plugins()`, and `wp_update_themes()` do not return meaningful responses, and their responses are never handled by core. As such, they shouldn't alternately return `void` or `false`. "Returning" in those functions is just "bailing"
* In the same functions, `version.php` doesn't need to load if `WP_INSTALLING` is defined - the function will immediately bail, the values will never be read, and the globals won't be reset. I have unified the approach in all 3 functions.
* When returning filtered `$locale`, there is no need to set the variable twice.
* In `_maybe_update_core()`, `isset()` can take multiple values to bail before the call to `time()`, if necessary. This is a micro-optimization to prevent PHP from hitting the OS unnecessarily.
See #32444.
Built from https://develop.svn.wordpress.org/trunk@32635
git-svn-id: http://core.svn.wordpress.org/trunk@32605 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2015-05-28 11:29:28 -04:00
return ;
}
2015-12-06 12:39:27 -05:00
Add missing doc blocks to `update.php`:
* `wp_version_check()`, `wp_update_plugins()`, and `wp_update_themes()` do not return meaningful responses, and their responses are never handled by core. As such, they shouldn't alternately return `void` or `false`. "Returning" in those functions is just "bailing"
* In the same functions, `version.php` doesn't need to load if `WP_INSTALLING` is defined - the function will immediately bail, the values will never be read, and the globals won't be reset. I have unified the approach in all 3 functions.
* When returning filtered `$locale`, there is no need to set the variable twice.
* In `_maybe_update_core()`, `isset()` can take multiple values to bail before the call to `time()`, if necessary. This is a micro-optimization to prevent PHP from hitting the OS unnecessarily.
See #32444.
Built from https://develop.svn.wordpress.org/trunk@32635
git-svn-id: http://core.svn.wordpress.org/trunk@32605 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2015-05-28 11:29:28 -04:00
// include an unmodified $wp_version
include ( ABSPATH . WPINC . '/version.php' );
2008-09-15 12:21:15 -04:00
Introduce WP_Theme, wp_get_themes(), and wp_get_theme() to replace get_themes(), get_theme(), get_theme_data(), current_theme_info(), and others.
* Getters and Helpers: Introduces a series of methods to allow for easy generation of headers for display, and other theme metadata, including page templates.
* Screenshots: Handles support for multiple screenshots. (see # Additional screenshots must be PNG and start with screenshot-2.png, and be sequential to be counted. see #19816.
* Error Handling: Broken themes have a WP_Error object attached to them.
* Caching: Introduces a wp_cache_themes_persistently filter (also in [20020]) to enable persistent caching of all filesystem and sanitization operations normally handled by WP_Theme (and formerly get_file_data() and get_themes()). Themes are cached individually and across five different cache keys for different data pieces.
* Compatibility: A WP_Theme object is backwards compatible with a theme's array formerly returned by get_themes() and get_theme(), and an stdClass object formerly returned by current_theme_info().
* i18n/L10n: Theme headers are now localizable with proper Text Domain and Domain Path headers, like plugins. (Language packs may remove the requirement for headers.) For page templates, see #6007 (not fixed yet, but will be easy now). For headers, fixes #15858.
* PHP and CSS files: New methods that fetch a list of theme files (for the theme editor) only on demand, rather than only loading them into memory. fixes #11214.
Functions deprecated:
* get_themes(), get_allowed_themes() and get_broken_themes() -- use wp_get_themes()
* get_theme() and current_theme_info() -- use wp_get_theme()
* get_site_allowed_themes() -- use WP_Theme::get_allowed_on_network()
* wpmu_get_blog_allowedthemes() -- use WP_theme::get_allowed_on_site()
see also [20016], [20018], [20019], [20020], [20021], [20022], [20025], [20026], [20027]. also fixes #19244.
see #20103.
git-svn-id: http://svn.automattic.com/wordpress/trunk@20029 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2012-02-28 16:24:44 -05:00
$installed_themes = wp_get_themes ();
2013-09-21 00:08:10 -04:00
$translations = wp_get_installed_translations ( 'themes' );
2013-09-20 15:13:09 -04:00
2010-07-22 09:24:41 -04:00
$last_update = get_site_transient ( 'update_themes' );
if ( ! is_object ( $last_update ) )
$last_update = new stdClass ;
2008-09-15 12:21:15 -04:00
2013-09-20 01:55:09 -04:00
$themes = $checked = $request = array ();
2010-07-22 09:24:41 -04:00
// Put slug of current theme into request.
2013-09-20 01:55:09 -04:00
$request [ 'active' ] = get_option ( 'stylesheet' );
2010-07-22 09:24:41 -04:00
Introduce WP_Theme, wp_get_themes(), and wp_get_theme() to replace get_themes(), get_theme(), get_theme_data(), current_theme_info(), and others.
* Getters and Helpers: Introduces a series of methods to allow for easy generation of headers for display, and other theme metadata, including page templates.
* Screenshots: Handles support for multiple screenshots. (see # Additional screenshots must be PNG and start with screenshot-2.png, and be sequential to be counted. see #19816.
* Error Handling: Broken themes have a WP_Error object attached to them.
* Caching: Introduces a wp_cache_themes_persistently filter (also in [20020]) to enable persistent caching of all filesystem and sanitization operations normally handled by WP_Theme (and formerly get_file_data() and get_themes()). Themes are cached individually and across five different cache keys for different data pieces.
* Compatibility: A WP_Theme object is backwards compatible with a theme's array formerly returned by get_themes() and get_theme(), and an stdClass object formerly returned by current_theme_info().
* i18n/L10n: Theme headers are now localizable with proper Text Domain and Domain Path headers, like plugins. (Language packs may remove the requirement for headers.) For page templates, see #6007 (not fixed yet, but will be easy now). For headers, fixes #15858.
* PHP and CSS files: New methods that fetch a list of theme files (for the theme editor) only on demand, rather than only loading them into memory. fixes #11214.
Functions deprecated:
* get_themes(), get_allowed_themes() and get_broken_themes() -- use wp_get_themes()
* get_theme() and current_theme_info() -- use wp_get_theme()
* get_site_allowed_themes() -- use WP_Theme::get_allowed_on_network()
* wpmu_get_blog_allowedthemes() -- use WP_theme::get_allowed_on_site()
see also [20016], [20018], [20019], [20020], [20021], [20022], [20025], [20026], [20027]. also fixes #19244.
see #20103.
git-svn-id: http://svn.automattic.com/wordpress/trunk@20029 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2012-02-28 16:24:44 -05:00
foreach ( $installed_themes as $theme ) {
$checked [ $theme -> get_stylesheet () ] = $theme -> get ( 'Version' );
$themes [ $theme -> get_stylesheet () ] = array (
'Name' => $theme -> get ( 'Name' ),
'Title' => $theme -> get ( 'Name' ),
'Version' => $theme -> get ( 'Version' ),
'Author' => $theme -> get ( 'Author' ),
'Author URI' => $theme -> get ( 'AuthorURI' ),
'Template' => $theme -> get_template (),
'Stylesheet' => $theme -> get_stylesheet (),
);
2008-09-15 12:21:15 -04:00
}
2012-01-05 14:49:47 -05:00
// Check for update on a different schedule, depending on the page.
switch ( current_filter () ) {
2013-09-22 22:08:10 -04:00
case 'upgrader_process_complete' :
$timeout = 0 ;
break ;
2012-01-05 14:49:47 -05:00
case 'load-update-core.php' :
2012-09-25 01:26:19 -04:00
$timeout = MINUTE_IN_SECONDS ;
2012-01-05 14:49:47 -05:00
break ;
2012-03-24 10:07:12 -04:00
case 'load-themes.php' :
2012-01-05 14:49:47 -05:00
case 'load-update.php' :
2012-09-25 01:26:19 -04:00
$timeout = HOUR_IN_SECONDS ;
2012-01-05 14:49:47 -05:00
break ;
default :
2014-04-14 22:23:16 -04:00
if ( defined ( 'DOING_CRON' ) && DOING_CRON ) {
$timeout = 0 ;
} else {
$timeout = 12 * HOUR_IN_SECONDS ;
}
2011-11-16 02:23:15 -05:00
}
2012-02-27 14:46:52 -05:00
2013-01-04 05:13:51 -05:00
$time_not_changed = isset ( $last_update -> last_checked ) && $timeout > ( time () - $last_update -> last_checked );
2012-01-05 14:49:47 -05:00
2014-04-02 09:05:15 -04:00
if ( $time_not_changed && ! $extra_stats ) {
2012-01-05 14:49:47 -05:00
$theme_changed = false ;
foreach ( $checked as $slug => $v ) {
if ( ! isset ( $last_update -> checked [ $slug ] ) || strval ( $last_update -> checked [ $slug ]) !== strval ( $v ) )
2011-11-16 02:23:15 -05:00
$theme_changed = true ;
2012-01-05 14:49:47 -05:00
}
if ( isset ( $last_update -> response ) && is_array ( $last_update -> response ) ) {
foreach ( $last_update -> response as $slug => $update_details ) {
if ( ! isset ( $checked [ $slug ]) ) {
$theme_changed = true ;
break ;
}
2011-11-16 02:23:15 -05:00
}
2009-07-14 04:34:39 -04:00
}
2012-01-05 14:49:47 -05:00
// Bail if we've checked recently and if nothing has changed
Add missing doc blocks to `update.php`:
* `wp_version_check()`, `wp_update_plugins()`, and `wp_update_themes()` do not return meaningful responses, and their responses are never handled by core. As such, they shouldn't alternately return `void` or `false`. "Returning" in those functions is just "bailing"
* In the same functions, `version.php` doesn't need to load if `WP_INSTALLING` is defined - the function will immediately bail, the values will never be read, and the globals won't be reset. I have unified the approach in all 3 functions.
* When returning filtered `$locale`, there is no need to set the variable twice.
* In `_maybe_update_core()`, `isset()` can take multiple values to bail before the call to `time()`, if necessary. This is a micro-optimization to prevent PHP from hitting the OS unnecessarily.
See #32444.
Built from https://develop.svn.wordpress.org/trunk@32635
git-svn-id: http://core.svn.wordpress.org/trunk@32605 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2015-05-28 11:29:28 -04:00
if ( ! $theme_changed ) {
return ;
}
2012-01-05 14:49:47 -05:00
}
2011-11-16 02:23:15 -05:00
2009-07-14 04:34:39 -04:00
// Update last_checked for current to prevent multiple blocking requests if request hangs
2010-07-22 09:24:41 -04:00
$last_update -> last_checked = time ();
set_site_transient ( 'update_themes' , $last_update );
2009-07-14 04:34:39 -04:00
2013-09-20 01:55:09 -04:00
$request [ 'themes' ] = $themes ;
2013-09-28 00:18:12 -04:00
/**
* Filter the locales requested for theme translations .
*
* @ since 3.7 . 0
*
2013-10-06 11:31:09 -04:00
* @ param array $locales Theme locale . Default is current locale of the site .
2013-09-28 00:18:12 -04:00
*/
Add missing doc blocks to `update.php`:
* `wp_version_check()`, `wp_update_plugins()`, and `wp_update_themes()` do not return meaningful responses, and their responses are never handled by core. As such, they shouldn't alternately return `void` or `false`. "Returning" in those functions is just "bailing"
* In the same functions, `version.php` doesn't need to load if `WP_INSTALLING` is defined - the function will immediately bail, the values will never be read, and the globals won't be reset. I have unified the approach in all 3 functions.
* When returning filtered `$locale`, there is no need to set the variable twice.
* In `_maybe_update_core()`, `isset()` can take multiple values to bail before the call to `time()`, if necessary. This is a micro-optimization to prevent PHP from hitting the OS unnecessarily.
See #32444.
Built from https://develop.svn.wordpress.org/trunk@32635
git-svn-id: http://core.svn.wordpress.org/trunk@32605 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2015-05-28 11:29:28 -04:00
$locales = apply_filters ( 'themes_update_check_locales' , array ( get_locale () ) );
2013-09-28 00:18:12 -04:00
2014-06-19 19:21:16 -04:00
if ( defined ( 'DOING_CRON' ) && DOING_CRON ) {
$timeout = 30 ;
} else {
2014-06-23 10:31:14 -04:00
// Three seconds, plus one extra second for every 10 themes
2014-06-24 12:06:14 -04:00
$timeout = 3 + ( int ) ( count ( $themes ) / 10 );
2014-06-19 19:21:16 -04:00
}
2008-09-15 12:21:15 -04:00
$options = array (
2014-06-19 19:21:16 -04:00
'timeout' => $timeout ,
2013-09-21 00:08:10 -04:00
'body' => array (
2014-10-28 14:35:19 -04:00
'themes' => wp_json_encode ( $request ),
'translations' => wp_json_encode ( $translations ),
'locale' => wp_json_encode ( $locales ),
2013-09-21 00:08:10 -04:00
),
2008-12-21 16:52:15 -05:00
'user-agent' => 'WordPress/' . $wp_version . '; ' . get_bloginfo ( 'url' )
2008-09-15 12:21:15 -04:00
);
2014-04-02 09:13:15 -04:00
if ( $extra_stats ) {
2014-10-28 14:35:19 -04:00
$options [ 'body' ][ 'update_stats' ] = wp_json_encode ( $extra_stats );
2014-04-02 09:05:15 -04:00
}
2013-10-27 17:09:10 -04:00
$url = $http_url = 'http://api.wordpress.org/themes/update-check/1.1/' ;
if ( $ssl = wp_http_supports ( array ( 'ssl' ) ) )
2013-09-09 03:54:11 -04:00
$url = set_url_scheme ( $url , 'https' );
$raw_response = wp_remote_post ( $url , $options );
2013-10-27 17:09:10 -04:00
if ( $ssl && is_wp_error ( $raw_response ) ) {
2014-04-15 20:38:14 -04:00
trigger_error ( __ ( 'An unexpected error occurred. Something may be wrong with WordPress.org or this server’s configuration. If you continue to have problems, please try the <a href="https://wordpress.org/support/">support forums</a>.' ) . ' ' . __ ( '(WordPress could not establish a secure connection to WordPress.org. Please contact your server administrator.)' ), headers_sent () || WP_DEBUG ? E_USER_WARNING : E_USER_NOTICE );
2013-10-27 17:09:10 -04:00
$raw_response = wp_remote_post ( $http_url , $options );
}
2008-09-15 12:21:15 -04:00
Add missing doc blocks to `update.php`:
* `wp_version_check()`, `wp_update_plugins()`, and `wp_update_themes()` do not return meaningful responses, and their responses are never handled by core. As such, they shouldn't alternately return `void` or `false`. "Returning" in those functions is just "bailing"
* In the same functions, `version.php` doesn't need to load if `WP_INSTALLING` is defined - the function will immediately bail, the values will never be read, and the globals won't be reset. I have unified the approach in all 3 functions.
* When returning filtered `$locale`, there is no need to set the variable twice.
* In `_maybe_update_core()`, `isset()` can take multiple values to bail before the call to `time()`, if necessary. This is a micro-optimization to prevent PHP from hitting the OS unnecessarily.
See #32444.
Built from https://develop.svn.wordpress.org/trunk@32635
git-svn-id: http://core.svn.wordpress.org/trunk@32605 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2015-05-28 11:29:28 -04:00
if ( is_wp_error ( $raw_response ) || 200 != wp_remote_retrieve_response_code ( $raw_response ) ) {
return ;
}
2008-09-15 12:21:15 -04:00
2010-07-22 09:24:41 -04:00
$new_update = new stdClass ;
2013-01-04 05:13:51 -05:00
$new_update -> last_checked = time ();
2011-04-07 05:56:20 -04:00
$new_update -> checked = $checked ;
2013-09-14 15:58:09 -04:00
$response = json_decode ( wp_remote_retrieve_body ( $raw_response ), true );
2013-09-20 01:55:09 -04:00
2013-09-21 00:08:10 -04:00
if ( is_array ( $response ) ) {
$new_update -> response = $response [ 'themes' ];
$new_update -> translations = $response [ 'translations' ];
}
2008-09-15 12:21:15 -04:00
2010-07-22 09:24:41 -04:00
set_site_transient ( 'update_themes' , $new_update );
2013-09-13 02:19:12 -04:00
}
/**
2013-10-16 20:55:09 -04:00
* Performs WordPress automatic background updates .
2013-09-13 02:19:12 -04:00
*
* @ since 3.7 . 0
*/
2013-10-16 20:55:09 -04:00
function wp_maybe_auto_update () {
2014-05-19 01:04:16 -04:00
include_once ( ABSPATH . '/wp-admin/includes/admin.php' );
include_once ( ABSPATH . '/wp-admin/includes/class-wp-upgrader.php' );
2013-09-13 02:19:12 -04:00
2013-10-24 18:54:38 -04:00
$upgrader = new WP_Automatic_Updater ;
2013-10-16 20:55:09 -04:00
$upgrader -> run ();
2008-09-15 12:21:15 -04:00
}
2013-10-16 10:34:10 -04:00
/**
* Retrieves a list of all language updates available .
*
* @ since 3.7 . 0
Add missing doc blocks to `update.php`:
* `wp_version_check()`, `wp_update_plugins()`, and `wp_update_themes()` do not return meaningful responses, and their responses are never handled by core. As such, they shouldn't alternately return `void` or `false`. "Returning" in those functions is just "bailing"
* In the same functions, `version.php` doesn't need to load if `WP_INSTALLING` is defined - the function will immediately bail, the values will never be read, and the globals won't be reset. I have unified the approach in all 3 functions.
* When returning filtered `$locale`, there is no need to set the variable twice.
* In `_maybe_update_core()`, `isset()` can take multiple values to bail before the call to `time()`, if necessary. This is a micro-optimization to prevent PHP from hitting the OS unnecessarily.
See #32444.
Built from https://develop.svn.wordpress.org/trunk@32635
git-svn-id: http://core.svn.wordpress.org/trunk@32605 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2015-05-28 11:29:28 -04:00
*
* @ return array
2013-10-16 10:34:10 -04:00
*/
function wp_get_translation_updates () {
$updates = array ();
$transients = array ( 'update_core' => 'core' , 'update_plugins' => 'plugin' , 'update_themes' => 'theme' );
foreach ( $transients as $transient => $type ) {
$transient = get_site_transient ( $transient );
if ( empty ( $transient -> translations ) )
continue ;
foreach ( $transient -> translations as $translation ) {
$updates [] = ( object ) $translation ;
}
}
return $updates ;
}
2013-11-11 08:32:10 -05:00
/**
2011-07-26 14:39:57 -04:00
* Collect counts and UI strings for available updates
*
* @ since 3.3 . 0
*
* @ return array
*/
function wp_get_update_data () {
2013-10-16 10:34:10 -04:00
$counts = array ( 'plugins' => 0 , 'themes' => 0 , 'wordpress' => 0 , 'translations' => 0 );
2011-07-26 14:39:57 -04:00
2013-10-16 10:34:10 -04:00
if ( $plugins = current_user_can ( 'update_plugins' ) ) {
2011-07-26 14:39:57 -04:00
$update_plugins = get_site_transient ( 'update_plugins' );
if ( ! empty ( $update_plugins -> response ) )
$counts [ 'plugins' ] = count ( $update_plugins -> response );
}
2013-10-16 10:34:10 -04:00
if ( $themes = current_user_can ( 'update_themes' ) ) {
2011-07-26 14:39:57 -04:00
$update_themes = get_site_transient ( 'update_themes' );
if ( ! empty ( $update_themes -> response ) )
$counts [ 'themes' ] = count ( $update_themes -> response );
}
2013-10-16 10:34:10 -04:00
if ( ( $core = current_user_can ( 'update_core' ) ) && function_exists ( 'get_core_updates' ) ) {
2011-07-26 14:39:57 -04:00
$update_wordpress = get_core_updates ( array ( 'dismissed' => false ) );
if ( ! empty ( $update_wordpress ) && ! in_array ( $update_wordpress [ 0 ] -> response , array ( 'development' , 'latest' ) ) && current_user_can ( 'update_core' ) )
$counts [ 'wordpress' ] = 1 ;
}
2013-10-16 10:34:10 -04:00
if ( ( $core || $plugins || $themes ) && wp_get_translation_updates () )
$counts [ 'translations' ] = 1 ;
$counts [ 'total' ] = $counts [ 'plugins' ] + $counts [ 'themes' ] + $counts [ 'wordpress' ] + $counts [ 'translations' ];
2012-09-16 16:51:51 -04:00
$titles = array ();
2011-07-26 14:39:57 -04:00
if ( $counts [ 'wordpress' ] )
2012-09-16 16:51:51 -04:00
$titles [ 'wordpress' ] = sprintf ( __ ( '%d WordPress Update' ), $counts [ 'wordpress' ] );
2011-07-26 14:39:57 -04:00
if ( $counts [ 'plugins' ] )
2012-09-16 16:51:51 -04:00
$titles [ 'plugins' ] = sprintf ( _n ( '%d Plugin Update' , '%d Plugin Updates' , $counts [ 'plugins' ] ), $counts [ 'plugins' ] );
2011-07-26 14:39:57 -04:00
if ( $counts [ 'themes' ] )
2012-09-16 16:51:51 -04:00
$titles [ 'themes' ] = sprintf ( _n ( '%d Theme Update' , '%d Theme Updates' , $counts [ 'themes' ] ), $counts [ 'themes' ] );
2013-10-16 10:34:10 -04:00
if ( $counts [ 'translations' ] )
$titles [ 'translations' ] = __ ( 'Translation Updates' );
2011-07-26 14:39:57 -04:00
2012-09-16 16:51:51 -04:00
$update_title = $titles ? esc_attr ( implode ( ', ' , $titles ) ) : '' ;
2011-10-24 15:13:23 -04:00
2013-10-06 11:31:09 -04:00
$update_data = array ( 'counts' => $counts , 'title' => $update_title );
/**
* Filter the returned array of update data for plugins , themes , and WordPress core .
*
* @ since 3.5 . 0
*
* @ param array $update_data {
* Fetched update data .
*
* @ type array $counts An array of counts for available plugin , theme , and WordPress updates .
* @ type string $update_title Titles of available updates .
* }
* @ param array $titles An array of update counts and UI strings for available updates .
*/
return apply_filters ( 'wp_get_update_data' , $update_data , $titles );
2011-07-26 14:39:57 -04:00
}
Add missing doc blocks to `update.php`:
* `wp_version_check()`, `wp_update_plugins()`, and `wp_update_themes()` do not return meaningful responses, and their responses are never handled by core. As such, they shouldn't alternately return `void` or `false`. "Returning" in those functions is just "bailing"
* In the same functions, `version.php` doesn't need to load if `WP_INSTALLING` is defined - the function will immediately bail, the values will never be read, and the globals won't be reset. I have unified the approach in all 3 functions.
* When returning filtered `$locale`, there is no need to set the variable twice.
* In `_maybe_update_core()`, `isset()` can take multiple values to bail before the call to `time()`, if necessary. This is a micro-optimization to prevent PHP from hitting the OS unnecessarily.
See #32444.
Built from https://develop.svn.wordpress.org/trunk@32635
git-svn-id: http://core.svn.wordpress.org/trunk@32605 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2015-05-28 11:29:28 -04:00
/**
* @ global string $wp_version
*/
2009-02-16 19:13:25 -05:00
function _maybe_update_core () {
2015-12-06 12:39:27 -05:00
// include an unmodified $wp_version
include ( ABSPATH . WPINC . '/version.php' );
2009-02-16 19:13:25 -05:00
2010-01-08 15:49:55 -05:00
$current = get_site_transient ( 'update_core' );
2009-02-16 19:13:25 -05:00
Add missing doc blocks to `update.php`:
* `wp_version_check()`, `wp_update_plugins()`, and `wp_update_themes()` do not return meaningful responses, and their responses are never handled by core. As such, they shouldn't alternately return `void` or `false`. "Returning" in those functions is just "bailing"
* In the same functions, `version.php` doesn't need to load if `WP_INSTALLING` is defined - the function will immediately bail, the values will never be read, and the globals won't be reset. I have unified the approach in all 3 functions.
* When returning filtered `$locale`, there is no need to set the variable twice.
* In `_maybe_update_core()`, `isset()` can take multiple values to bail before the call to `time()`, if necessary. This is a micro-optimization to prevent PHP from hitting the OS unnecessarily.
See #32444.
Built from https://develop.svn.wordpress.org/trunk@32635
git-svn-id: http://core.svn.wordpress.org/trunk@32605 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2015-05-28 11:29:28 -04:00
if ( isset ( $current -> last_checked , $current -> version_checked ) &&
2012-09-25 01:26:19 -04:00
12 * HOUR_IN_SECONDS > ( time () - $current -> last_checked ) &&
Add missing doc blocks to `update.php`:
* `wp_version_check()`, `wp_update_plugins()`, and `wp_update_themes()` do not return meaningful responses, and their responses are never handled by core. As such, they shouldn't alternately return `void` or `false`. "Returning" in those functions is just "bailing"
* In the same functions, `version.php` doesn't need to load if `WP_INSTALLING` is defined - the function will immediately bail, the values will never be read, and the globals won't be reset. I have unified the approach in all 3 functions.
* When returning filtered `$locale`, there is no need to set the variable twice.
* In `_maybe_update_core()`, `isset()` can take multiple values to bail before the call to `time()`, if necessary. This is a micro-optimization to prevent PHP from hitting the OS unnecessarily.
See #32444.
Built from https://develop.svn.wordpress.org/trunk@32635
git-svn-id: http://core.svn.wordpress.org/trunk@32605 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2015-05-28 11:29:28 -04:00
$current -> version_checked == $wp_version ) {
2009-02-16 19:13:25 -05:00
return ;
Add missing doc blocks to `update.php`:
* `wp_version_check()`, `wp_update_plugins()`, and `wp_update_themes()` do not return meaningful responses, and their responses are never handled by core. As such, they shouldn't alternately return `void` or `false`. "Returning" in those functions is just "bailing"
* In the same functions, `version.php` doesn't need to load if `WP_INSTALLING` is defined - the function will immediately bail, the values will never be read, and the globals won't be reset. I have unified the approach in all 3 functions.
* When returning filtered `$locale`, there is no need to set the variable twice.
* In `_maybe_update_core()`, `isset()` can take multiple values to bail before the call to `time()`, if necessary. This is a micro-optimization to prevent PHP from hitting the OS unnecessarily.
See #32444.
Built from https://develop.svn.wordpress.org/trunk@32635
git-svn-id: http://core.svn.wordpress.org/trunk@32605 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2015-05-28 11:29:28 -04:00
}
2009-02-16 19:13:25 -05:00
wp_version_check ();
}
2008-09-18 13:32:18 -04:00
/**
* Check the last time plugins were run before checking plugin versions .
*
* This might have been backported to WordPress 2.6 . 1 for performance reasons .
* This is used for the wp - admin to check only so often instead of every page
* load .
*
* @ since 2.7 . 0
* @ access private
*/
2008-08-01 00:26:32 -04:00
function _maybe_update_plugins () {
2010-01-08 15:49:55 -05:00
$current = get_site_transient ( 'update_plugins' );
2012-09-25 01:26:19 -04:00
if ( isset ( $current -> last_checked ) && 12 * HOUR_IN_SECONDS > ( time () - $current -> last_checked ) )
2008-08-01 00:26:32 -04:00
return ;
wp_update_plugins ();
}
2008-09-18 13:32:18 -04:00
/**
* Check themes versions only after a duration of time .
*
* This is for performance reasons to make sure that on the theme version
* checker is not run on every page load .
*
* @ since 2.7 . 0
* @ access private
*/
2013-01-04 05:13:51 -05:00
function _maybe_update_themes () {
2010-01-08 15:49:55 -05:00
$current = get_site_transient ( 'update_themes' );
2013-01-04 05:13:51 -05:00
if ( isset ( $current -> last_checked ) && 12 * HOUR_IN_SECONDS > ( time () - $current -> last_checked ) )
2008-09-15 12:21:15 -04:00
return ;
2009-08-16 00:59:38 -04:00
wp_update_themes ();
2008-09-15 12:21:15 -04:00
}
2010-10-20 12:50:57 -04:00
/**
* Schedule core , theme , and plugin update checks .
*
* @ since 3.1 . 0
*/
function wp_schedule_update_checks () {
Use `wp_installing()` instead of `WP_INSTALLING` constant.
The `WP_INSTALLING` constant is a flag that WordPress sets in a number of
places, telling the system that options should be fetched directly from the
database instead of from the cache, that WP should not ping wordpress.org for
updates, that the normal "not installed" checks should be bypassed, and so on.
A constant is generally necessary for this purpose, because the flag is
typically set before the WP bootstrap, meaning that WP functions are not yet
available. However, it is possible - notably, during `wpmu_create_blog()` -
for the "installing" flag to be set after WP has already loaded. In these
cases, `WP_INSTALLING` would be set for the remainder of the process, since
there's no way to change a constant once it's defined. This, in turn, polluted
later function calls that ought to have been outside the scope of site
creation, particularly the non-caching of option data. The problem was
particularly evident in the case of the automated tests, where `WP_INSTALLING`
was set the first time a site was created, and remained set for the rest of the
suite.
The new `wp_installing()` function allows developers to fetch the current
installation status (when called without any arguments) or to set the
installation status (when called with a boolean `true` or `false`). Use of
the `WP_INSTALLING` constant is still supported; `wp_installing()` will default
to `true` if the constant is defined during the bootstrap.
Props boonebgorges, jeremyfelt.
See #31130.
Built from https://develop.svn.wordpress.org/trunk@34828
git-svn-id: http://core.svn.wordpress.org/trunk@34793 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2015-10-05 11:06:28 -04:00
if ( ! wp_next_scheduled ( 'wp_version_check' ) && ! wp_installing () )
2010-10-20 12:50:57 -04:00
wp_schedule_event ( time (), 'twicedaily' , 'wp_version_check' );
Use `wp_installing()` instead of `WP_INSTALLING` constant.
The `WP_INSTALLING` constant is a flag that WordPress sets in a number of
places, telling the system that options should be fetched directly from the
database instead of from the cache, that WP should not ping wordpress.org for
updates, that the normal "not installed" checks should be bypassed, and so on.
A constant is generally necessary for this purpose, because the flag is
typically set before the WP bootstrap, meaning that WP functions are not yet
available. However, it is possible - notably, during `wpmu_create_blog()` -
for the "installing" flag to be set after WP has already loaded. In these
cases, `WP_INSTALLING` would be set for the remainder of the process, since
there's no way to change a constant once it's defined. This, in turn, polluted
later function calls that ought to have been outside the scope of site
creation, particularly the non-caching of option data. The problem was
particularly evident in the case of the automated tests, where `WP_INSTALLING`
was set the first time a site was created, and remained set for the rest of the
suite.
The new `wp_installing()` function allows developers to fetch the current
installation status (when called without any arguments) or to set the
installation status (when called with a boolean `true` or `false`). Use of
the `WP_INSTALLING` constant is still supported; `wp_installing()` will default
to `true` if the constant is defined during the bootstrap.
Props boonebgorges, jeremyfelt.
See #31130.
Built from https://develop.svn.wordpress.org/trunk@34828
git-svn-id: http://core.svn.wordpress.org/trunk@34793 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2015-10-05 11:06:28 -04:00
if ( ! wp_next_scheduled ( 'wp_update_plugins' ) && ! wp_installing () )
2010-10-20 12:50:57 -04:00
wp_schedule_event ( time (), 'twicedaily' , 'wp_update_plugins' );
Use `wp_installing()` instead of `WP_INSTALLING` constant.
The `WP_INSTALLING` constant is a flag that WordPress sets in a number of
places, telling the system that options should be fetched directly from the
database instead of from the cache, that WP should not ping wordpress.org for
updates, that the normal "not installed" checks should be bypassed, and so on.
A constant is generally necessary for this purpose, because the flag is
typically set before the WP bootstrap, meaning that WP functions are not yet
available. However, it is possible - notably, during `wpmu_create_blog()` -
for the "installing" flag to be set after WP has already loaded. In these
cases, `WP_INSTALLING` would be set for the remainder of the process, since
there's no way to change a constant once it's defined. This, in turn, polluted
later function calls that ought to have been outside the scope of site
creation, particularly the non-caching of option data. The problem was
particularly evident in the case of the automated tests, where `WP_INSTALLING`
was set the first time a site was created, and remained set for the rest of the
suite.
The new `wp_installing()` function allows developers to fetch the current
installation status (when called without any arguments) or to set the
installation status (when called with a boolean `true` or `false`). Use of
the `WP_INSTALLING` constant is still supported; `wp_installing()` will default
to `true` if the constant is defined during the bootstrap.
Props boonebgorges, jeremyfelt.
See #31130.
Built from https://develop.svn.wordpress.org/trunk@34828
git-svn-id: http://core.svn.wordpress.org/trunk@34793 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2015-10-05 11:06:28 -04:00
if ( ! wp_next_scheduled ( 'wp_update_themes' ) && ! wp_installing () )
2010-10-20 12:50:57 -04:00
wp_schedule_event ( time (), 'twicedaily' , 'wp_update_themes' );
2013-09-16 22:26:09 -04:00
Use `wp_installing()` instead of `WP_INSTALLING` constant.
The `WP_INSTALLING` constant is a flag that WordPress sets in a number of
places, telling the system that options should be fetched directly from the
database instead of from the cache, that WP should not ping wordpress.org for
updates, that the normal "not installed" checks should be bypassed, and so on.
A constant is generally necessary for this purpose, because the flag is
typically set before the WP bootstrap, meaning that WP functions are not yet
available. However, it is possible - notably, during `wpmu_create_blog()` -
for the "installing" flag to be set after WP has already loaded. In these
cases, `WP_INSTALLING` would be set for the remainder of the process, since
there's no way to change a constant once it's defined. This, in turn, polluted
later function calls that ought to have been outside the scope of site
creation, particularly the non-caching of option data. The problem was
particularly evident in the case of the automated tests, where `WP_INSTALLING`
was set the first time a site was created, and remained set for the rest of the
suite.
The new `wp_installing()` function allows developers to fetch the current
installation status (when called without any arguments) or to set the
installation status (when called with a boolean `true` or `false`). Use of
the `WP_INSTALLING` constant is still supported; `wp_installing()` will default
to `true` if the constant is defined during the bootstrap.
Props boonebgorges, jeremyfelt.
See #31130.
Built from https://develop.svn.wordpress.org/trunk@34828
git-svn-id: http://core.svn.wordpress.org/trunk@34793 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2015-10-05 11:06:28 -04:00
if ( ! wp_next_scheduled ( 'wp_maybe_auto_update' ) && ! wp_installing () ) {
2013-10-17 00:02:09 -04:00
// Schedule auto updates for 7 a.m. and 7 p.m. in the timezone of the site.
$next = strtotime ( 'today 7am' );
$now = time ();
// Find the next instance of 7 a.m. or 7 p.m., but skip it if it is within 3 hours from now.
while ( ( $now + 3 * HOUR_IN_SECONDS ) > $next ) {
$next += 12 * HOUR_IN_SECONDS ;
}
$next = $next - get_option ( 'gmt_offset' ) * HOUR_IN_SECONDS ;
2013-11-13 23:04:10 -05:00
// Add a random number of minutes, so we don't have all sites trying to update exactly on the hour
$next = $next + rand ( 0 , 59 ) * MINUTE_IN_SECONDS ;
2013-10-17 00:02:09 -04:00
wp_schedule_event ( $next , 'twicedaily' , 'wp_maybe_auto_update' );
}
2010-10-20 12:50:57 -04:00
}
2014-11-24 17:50:22 -05:00
/**
* Clear existing update caches for plugins , themes , and core .
*
* @ since 4.1 . 0
*/
2014-12-15 03:55:22 -05:00
function wp_clean_update_cache () {
if ( function_exists ( 'wp_clean_plugins_cache' ) ) {
wp_clean_plugins_cache ();
} else {
delete_site_transient ( 'update_plugins' );
}
2014-11-24 17:50:22 -05:00
wp_clean_themes_cache ();
delete_site_transient ( 'update_core' );
}
2015-03-10 19:20:26 -04:00
if ( ( ! is_main_site () && ! is_network_admin () ) || ( defined ( 'DOING_AJAX' ) && DOING_AJAX ) ) {
return ;
}
add_action ( 'admin_init' , '_maybe_update_core' );
add_action ( 'wp_version_check' , 'wp_version_check' );
add_action ( 'upgrader_process_complete' , 'wp_version_check' , 10 , 0 );
add_action ( 'load-plugins.php' , 'wp_update_plugins' );
add_action ( 'load-update.php' , 'wp_update_plugins' );
add_action ( 'load-update-core.php' , 'wp_update_plugins' );
add_action ( 'admin_init' , '_maybe_update_plugins' );
add_action ( 'wp_update_plugins' , 'wp_update_plugins' );
add_action ( 'upgrader_process_complete' , 'wp_update_plugins' , 10 , 0 );
add_action ( 'load-themes.php' , 'wp_update_themes' );
add_action ( 'load-update.php' , 'wp_update_themes' );
add_action ( 'load-update-core.php' , 'wp_update_themes' );
add_action ( 'admin_init' , '_maybe_update_themes' );
add_action ( 'wp_update_themes' , 'wp_update_themes' );
add_action ( 'upgrader_process_complete' , 'wp_update_themes' , 10 , 0 );
add_action ( 'update_option_WPLANG' , 'wp_clean_update_cache' , 10 , 0 );
add_action ( 'wp_maybe_auto_update' , 'wp_maybe_auto_update' );
add_action ( 'init' , 'wp_schedule_update_checks' );