2007-08-17 06:33:52 -04:00
< ? php
2007-10-30 17:40:30 -04:00
/**
2022-09-09 05:15:12 -04:00
* A simple set of functions to check the WordPress . org Version 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
/**
2022-09-09 04:58:09 -04:00
* Checks WordPress version against the newest version .
2008-08-12 17:21:11 -04:00
*
2020-06-16 17:07:14 -04:00
* The WordPress version , PHP version , and locale is sent .
*
* Checks against the WordPress server at api . wordpress . org . 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
2020-06-16 17:07:14 -04:00
*
2019-08-03 21:12:56 -04:00
* @ global string $wp_version Used to check against the newest WordPress version .
* @ global wpdb $wpdb WordPress database abstraction object .
2020-02-09 22:30:06 -05:00
* @ global string $wp_local_package Locale code of the 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 .
2022-09-09 04:58:09 -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 ) {
2020-05-09 08:52:10 -04:00
global $wpdb , $wp_local_package ;
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
2022-05-20 13:38:14 -04:00
$php_version = PHP_VERSION ;
2007-09-03 19:19:20 -04:00
2017-11-30 18:11:00 -05:00
$current = get_site_transient ( 'update_core' );
2013-09-30 15:47:12 -04:00
$translations = wp_get_installed_translations ( 'core' );
2020-01-28 19:45:18 -05:00
// Invalidate the transient when $wp_version changes.
2024-07-26 20:27:16 -04:00
if ( is_object ( $current ) && wp_get_wp_version () !== $current -> version_checked ) {
2013-11-14 21:35:10 -05:00
$current = false ;
2017-11-30 18:11:00 -05:00
}
2013-11-14 21:35:10 -05:00
2017-11-30 18:11:00 -05:00
if ( ! is_object ( $current ) ) {
2022-11-29 10:51:14 -05:00
$current = new stdClass ();
2017-11-30 18:11:00 -05:00
$current -> updates = array ();
2024-07-26 20:27:16 -04:00
$current -> version_checked = wp_get_wp_version ();
2009-05-05 17:51:48 -04:00
}
2008-11-26 07:04:29 -05:00
2017-11-30 18:11:00 -05:00
if ( ! empty ( $extra_stats ) ) {
2013-11-14 22:04:10 -05:00
$force_check = true ;
2017-11-30 18:11:00 -05:00
}
2013-11-14 22:04:10 -05:00
2020-01-28 19:45:18 -05:00
// Wait 1 minute between multiple version check requests.
$timeout = MINUTE_IN_SECONDS ;
2012-01-05 14:49:47 -05:00
$time_not_changed = isset ( $current -> last_checked ) && $timeout > ( time () - $current -> last_checked );
2020-05-09 08:52:10 -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 ( ! $force_check && $time_not_changed ) {
return ;
}
2012-01-05 14:49:47 -05:00
2013-10-06 11:31:09 -04:00
/**
2016-05-22 14:50:28 -04:00
* Filters the locale requested for WordPress core translations .
2013-10-06 11:31:09 -04:00
*
* @ 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
2020-01-28 19:45:18 -05:00
// Update last_checked for current to prevent multiple blocking requests if request hangs.
2008-11-26 06:48:05 -05:00
$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
2023-06-27 01:11:27 -04:00
if ( method_exists ( $wpdb , 'db_server_info' ) ) {
$mysql_version = $wpdb -> db_server_info ();
} elseif ( method_exists ( $wpdb , 'db_version' ) ) {
2017-11-30 18:11:00 -05:00
$mysql_version = preg_replace ( '/[^0-9.].*/' , '' , $wpdb -> db_version () );
} else {
2008-08-26 18:30:56 -04:00
$mysql_version = 'N/A' ;
2017-11-30 18:11:00 -05:00
}
2010-04-05 16:19:07 -04:00
2013-01-04 05:13:51 -05:00
if ( is_multisite () ) {
2017-11-30 18:11:00 -05:00
$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 {
$multisite_enabled = 0 ;
2017-11-30 18:11:00 -05:00
$num_blogs = 1 ;
$wp_install = home_url ( '/' );
2010-04-05 16:19:07 -04:00
}
2022-07-21 16:22:09 -04:00
$extensions = get_loaded_extensions ();
sort ( $extensions , SORT_STRING | SORT_FLAG_CASE );
2011-09-17 05:14:27 -04:00
$query = array (
2024-07-26 20:27:16 -04:00
'version' => wp_get_wp_version (),
2015-12-06 10:44:27 -05:00
'php' => $php_version ,
'locale' => $locale ,
'mysql' => $mysql_version ,
'local_package' => isset ( $wp_local_package ) ? $wp_local_package : '' ,
'blogs' => $num_blogs ,
Users: Introduce the concept of a large site to single site installations.
Currently in WordPress multisite there is a concept of large networks. The function `wp_is_large_network` is used to determine if a network has a large number of sites or users. If a network is marked as large, then
expensive queries to calculate user counts are not run on page load but deferred to scheduled events. However there are a number of places in a single site installation where this functionality would also be useful, as
expensive calls to count users and roles can make screens in the admin extremely slow.
In this change, the `get_user_count` function and related functionality around it is ported to be available in a single site context. This means that expensive calls to the `count_users` function are replaced with
calls to `get_user_count`. This change also includes a new function called `wp_is_large_user_count` and a filter of the same name, to mark if a site is large.
Props johnbillion, Spacedmonkey, Mista-Flo, lumpysimon, tharsheblows, obenland, miss_jwo, jrchamp, flixos90, macbookandrew, pento, desrosj, johnjamesjacoby, jb510, davidbaumwald, costdev.
Fixes #38741.
Built from https://develop.svn.wordpress.org/trunk@53011
git-svn-id: http://core.svn.wordpress.org/trunk@52600 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2022-03-29 08:42:13 -04:00
'users' => get_user_count (),
2015-12-06 10:44:27 -05:00
'multisite_enabled' => $multisite_enabled ,
'initial_db_version' => get_site_option ( 'initial_db_version' ),
2022-07-21 16:22:09 -04:00
'extensions' => array_combine ( $extensions , array_map ( 'phpversion' , $extensions ) ),
'platform_flags' => array (
'os' => PHP_OS ,
'bits' => PHP_INT_SIZE === 4 ? 32 : 64 ,
),
'image_support' => array (),
2011-09-17 05:14:27 -04:00
);
2022-07-21 16:22:09 -04:00
if ( function_exists ( 'gd_info' ) ) {
$gd_info = gd_info ();
// Filter to supported values.
$gd_info = array_filter ( $gd_info );
// Add data for GD WebP and AVIF support.
$query [ 'image_support' ][ 'gd' ] = array_keys (
array_filter (
array (
'webp' => isset ( $gd_info [ 'WebP Support' ] ),
'avif' => isset ( $gd_info [ 'AVIF Support' ] ),
)
)
);
}
if ( class_exists ( 'Imagick' ) ) {
// Add data for Imagick WebP and AVIF support.
$query [ 'image_support' ][ 'imagick' ] = array_keys (
array_filter (
array (
'webp' => ! empty ( Imagick :: queryFormats ( 'WEBP' ) ),
'avif' => ! empty ( Imagick :: queryFormats ( 'AVIF' ) ),
)
)
);
}
2017-10-21 07:55:47 -04:00
/**
2020-08-10 20:34:08 -04:00
* Filters the query arguments sent as part of the core version check .
2017-10-21 09:46:50 -04:00
*
2017-10-21 07:55:47 -04:00
* WARNING : Changing this data may result in your site not receiving security updates .
* Please exercise extreme caution .
*
* @ since 4.9 . 0
*
2017-10-21 09:46:50 -04:00
* @ param array $query {
2017-11-30 18:11:00 -05:00
* Version check query arguments .
2017-10-21 09:46:50 -04:00
*
* @ type string $version WordPress version number .
* @ type string $php PHP version number .
* @ type string $locale The locale to retrieve updates for .
* @ type string $mysql MySQL version number .
* @ type string $local_package The value of the $wp_local_package global , when set .
2017-10-21 18:42:51 -04:00
* @ type int $blogs Number of sites on this WordPress installation .
* @ type int $users Number of users on this WordPress installation .
* @ type int $multisite_enabled Whether this WordPress installation uses Multisite .
2017-10-21 09:46:50 -04:00
* @ type int $initial_db_version Database version of WordPress at time of installation .
* }
2017-10-21 07:55:47 -04:00
*/
$query = apply_filters ( 'core_version_check_query_args' , $query );
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
);
2017-11-30 18:11:00 -05:00
if ( is_array ( $extra_stats ) ) {
2013-10-14 19:33:10 -04:00
$post_body = array_merge ( $post_body , $extra_stats );
2017-11-30 18:11:00 -05:00
}
2013-10-09 21:32:09 -04:00
2021-01-30 05:34:02 -05:00
// Allow for WP_AUTO_UPDATE_CORE to specify beta/RC/development releases.
if ( defined ( 'WP_AUTO_UPDATE_CORE' )
&& in_array ( WP_AUTO_UPDATE_CORE , array ( 'beta' , 'rc' , 'development' , 'branch-development' ), true )
) {
2020-10-20 13:56:06 -04:00
$query [ 'channel' ] = WP_AUTO_UPDATE_CORE ;
}
2021-11-05 08:18:58 -04:00
$url = 'http://api.wordpress.org/core/version-check/1.7/?' . http_build_query ( $query , '' , '&' );
2019-07-02 19:42:58 -04:00
$http_url = $url ;
$ssl = wp_http_supports ( array ( 'ssl' ) );
2020-05-09 08:52:10 -04:00
2019-07-02 19:42:58 -04:00
if ( $ssl ) {
2013-09-02 23:22:10 -04:00
$url = set_url_scheme ( $url , 'https' );
2017-11-30 18:11:00 -05:00
}
2008-08-01 01:00:07 -04:00
2017-05-06 10:30:40 -04:00
$doing_cron = wp_doing_cron ();
2008-12-21 16:52:15 -05:00
$options = array (
2017-11-30 18:11:00 -05:00
'timeout' => $doing_cron ? 30 : 3 ,
2024-07-26 20:27:16 -04:00
'user-agent' => 'WordPress/' . wp_get_wp_version () . '; ' . home_url ( '/' ),
2017-11-30 18:11:00 -05:00
'headers' => array (
2010-04-05 16:19:07 -04:00
'wp_install' => $wp_install ,
2017-11-30 18:11:00 -05:00
'wp_blog' => home_url ( '/' ),
2013-09-30 15:47:12 -04:00
),
2017-11-30 18:11:00 -05: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 );
2020-05-09 08:52:10 -04:00
2013-10-27 17:09:10 -04:00
if ( $ssl && is_wp_error ( $response ) ) {
Code Modernization: Use wp_trigger_error() instead of trigger_error().
Replaces `trigger_error()` with `wp_trigger_error()`.
The usage of `wp_trigger_error()` avoids generating `E_USER` family errors unless `WP_DEBUG` is on. In doing so, users should not see these messages in normal production.
Notes:
* Removes `E_USER_NOTICE` when passed as an argumnent, as it's the default error level.
* An empty string is passed for the function name when its name is already in the error message or does not add value to the error message.
* Externally maintained libraries are not included.
Follow-up to [55204], [25956], [29630], [38883], [52062], [52049], [54272], [38883], [55245], [51599], [14452], [38883], [24976].
Props prasadkarmalkar, rajinsharwar, thelovekesh, hellofromTonya, swissspidy.
Fixes #59652.
Built from https://develop.svn.wordpress.org/trunk@58409
git-svn-id: http://core.svn.wordpress.org/trunk@57858 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2024-06-13 16:50:14 -04:00
wp_trigger_error (
__FUNCTION__ ,
2016-11-20 20:52:32 -05:00
sprintf (
2019-09-02 20:41:05 -04:00
/* translators: %s: Support forums URL. */
2016-11-20 20:52:32 -05:00
__ ( '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="%s">support forums</a>.' ),
2019-05-25 10:24:50 -04:00
__ ( 'https://wordpress.org/support/forums/' )
2016-11-20 20:52:32 -05:00
) . ' ' . __ ( '(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
2020-05-09 08:52:10 -04:00
if ( is_wp_error ( $response ) || 200 !== wp_remote_retrieve_response_code ( $response ) ) {
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-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
2018-02-06 06:04:34 -05:00
$offers = $body [ 'offers' ];
2011-06-10 01:47:44 -04:00
foreach ( $offers as & $offer ) {
foreach ( $offer as $offer_key => $value ) {
2020-05-09 08:52:10 -04:00
if ( 'packages' === $offer_key ) {
2017-11-30 18:11:00 -05:00
$offer [ 'packages' ] = ( object ) array_intersect_key (
array_map ( 'esc_url' , $offer [ 'packages' ] ),
array_fill_keys ( array ( 'full' , 'no_content' , 'new_bundled' , 'partial' , 'rollback' ), '' )
);
2020-05-09 08:52:10 -04:00
} elseif ( 'download' === $offer_key ) {
2011-06-10 01:47:44 -04:00
$offer [ 'download' ] = esc_url ( $value );
2017-11-30 18:11:00 -05:00
} else {
2011-06-10 01:47:44 -04:00
$offer [ $offer_key ] = esc_html ( $value );
2017-11-30 18:11:00 -05:00
}
2011-06-10 01:47:44 -04:00
}
2017-11-30 18:11:00 -05:00
$offer = ( object ) array_intersect_key (
2018-08-16 21:51:36 -04:00
$offer ,
array_fill_keys (
2017-11-30 18:11:00 -05:00
array (
'response' ,
'download' ,
'locale' ,
'packages' ,
'current' ,
'version' ,
'php_version' ,
'mysql_version' ,
'new_bundled' ,
'partial_version' ,
'notify_email' ,
'support_email' ,
'new_files' ,
2018-08-16 21:51:36 -04:00
),
''
2017-11-30 18:11:00 -05:00
)
);
2008-10-31 14:51:06 -04:00
}
2017-11-30 18:11:00 -05:00
$updates = new stdClass ();
$updates -> updates = $offers ;
$updates -> last_checked = time ();
2024-07-26 20:27:16 -04:00
$updates -> version_checked = wp_get_wp_version ();
2013-09-30 15:47:12 -04:00
2017-11-30 18:11:00 -05:00
if ( isset ( $body [ 'translations' ] ) ) {
2013-09-30 15:47:12 -04:00
$updates -> translations = $body [ 'translations' ];
2017-11-30 18:11:00 -05:00
}
2013-09-30 15:47:12 -04:00
2014-04-14 22:23:16 -04:00
set_site_transient ( 'update_core' , $updates );
if ( ! empty ( $body [ 'ttl' ] ) ) {
$ttl = ( int ) $body [ 'ttl' ];
2020-05-09 08:52:10 -04:00
2014-04-14 22:23:16 -04:00
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' );
}
}
2016-01-06 01:12:26 -05:00
// Trigger background updates if running non-interactively, and we weren't called from the update handler.
2018-02-06 06:04:34 -05:00
if ( $doing_cron && ! doing_action ( 'wp_maybe_auto_update' ) ) {
2019-01-15 22:38:49 -05:00
/**
2020-07-06 15:15:03 -04:00
* Fires during wp_cron , starting the auto - update process .
2019-01-15 22:38:49 -05:00
*
* @ since 3.9 . 0
*/
2018-02-06 06:04:34 -05:00
do_action ( 'wp_maybe_auto_update' );
2014-04-14 22:23:16 -04:00
}
2007-08-17 06:33:52 -04:00
}
2008-07-11 18:04:03 -04:00
/**
2020-06-26 14:34:03 -04:00
* Checks for available updates to plugins based on the latest versions hosted on WordPress . org .
*
* Despite its name this function does not actually perform any updates , it only checks for available updates .
2008-07-11 18:04:03 -04:00
*
2020-06-16 17:07:14 -04:00
* A list of all plugins installed is sent to WP , along with the site locale .
*
* Checks against the WordPress server at 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
2020-06-16 17:07:14 -04:00
*
2020-02-09 22:30:06 -05:00
* @ global string $wp_version The WordPress version string .
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
2020-01-28 19:45:18 -05:00
// If running blog-side, bail unless we've not checked in the last 12 hours.
2017-11-30 18:11:00 -05:00
if ( ! function_exists ( 'get_plugins' ) ) {
2020-02-06 01:33:11 -05:00
require_once ABSPATH . 'wp-admin/includes/plugin.php' ;
2017-11-30 18:11:00 -05:00
}
2008-07-11 18:04:03 -04:00
2017-11-30 18:11:00 -05:00
$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' );
2020-05-09 08:52:10 -04:00
2017-11-30 18:11:00 -05:00
if ( ! is_object ( $current ) ) {
2022-11-29 10:51:14 -05:00
$current = new stdClass ();
2017-11-30 18:11:00 -05:00
}
2008-07-11 18:04:03 -04:00
2022-11-29 10:51:14 -05:00
$updates = new stdClass ();
Plugins: Add support for `Update URI` header.
This allows third-party plugins to avoid accidentally being overwritten with an update of a plugin of a similar name from the WordPress.org Plugin Directory.
Additionally, introduce the `update_plugins_{$hostname}` filter, which third-party plugins can use to offer updates for a given hostname.
If set, the `Update URI` header field should be a URI and have a unique hostname.
Some examples include:
* `https://wordpress.org/plugins/example-plugin/`
* `https://example.com/my-plugin/`
* `my-custom-plugin-name`
`Update URI: false` also works, and unless there is code handling the `false` hostname, the plugin will never get an update notification.
If the header is present, the WordPress.org API will currently only return updates for the plugin if it matches the following format:
* `https://wordpress.org/plugins/{$slug}/`
* `w.org/plugin/{$slug}`
If the header has any other value, the API will not return a result and will ignore the plugin for update purposes.
Props dd32, DavidAnderson, meloniq, markjaquith, DrewAPicture, mweichert, design_dolphin, filosofo, sean212, nhuja, JeroenReumkens, infolu, dingdang, joyously, earnjam, williampatton, grapplerulrich, markparnell, apedog, afragen, miqrogroove, rmccue, crazycoders, jdgrimes, damonganto, joostdevalk, jorbin, georgestephanis, khromov, GeekStreetWP, jb510, Rarst, juliobox, Ipstenu, mikejolley, Otto42, gMagicScott, TJNowell, GaryJ, knutsp, mordauk, nvartolomei, aspexi, chriscct7, benoitchantre, ryno267, lev0, gregorlove, dougwollison, SergeyBiryukov.
See #14179, #23318, #32101.
Built from https://develop.svn.wordpress.org/trunk@50921
git-svn-id: http://core.svn.wordpress.org/trunk@50530 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2021-05-17 13:04:01 -04:00
$updates -> last_checked = time ();
$updates -> response = array ();
$updates -> translations = array ();
$updates -> no_update = array ();
2008-07-11 18:04:03 -04:00
2017-05-06 10:30:40 -04:00
$doing_cron = wp_doing_cron ();
2012-01-05 14:49:47 -05:00
// Check for update on a different schedule, depending on the page.
switch ( current_filter () ) {
2017-11-30 18:11:00 -05:00
case 'upgrader_process_complete' :
2013-09-22 22:08:10 -04:00
$timeout = 0 ;
break ;
2017-11-30 18:11:00 -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 ;
2017-11-30 18:11:00 -05:00
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 ;
2017-11-30 18:11:00 -05:00
default :
2017-05-06 10:30:40 -04:00
if ( $doing_cron ) {
2018-01-23 23:17:30 -05:00
$timeout = 2 * HOUR_IN_SECONDS ;
2014-04-14 22:23:16 -04:00
} 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 ;
2020-05-09 08:52:10 -04:00
2012-01-05 14:49:47 -05:00
foreach ( $plugins as $file => $p ) {
Plugins: Add support for `Update URI` header.
This allows third-party plugins to avoid accidentally being overwritten with an update of a plugin of a similar name from the WordPress.org Plugin Directory.
Additionally, introduce the `update_plugins_{$hostname}` filter, which third-party plugins can use to offer updates for a given hostname.
If set, the `Update URI` header field should be a URI and have a unique hostname.
Some examples include:
* `https://wordpress.org/plugins/example-plugin/`
* `https://example.com/my-plugin/`
* `my-custom-plugin-name`
`Update URI: false` also works, and unless there is code handling the `false` hostname, the plugin will never get an update notification.
If the header is present, the WordPress.org API will currently only return updates for the plugin if it matches the following format:
* `https://wordpress.org/plugins/{$slug}/`
* `w.org/plugin/{$slug}`
If the header has any other value, the API will not return a result and will ignore the plugin for update purposes.
Props dd32, DavidAnderson, meloniq, markjaquith, DrewAPicture, mweichert, design_dolphin, filosofo, sean212, nhuja, JeroenReumkens, infolu, dingdang, joyously, earnjam, williampatton, grapplerulrich, markparnell, apedog, afragen, miqrogroove, rmccue, crazycoders, jdgrimes, damonganto, joostdevalk, jorbin, georgestephanis, khromov, GeekStreetWP, jb510, Rarst, juliobox, Ipstenu, mikejolley, Otto42, gMagicScott, TJNowell, GaryJ, knutsp, mordauk, nvartolomei, aspexi, chriscct7, benoitchantre, ryno267, lev0, gregorlove, dougwollison, SergeyBiryukov.
See #14179, #23318, #32101.
Built from https://develop.svn.wordpress.org/trunk@50921
git-svn-id: http://core.svn.wordpress.org/trunk@50530 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2021-05-17 13:04:01 -04:00
$updates -> checked [ $file ] = $p [ 'Version' ];
2012-01-05 14:49:47 -05:00
2020-10-08 17:15:13 -04:00
if ( ! isset ( $current -> checked [ $file ] ) || ( string ) $current -> checked [ $file ] !== ( string ) $p [ 'Version' ] ) {
2011-11-16 02:23:15 -05:00
$plugin_changed = true ;
2017-11-30 18:11:00 -05:00
}
2012-01-05 14:49:47 -05:00
}
2017-11-30 18:11:00 -05:00
if ( isset ( $current -> response ) && is_array ( $current -> response ) ) {
2012-01-05 14:49:47 -05:00
foreach ( $current -> response as $plugin_file => $update_details ) {
2017-11-30 18:11:00 -05:00
if ( ! isset ( $plugins [ $plugin_file ] ) ) {
2012-01-05 14:49:47 -05:00
$plugin_changed = true ;
break ;
}
2011-11-16 02:23:15 -05:00
}
2008-07-16 17:53:32 -04:00
}
2020-01-28 19:45:18 -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
2020-01-28 19:45:18 -05:00
// Update last_checked for current to prevent multiple blocking requests if request hangs.
2008-11-26 06:48:05 -05:00
$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
2016-02-23 11:17:26 -05:00
$locales = array_values ( get_available_languages () );
2016-03-16 12:15:28 -04:00
2013-09-28 00:18:12 -04:00
/**
2016-05-22 14:50:28 -04:00
* Filters the locales requested for plugin translations .
2013-09-28 00:18:12 -04:00
*
* @ since 3.7 . 0
2016-03-10 18:01:26 -05:00
* @ since 4.5 . 0 The default value of the `$locales` parameter changed to include all locales .
2013-09-28 00:18:12 -04:00
*
2022-09-22 07:13:14 -04:00
* @ param string [] $locales Plugin locales . Default is all available locales of the site .
2013-09-28 00:18:12 -04:00
*/
2016-02-23 11:17:26 -05:00
$locales = apply_filters ( 'plugins_update_check_locales' , $locales );
$locales = array_unique ( $locales );
2013-09-28 00:18:12 -04:00
2017-05-06 10:30:40 -04:00
if ( $doing_cron ) {
Coding Standards: Clarify time units for various timeout or expiration values.
This changeset implements a clearer and more consistent timeout/duration/expiration format. It updates time durations used in various files, as per WordPress coding standards:
- If the value can be represented as an integer (not a fractional) number of minutes (hours, etc.), use the appropriate constant (e.g.: `MINUTE_IN_SECONDS`) multiplied by that number.
- Otherwise, keep the value as is and add a comment with the units for clarity.
Follow-up to [11823], [13177], [21996], [37747], [53714].
Props hztyfoon, audrasjb, arrasel403, krupalpanchal, GaryJ, SergeyBiryukov, peterwilsoncc, rudlinkon, costdev, robinwpdeveloper.
Fixes #56293.
See #55647.
Built from https://develop.svn.wordpress.org/trunk@54113
git-svn-id: http://core.svn.wordpress.org/trunk@53672 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2022-09-09 04:16:18 -04:00
$timeout = 30 ; // 30 seconds.
2014-06-19 19:21:16 -04:00
} else {
2020-01-28 19:45:18 -05: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 (
2017-11-30 18:11:00 -05:00
'timeout' => $timeout ,
'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
),
2024-07-26 20:27:16 -04:00
'user-agent' => 'WordPress/' . wp_get_wp_version () . '; ' . home_url ( '/' ),
2008-12-21 16:52:15 -05:00
);
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
}
2019-07-02 19:42:58 -04:00
$url = 'http://api.wordpress.org/plugins/update-check/1.1/' ;
$http_url = $url ;
$ssl = wp_http_supports ( array ( 'ssl' ) );
2020-05-09 08:52:10 -04:00
2019-07-02 19:42:58 -04:00
if ( $ssl ) {
2013-09-09 03:54:11 -04:00
$url = set_url_scheme ( $url , 'https' );
2017-11-30 18:11:00 -05:00
}
2013-09-09 03:54:11 -04:00
$raw_response = wp_remote_post ( $url , $options );
2020-05-09 08:52:10 -04:00
2013-10-27 17:09:10 -04:00
if ( $ssl && is_wp_error ( $raw_response ) ) {
Code Modernization: Use wp_trigger_error() instead of trigger_error().
Replaces `trigger_error()` with `wp_trigger_error()`.
The usage of `wp_trigger_error()` avoids generating `E_USER` family errors unless `WP_DEBUG` is on. In doing so, users should not see these messages in normal production.
Notes:
* Removes `E_USER_NOTICE` when passed as an argumnent, as it's the default error level.
* An empty string is passed for the function name when its name is already in the error message or does not add value to the error message.
* Externally maintained libraries are not included.
Follow-up to [55204], [25956], [29630], [38883], [52062], [52049], [54272], [38883], [55245], [51599], [14452], [38883], [24976].
Props prasadkarmalkar, rajinsharwar, thelovekesh, hellofromTonya, swissspidy.
Fixes #59652.
Built from https://develop.svn.wordpress.org/trunk@58409
git-svn-id: http://core.svn.wordpress.org/trunk@57858 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2024-06-13 16:50:14 -04:00
wp_trigger_error (
__FUNCTION__ ,
2016-11-20 20:52:32 -05:00
sprintf (
2019-09-02 20:41:05 -04:00
/* translators: %s: Support forums URL. */
2016-11-20 20:52:32 -05:00
__ ( '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="%s">support forums</a>.' ),
2019-05-25 10:24:50 -04:00
__ ( 'https://wordpress.org/support/forums/' )
2016-11-20 20:52:32 -05:00
) . ' ' . __ ( '(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
2020-05-09 08:52:10 -04:00
if ( is_wp_error ( $raw_response ) || 200 !== wp_remote_retrieve_response_code ( $raw_response ) ) {
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
2013-09-21 00:08:10 -04:00
$response = json_decode ( wp_remote_retrieve_body ( $raw_response ), true );
2020-05-09 08:52:10 -04:00
Plugins: Add support for `Update URI` header.
This allows third-party plugins to avoid accidentally being overwritten with an update of a plugin of a similar name from the WordPress.org Plugin Directory.
Additionally, introduce the `update_plugins_{$hostname}` filter, which third-party plugins can use to offer updates for a given hostname.
If set, the `Update URI` header field should be a URI and have a unique hostname.
Some examples include:
* `https://wordpress.org/plugins/example-plugin/`
* `https://example.com/my-plugin/`
* `my-custom-plugin-name`
`Update URI: false` also works, and unless there is code handling the `false` hostname, the plugin will never get an update notification.
If the header is present, the WordPress.org API will currently only return updates for the plugin if it matches the following format:
* `https://wordpress.org/plugins/{$slug}/`
* `w.org/plugin/{$slug}`
If the header has any other value, the API will not return a result and will ignore the plugin for update purposes.
Props dd32, DavidAnderson, meloniq, markjaquith, DrewAPicture, mweichert, design_dolphin, filosofo, sean212, nhuja, JeroenReumkens, infolu, dingdang, joyously, earnjam, williampatton, grapplerulrich, markparnell, apedog, afragen, miqrogroove, rmccue, crazycoders, jdgrimes, damonganto, joostdevalk, jorbin, georgestephanis, khromov, GeekStreetWP, jb510, Rarst, juliobox, Ipstenu, mikejolley, Otto42, gMagicScott, TJNowell, GaryJ, knutsp, mordauk, nvartolomei, aspexi, chriscct7, benoitchantre, ryno267, lev0, gregorlove, dougwollison, SergeyBiryukov.
See #14179, #23318, #32101.
Built from https://develop.svn.wordpress.org/trunk@50921
git-svn-id: http://core.svn.wordpress.org/trunk@50530 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2021-05-17 13:04:01 -04:00
if ( $response && is_array ( $response ) ) {
$updates -> response = $response [ 'plugins' ];
$updates -> translations = $response [ 'translations' ];
$updates -> no_update = $response [ 'no_update' ];
}
// Support updates for any plugins using the `Update URI` header field.
foreach ( $plugins as $plugin_file => $plugin_data ) {
if ( ! $plugin_data [ 'UpdateURI' ] || isset ( $updates -> response [ $plugin_file ] ) ) {
continue ;
}
2022-06-01 14:14:10 -04:00
$hostname = wp_parse_url ( sanitize_url ( $plugin_data [ 'UpdateURI' ] ), PHP_URL_HOST );
Plugins: Add support for `Update URI` header.
This allows third-party plugins to avoid accidentally being overwritten with an update of a plugin of a similar name from the WordPress.org Plugin Directory.
Additionally, introduce the `update_plugins_{$hostname}` filter, which third-party plugins can use to offer updates for a given hostname.
If set, the `Update URI` header field should be a URI and have a unique hostname.
Some examples include:
* `https://wordpress.org/plugins/example-plugin/`
* `https://example.com/my-plugin/`
* `my-custom-plugin-name`
`Update URI: false` also works, and unless there is code handling the `false` hostname, the plugin will never get an update notification.
If the header is present, the WordPress.org API will currently only return updates for the plugin if it matches the following format:
* `https://wordpress.org/plugins/{$slug}/`
* `w.org/plugin/{$slug}`
If the header has any other value, the API will not return a result and will ignore the plugin for update purposes.
Props dd32, DavidAnderson, meloniq, markjaquith, DrewAPicture, mweichert, design_dolphin, filosofo, sean212, nhuja, JeroenReumkens, infolu, dingdang, joyously, earnjam, williampatton, grapplerulrich, markparnell, apedog, afragen, miqrogroove, rmccue, crazycoders, jdgrimes, damonganto, joostdevalk, jorbin, georgestephanis, khromov, GeekStreetWP, jb510, Rarst, juliobox, Ipstenu, mikejolley, Otto42, gMagicScott, TJNowell, GaryJ, knutsp, mordauk, nvartolomei, aspexi, chriscct7, benoitchantre, ryno267, lev0, gregorlove, dougwollison, SergeyBiryukov.
See #14179, #23318, #32101.
Built from https://develop.svn.wordpress.org/trunk@50921
git-svn-id: http://core.svn.wordpress.org/trunk@50530 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2021-05-17 13:04:01 -04:00
/**
* Filters the update response for a given plugin hostname .
*
* The dynamic portion of the hook name , `$hostname` , refers to the hostname
* of the URI specified in the `Update URI` header field .
*
* @ since 5.8 . 0
*
* @ param array | false $update {
* The plugin update data with the latest details . Default false .
*
* @ type string $id Optional . ID of the plugin for update purposes , should be a URI
* specified in the `Update URI` header field .
* @ type string $slug Slug of the plugin .
* @ type string $version The version of the plugin .
* @ type string $url The URL for details of the plugin .
* @ type string $package Optional . The update ZIP for the plugin .
* @ type string $tested Optional . The version of WordPress the plugin is tested against .
* @ type string $requires_php Optional . The version of PHP which the plugin requires .
* @ type bool $autoupdate Optional . Whether the plugin should automatically update .
* @ type array $icons Optional . Array of plugin icons .
* @ type array $banners Optional . Array of plugin banners .
* @ type array $banners_rtl Optional . Array of plugin RTL banners .
* @ type array $translations {
* Optional . List of translation updates for the plugin .
*
* @ type string $language The language the translation update is for .
* @ type string $version The version of the plugin this translation is for .
* This is not the version of the language file .
* @ type string $updated The update timestamp of the translation file .
* Should be a date in the `YYYY-MM-DD HH:MM:SS` format .
* @ type string $package The ZIP location containing the translation update .
* @ type string $autoupdate Whether the translation should be automatically installed .
* }
* }
* @ param array $plugin_data Plugin headers .
* @ param string $plugin_file Plugin filename .
2022-09-22 07:13:14 -04:00
* @ param string [] $locales Installed locales to look up translations for .
Plugins: Add support for `Update URI` header.
This allows third-party plugins to avoid accidentally being overwritten with an update of a plugin of a similar name from the WordPress.org Plugin Directory.
Additionally, introduce the `update_plugins_{$hostname}` filter, which third-party plugins can use to offer updates for a given hostname.
If set, the `Update URI` header field should be a URI and have a unique hostname.
Some examples include:
* `https://wordpress.org/plugins/example-plugin/`
* `https://example.com/my-plugin/`
* `my-custom-plugin-name`
`Update URI: false` also works, and unless there is code handling the `false` hostname, the plugin will never get an update notification.
If the header is present, the WordPress.org API will currently only return updates for the plugin if it matches the following format:
* `https://wordpress.org/plugins/{$slug}/`
* `w.org/plugin/{$slug}`
If the header has any other value, the API will not return a result and will ignore the plugin for update purposes.
Props dd32, DavidAnderson, meloniq, markjaquith, DrewAPicture, mweichert, design_dolphin, filosofo, sean212, nhuja, JeroenReumkens, infolu, dingdang, joyously, earnjam, williampatton, grapplerulrich, markparnell, apedog, afragen, miqrogroove, rmccue, crazycoders, jdgrimes, damonganto, joostdevalk, jorbin, georgestephanis, khromov, GeekStreetWP, jb510, Rarst, juliobox, Ipstenu, mikejolley, Otto42, gMagicScott, TJNowell, GaryJ, knutsp, mordauk, nvartolomei, aspexi, chriscct7, benoitchantre, ryno267, lev0, gregorlove, dougwollison, SergeyBiryukov.
See #14179, #23318, #32101.
Built from https://develop.svn.wordpress.org/trunk@50921
git-svn-id: http://core.svn.wordpress.org/trunk@50530 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2021-05-17 13:04:01 -04:00
*/
$update = apply_filters ( " update_plugins_ { $hostname } " , false , $plugin_data , $plugin_file , $locales );
if ( ! $update ) {
continue ;
}
2020-05-09 08:52:10 -04:00
Plugins: Add support for `Update URI` header.
This allows third-party plugins to avoid accidentally being overwritten with an update of a plugin of a similar name from the WordPress.org Plugin Directory.
Additionally, introduce the `update_plugins_{$hostname}` filter, which third-party plugins can use to offer updates for a given hostname.
If set, the `Update URI` header field should be a URI and have a unique hostname.
Some examples include:
* `https://wordpress.org/plugins/example-plugin/`
* `https://example.com/my-plugin/`
* `my-custom-plugin-name`
`Update URI: false` also works, and unless there is code handling the `false` hostname, the plugin will never get an update notification.
If the header is present, the WordPress.org API will currently only return updates for the plugin if it matches the following format:
* `https://wordpress.org/plugins/{$slug}/`
* `w.org/plugin/{$slug}`
If the header has any other value, the API will not return a result and will ignore the plugin for update purposes.
Props dd32, DavidAnderson, meloniq, markjaquith, DrewAPicture, mweichert, design_dolphin, filosofo, sean212, nhuja, JeroenReumkens, infolu, dingdang, joyously, earnjam, williampatton, grapplerulrich, markparnell, apedog, afragen, miqrogroove, rmccue, crazycoders, jdgrimes, damonganto, joostdevalk, jorbin, georgestephanis, khromov, GeekStreetWP, jb510, Rarst, juliobox, Ipstenu, mikejolley, Otto42, gMagicScott, TJNowell, GaryJ, knutsp, mordauk, nvartolomei, aspexi, chriscct7, benoitchantre, ryno267, lev0, gregorlove, dougwollison, SergeyBiryukov.
See #14179, #23318, #32101.
Built from https://develop.svn.wordpress.org/trunk@50921
git-svn-id: http://core.svn.wordpress.org/trunk@50530 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2021-05-17 13:04:01 -04:00
$update = ( object ) $update ;
2020-05-09 08:52:10 -04:00
Plugins: Add support for `Update URI` header.
This allows third-party plugins to avoid accidentally being overwritten with an update of a plugin of a similar name from the WordPress.org Plugin Directory.
Additionally, introduce the `update_plugins_{$hostname}` filter, which third-party plugins can use to offer updates for a given hostname.
If set, the `Update URI` header field should be a URI and have a unique hostname.
Some examples include:
* `https://wordpress.org/plugins/example-plugin/`
* `https://example.com/my-plugin/`
* `my-custom-plugin-name`
`Update URI: false` also works, and unless there is code handling the `false` hostname, the plugin will never get an update notification.
If the header is present, the WordPress.org API will currently only return updates for the plugin if it matches the following format:
* `https://wordpress.org/plugins/{$slug}/`
* `w.org/plugin/{$slug}`
If the header has any other value, the API will not return a result and will ignore the plugin for update purposes.
Props dd32, DavidAnderson, meloniq, markjaquith, DrewAPicture, mweichert, design_dolphin, filosofo, sean212, nhuja, JeroenReumkens, infolu, dingdang, joyously, earnjam, williampatton, grapplerulrich, markparnell, apedog, afragen, miqrogroove, rmccue, crazycoders, jdgrimes, damonganto, joostdevalk, jorbin, georgestephanis, khromov, GeekStreetWP, jb510, Rarst, juliobox, Ipstenu, mikejolley, Otto42, gMagicScott, TJNowell, GaryJ, knutsp, mordauk, nvartolomei, aspexi, chriscct7, benoitchantre, ryno267, lev0, gregorlove, dougwollison, SergeyBiryukov.
See #14179, #23318, #32101.
Built from https://develop.svn.wordpress.org/trunk@50921
git-svn-id: http://core.svn.wordpress.org/trunk@50530 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2021-05-17 13:04:01 -04:00
// Is it valid? We require at least a version.
if ( ! isset ( $update -> version ) ) {
continue ;
}
// These should remain constant.
$update -> id = $plugin_data [ 'UpdateURI' ];
$update -> plugin = $plugin_file ;
// WordPress needs the version field specified as 'new_version'.
if ( ! isset ( $update -> new_version ) ) {
$update -> new_version = $update -> version ;
}
// Handle any translation updates.
if ( ! empty ( $update -> translations ) ) {
foreach ( $update -> translations as $translation ) {
if ( isset ( $translation [ 'language' ], $translation [ 'package' ] ) ) {
$translation [ 'type' ] = 'plugin' ;
$translation [ 'slug' ] = isset ( $update -> slug ) ? $update -> slug : $update -> id ;
$updates -> translations [] = $translation ;
}
2016-01-06 02:53:26 -05:00
}
}
2020-05-09 08:52:10 -04:00
Plugins: Add support for `Update URI` header.
This allows third-party plugins to avoid accidentally being overwritten with an update of a plugin of a similar name from the WordPress.org Plugin Directory.
Additionally, introduce the `update_plugins_{$hostname}` filter, which third-party plugins can use to offer updates for a given hostname.
If set, the `Update URI` header field should be a URI and have a unique hostname.
Some examples include:
* `https://wordpress.org/plugins/example-plugin/`
* `https://example.com/my-plugin/`
* `my-custom-plugin-name`
`Update URI: false` also works, and unless there is code handling the `false` hostname, the plugin will never get an update notification.
If the header is present, the WordPress.org API will currently only return updates for the plugin if it matches the following format:
* `https://wordpress.org/plugins/{$slug}/`
* `w.org/plugin/{$slug}`
If the header has any other value, the API will not return a result and will ignore the plugin for update purposes.
Props dd32, DavidAnderson, meloniq, markjaquith, DrewAPicture, mweichert, design_dolphin, filosofo, sean212, nhuja, JeroenReumkens, infolu, dingdang, joyously, earnjam, williampatton, grapplerulrich, markparnell, apedog, afragen, miqrogroove, rmccue, crazycoders, jdgrimes, damonganto, joostdevalk, jorbin, georgestephanis, khromov, GeekStreetWP, jb510, Rarst, juliobox, Ipstenu, mikejolley, Otto42, gMagicScott, TJNowell, GaryJ, knutsp, mordauk, nvartolomei, aspexi, chriscct7, benoitchantre, ryno267, lev0, gregorlove, dougwollison, SergeyBiryukov.
See #14179, #23318, #32101.
Built from https://develop.svn.wordpress.org/trunk@50921
git-svn-id: http://core.svn.wordpress.org/trunk@50530 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2021-05-17 13:04:01 -04:00
unset ( $updates -> no_update [ $plugin_file ], $updates -> response [ $plugin_file ] );
2020-05-09 08:52:10 -04:00
Plugins: Add support for `Update URI` header.
This allows third-party plugins to avoid accidentally being overwritten with an update of a plugin of a similar name from the WordPress.org Plugin Directory.
Additionally, introduce the `update_plugins_{$hostname}` filter, which third-party plugins can use to offer updates for a given hostname.
If set, the `Update URI` header field should be a URI and have a unique hostname.
Some examples include:
* `https://wordpress.org/plugins/example-plugin/`
* `https://example.com/my-plugin/`
* `my-custom-plugin-name`
`Update URI: false` also works, and unless there is code handling the `false` hostname, the plugin will never get an update notification.
If the header is present, the WordPress.org API will currently only return updates for the plugin if it matches the following format:
* `https://wordpress.org/plugins/{$slug}/`
* `w.org/plugin/{$slug}`
If the header has any other value, the API will not return a result and will ignore the plugin for update purposes.
Props dd32, DavidAnderson, meloniq, markjaquith, DrewAPicture, mweichert, design_dolphin, filosofo, sean212, nhuja, JeroenReumkens, infolu, dingdang, joyously, earnjam, williampatton, grapplerulrich, markparnell, apedog, afragen, miqrogroove, rmccue, crazycoders, jdgrimes, damonganto, joostdevalk, jorbin, georgestephanis, khromov, GeekStreetWP, jb510, Rarst, juliobox, Ipstenu, mikejolley, Otto42, gMagicScott, TJNowell, GaryJ, knutsp, mordauk, nvartolomei, aspexi, chriscct7, benoitchantre, ryno267, lev0, gregorlove, dougwollison, SergeyBiryukov.
See #14179, #23318, #32101.
Built from https://develop.svn.wordpress.org/trunk@50921
git-svn-id: http://core.svn.wordpress.org/trunk@50530 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2021-05-17 13:04:01 -04:00
if ( version_compare ( $update -> new_version , $plugin_data [ 'Version' ], '>' ) ) {
$updates -> response [ $plugin_file ] = $update ;
} else {
$updates -> no_update [ $plugin_file ] = $update ;
}
2014-07-18 16:49:17 -04:00
}
2020-05-09 08:52:10 -04:00
2023-09-12 11:23:18 -04:00
$sanitize_plugin_update_payload = static function ( & $item ) {
Plugins: Add support for `Update URI` header.
This allows third-party plugins to avoid accidentally being overwritten with an update of a plugin of a similar name from the WordPress.org Plugin Directory.
Additionally, introduce the `update_plugins_{$hostname}` filter, which third-party plugins can use to offer updates for a given hostname.
If set, the `Update URI` header field should be a URI and have a unique hostname.
Some examples include:
* `https://wordpress.org/plugins/example-plugin/`
* `https://example.com/my-plugin/`
* `my-custom-plugin-name`
`Update URI: false` also works, and unless there is code handling the `false` hostname, the plugin will never get an update notification.
If the header is present, the WordPress.org API will currently only return updates for the plugin if it matches the following format:
* `https://wordpress.org/plugins/{$slug}/`
* `w.org/plugin/{$slug}`
If the header has any other value, the API will not return a result and will ignore the plugin for update purposes.
Props dd32, DavidAnderson, meloniq, markjaquith, DrewAPicture, mweichert, design_dolphin, filosofo, sean212, nhuja, JeroenReumkens, infolu, dingdang, joyously, earnjam, williampatton, grapplerulrich, markparnell, apedog, afragen, miqrogroove, rmccue, crazycoders, jdgrimes, damonganto, joostdevalk, jorbin, georgestephanis, khromov, GeekStreetWP, jb510, Rarst, juliobox, Ipstenu, mikejolley, Otto42, gMagicScott, TJNowell, GaryJ, knutsp, mordauk, nvartolomei, aspexi, chriscct7, benoitchantre, ryno267, lev0, gregorlove, dougwollison, SergeyBiryukov.
See #14179, #23318, #32101.
Built from https://develop.svn.wordpress.org/trunk@50921
git-svn-id: http://core.svn.wordpress.org/trunk@50530 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2021-05-17 13:04:01 -04:00
$item = ( object ) $item ;
2008-07-11 18:04:03 -04:00
Plugins: Add support for `Update URI` header.
This allows third-party plugins to avoid accidentally being overwritten with an update of a plugin of a similar name from the WordPress.org Plugin Directory.
Additionally, introduce the `update_plugins_{$hostname}` filter, which third-party plugins can use to offer updates for a given hostname.
If set, the `Update URI` header field should be a URI and have a unique hostname.
Some examples include:
* `https://wordpress.org/plugins/example-plugin/`
* `https://example.com/my-plugin/`
* `my-custom-plugin-name`
`Update URI: false` also works, and unless there is code handling the `false` hostname, the plugin will never get an update notification.
If the header is present, the WordPress.org API will currently only return updates for the plugin if it matches the following format:
* `https://wordpress.org/plugins/{$slug}/`
* `w.org/plugin/{$slug}`
If the header has any other value, the API will not return a result and will ignore the plugin for update purposes.
Props dd32, DavidAnderson, meloniq, markjaquith, DrewAPicture, mweichert, design_dolphin, filosofo, sean212, nhuja, JeroenReumkens, infolu, dingdang, joyously, earnjam, williampatton, grapplerulrich, markparnell, apedog, afragen, miqrogroove, rmccue, crazycoders, jdgrimes, damonganto, joostdevalk, jorbin, georgestephanis, khromov, GeekStreetWP, jb510, Rarst, juliobox, Ipstenu, mikejolley, Otto42, gMagicScott, TJNowell, GaryJ, knutsp, mordauk, nvartolomei, aspexi, chriscct7, benoitchantre, ryno267, lev0, gregorlove, dougwollison, SergeyBiryukov.
See #14179, #23318, #32101.
Built from https://develop.svn.wordpress.org/trunk@50921
git-svn-id: http://core.svn.wordpress.org/trunk@50530 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2021-05-17 13:04:01 -04:00
unset ( $item -> translations , $item -> compatibility );
return $item ;
};
array_walk ( $updates -> response , $sanitize_plugin_update_payload );
array_walk ( $updates -> no_update , $sanitize_plugin_update_payload );
2008-07-11 18:04:03 -04:00
Plugins: Add support for `Update URI` header.
This allows third-party plugins to avoid accidentally being overwritten with an update of a plugin of a similar name from the WordPress.org Plugin Directory.
Additionally, introduce the `update_plugins_{$hostname}` filter, which third-party plugins can use to offer updates for a given hostname.
If set, the `Update URI` header field should be a URI and have a unique hostname.
Some examples include:
* `https://wordpress.org/plugins/example-plugin/`
* `https://example.com/my-plugin/`
* `my-custom-plugin-name`
`Update URI: false` also works, and unless there is code handling the `false` hostname, the plugin will never get an update notification.
If the header is present, the WordPress.org API will currently only return updates for the plugin if it matches the following format:
* `https://wordpress.org/plugins/{$slug}/`
* `w.org/plugin/{$slug}`
If the header has any other value, the API will not return a result and will ignore the plugin for update purposes.
Props dd32, DavidAnderson, meloniq, markjaquith, DrewAPicture, mweichert, design_dolphin, filosofo, sean212, nhuja, JeroenReumkens, infolu, dingdang, joyously, earnjam, williampatton, grapplerulrich, markparnell, apedog, afragen, miqrogroove, rmccue, crazycoders, jdgrimes, damonganto, joostdevalk, jorbin, georgestephanis, khromov, GeekStreetWP, jb510, Rarst, juliobox, Ipstenu, mikejolley, Otto42, gMagicScott, TJNowell, GaryJ, knutsp, mordauk, nvartolomei, aspexi, chriscct7, benoitchantre, ryno267, lev0, gregorlove, dougwollison, SergeyBiryukov.
See #14179, #23318, #32101.
Built from https://develop.svn.wordpress.org/trunk@50921
git-svn-id: http://core.svn.wordpress.org/trunk@50530 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2021-05-17 13:04:01 -04:00
set_site_transient ( 'update_plugins' , $updates );
2008-07-11 18:04:03 -04:00
}
2008-08-01 00:26:32 -04:00
2008-09-15 12:21:15 -04:00
/**
2020-06-26 14:34:03 -04:00
* Checks for available updates to themes based on the latest versions hosted on WordPress . org .
*
* Despite its name this function does not actually perform any updates , it only checks for available updates .
2008-09-15 12:21:15 -04:00
*
2020-06-16 17:07:14 -04:00
* A list of all themes installed is sent to WP , along with the site locale .
*
* Checks against the 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
2020-06-16 17:07:14 -04:00
*
2020-02-09 22:30:06 -05:00
* @ global string $wp_version The WordPress version string .
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
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 ();
2017-11-30 18:11:00 -05: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' );
2020-05-09 08:52:10 -04:00
2017-11-30 18:11:00 -05:00
if ( ! is_object ( $last_update ) ) {
2022-11-29 10:51:14 -05:00
$last_update = new stdClass ();
2017-11-30 18:11:00 -05:00
}
2008-09-15 12:21:15 -04:00
2019-07-02 19:42:58 -04:00
$themes = array ();
$checked = array ();
$request = array ();
2010-07-22 09:24:41 -04:00
2022-01-20 18:53:05 -05:00
// Put slug of active 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 ) {
2017-11-30 18:11:00 -05:00
$checked [ $theme -> get_stylesheet () ] = $theme -> get ( 'Version' );
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
$themes [ $theme -> get_stylesheet () ] = array (
2017-11-30 18:11:00 -05:00
'Name' => $theme -> get ( 'Name' ),
'Title' => $theme -> get ( 'Name' ),
'Version' => $theme -> get ( 'Version' ),
'Author' => $theme -> get ( 'Author' ),
'Author URI' => $theme -> get ( 'AuthorURI' ),
Themes: Add support for `Update URI` header.
This allows third-party themes to avoid accidentally being overwritten with an update of a theme of a similar name from the WordPress.org Theme Directory.
Additionally, introduce the `update_themes_{$hostname}` filter, which third-party themes can use to offer updates for a given hostname.
If set, the `Update URI` header field should be a URI and have a unique hostname.
Some examples include:
* `https://wordpress.org/themes/example-theme/`
* `https://example.com/my-theme/`
* `my-custom-theme-name`
`Update URI: false` also works, and unless there is code handling the `false` hostname, the theme will never get an update notification.
If the header is present, the WordPress.org API will currently only return updates for the theme if it matches the following format:
* `https://wordpress.org/themes/{$slug}/`
* `w.org/theme/{$slug}`
If the header has any other value, the API will not return a result and will ignore the theme for update purposes.
Follow-up to [50921].
Props dd32, meloniq, costdev, audrasjb, DavidAnderson, markjaquith, DrewAPicture, mweichert, design_dolphin, filosofo, sean212, nhuja, JeroenReumkens, infolu, dingdang, joyously, earnjam, williampatton, grapplerulrich, markparnell, apedog, afragen, miqrogroove, rmccue, crazycoders, jdgrimes, damonganto, joostdevalk, jorbin, georgestephanis, khromov, GeekStreetWP, jb510, Rarst, juliobox, Ipstenu, mikejolley, Otto42, gMagicScott, TJNowell, GaryJ, knutsp, mordauk, nvartolomei, aspexi, chriscct7, benoitchantre, ryno267, lev0, gregorlove, dougwollison, leemon, SergeyBiryukov.
See #14179, #23318, #32101.
Built from https://develop.svn.wordpress.org/trunk@53933
git-svn-id: http://core.svn.wordpress.org/trunk@53492 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2022-08-23 13:48:15 -04:00
'UpdateURI' => $theme -> get ( 'UpdateURI' ),
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
'Template' => $theme -> get_template (),
'Stylesheet' => $theme -> get_stylesheet (),
);
2008-09-15 12:21:15 -04:00
}
2017-05-06 10:30:40 -04:00
$doing_cron = wp_doing_cron ();
2012-01-05 14:49:47 -05:00
// Check for update on a different schedule, depending on the page.
switch ( current_filter () ) {
2017-11-30 18:11:00 -05:00
case 'upgrader_process_complete' :
2013-09-22 22:08:10 -04:00
$timeout = 0 ;
break ;
2017-11-30 18:11:00 -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 ;
2017-11-30 18:11:00 -05:00
case 'load-themes.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 ;
2017-11-30 18:11:00 -05:00
default :
2018-01-23 23:17:30 -05:00
if ( $doing_cron ) {
$timeout = 2 * HOUR_IN_SECONDS ;
} 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 ;
2020-05-09 08:52:10 -04:00
2012-01-05 14:49:47 -05:00
foreach ( $checked as $slug => $v ) {
2020-10-08 17:15:13 -04:00
if ( ! isset ( $last_update -> checked [ $slug ] ) || ( string ) $last_update -> checked [ $slug ] !== ( string ) $v ) {
2011-11-16 02:23:15 -05:00
$theme_changed = true ;
2017-11-30 18:11:00 -05:00
}
2012-01-05 14:49:47 -05:00
}
2017-11-30 18:11:00 -05:00
if ( isset ( $last_update -> response ) && is_array ( $last_update -> response ) ) {
2012-01-05 14:49:47 -05:00
foreach ( $last_update -> response as $slug => $update_details ) {
2017-11-30 18:11:00 -05:00
if ( ! isset ( $checked [ $slug ] ) ) {
2012-01-05 14:49:47 -05:00
$theme_changed = true ;
break ;
}
2011-11-16 02:23:15 -05:00
}
2009-07-14 04:34:39 -04:00
}
2020-01-28 19:45:18 -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
2020-01-28 19:45:18 -05: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 ;
2016-02-23 11:17:26 -05:00
$locales = array_values ( get_available_languages () );
2016-03-16 12:15:28 -04:00
2013-09-28 00:18:12 -04:00
/**
2016-05-22 14:50:28 -04:00
* Filters the locales requested for theme translations .
2013-09-28 00:18:12 -04:00
*
* @ since 3.7 . 0
2016-03-10 18:01:26 -05:00
* @ since 4.5 . 0 The default value of the `$locales` parameter changed to include all locales .
2013-09-28 00:18:12 -04:00
*
2022-09-21 16:24:12 -04:00
* @ param string [] $locales Theme locales . Default is all available locales of the site .
2013-09-28 00:18:12 -04:00
*/
2016-02-23 11:17:26 -05:00
$locales = apply_filters ( 'themes_update_check_locales' , $locales );
$locales = array_unique ( $locales );
2013-09-28 00:18:12 -04:00
2017-05-06 10:30:40 -04:00
if ( $doing_cron ) {
Coding Standards: Clarify time units for various timeout or expiration values.
This changeset implements a clearer and more consistent timeout/duration/expiration format. It updates time durations used in various files, as per WordPress coding standards:
- If the value can be represented as an integer (not a fractional) number of minutes (hours, etc.), use the appropriate constant (e.g.: `MINUTE_IN_SECONDS`) multiplied by that number.
- Otherwise, keep the value as is and add a comment with the units for clarity.
Follow-up to [11823], [13177], [21996], [37747], [53714].
Props hztyfoon, audrasjb, arrasel403, krupalpanchal, GaryJ, SergeyBiryukov, peterwilsoncc, rudlinkon, costdev, robinwpdeveloper.
Fixes #56293.
See #55647.
Built from https://develop.svn.wordpress.org/trunk@54113
git-svn-id: http://core.svn.wordpress.org/trunk@53672 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2022-09-09 04:16:18 -04:00
$timeout = 30 ; // 30 seconds.
2014-06-19 19:21:16 -04:00
} else {
2020-01-28 19:45:18 -05: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 (
2017-11-30 18:11:00 -05:00
'timeout' => $timeout ,
'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
),
2024-07-26 20:27:16 -04:00
'user-agent' => 'WordPress/' . wp_get_wp_version () . '; ' . home_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
}
2019-07-02 19:42:58 -04:00
$url = 'http://api.wordpress.org/themes/update-check/1.1/' ;
$http_url = $url ;
$ssl = wp_http_supports ( array ( 'ssl' ) );
2020-05-09 08:52:10 -04:00
2019-07-02 19:42:58 -04:00
if ( $ssl ) {
2013-09-09 03:54:11 -04:00
$url = set_url_scheme ( $url , 'https' );
2017-11-30 18:11:00 -05:00
}
2013-09-09 03:54:11 -04:00
$raw_response = wp_remote_post ( $url , $options );
2020-05-09 08:52:10 -04:00
2013-10-27 17:09:10 -04:00
if ( $ssl && is_wp_error ( $raw_response ) ) {
Code Modernization: Use wp_trigger_error() instead of trigger_error().
Replaces `trigger_error()` with `wp_trigger_error()`.
The usage of `wp_trigger_error()` avoids generating `E_USER` family errors unless `WP_DEBUG` is on. In doing so, users should not see these messages in normal production.
Notes:
* Removes `E_USER_NOTICE` when passed as an argumnent, as it's the default error level.
* An empty string is passed for the function name when its name is already in the error message or does not add value to the error message.
* Externally maintained libraries are not included.
Follow-up to [55204], [25956], [29630], [38883], [52062], [52049], [54272], [38883], [55245], [51599], [14452], [38883], [24976].
Props prasadkarmalkar, rajinsharwar, thelovekesh, hellofromTonya, swissspidy.
Fixes #59652.
Built from https://develop.svn.wordpress.org/trunk@58409
git-svn-id: http://core.svn.wordpress.org/trunk@57858 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2024-06-13 16:50:14 -04:00
wp_trigger_error (
__FUNCTION__ ,
2016-11-20 20:52:32 -05:00
sprintf (
2019-09-02 20:41:05 -04:00
/* translators: %s: Support forums URL. */
2016-11-20 20:52:32 -05:00
__ ( '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="%s">support forums</a>.' ),
2019-05-25 10:24:50 -04:00
__ ( 'https://wordpress.org/support/forums/' )
2016-11-20 20:52:32 -05:00
) . ' ' . __ ( '(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
2020-05-09 08:52:10 -04:00
if ( is_wp_error ( $raw_response ) || 200 !== wp_remote_retrieve_response_code ( $raw_response ) ) {
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-09-15 12:21:15 -04:00
2022-11-29 10:51:14 -05:00
$new_update = new stdClass ();
2013-01-04 05:13:51 -05:00
$new_update -> last_checked = time ();
2017-11-30 18:11:00 -05:00
$new_update -> checked = $checked ;
2011-04-07 05:56:20 -04:00
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' ];
2020-07-29 16:01:08 -04:00
$new_update -> no_update = $response [ 'no_update' ];
2013-09-21 00:08:10 -04:00
$new_update -> translations = $response [ 'translations' ];
}
2008-09-15 12:21:15 -04:00
Themes: Add support for `Update URI` header.
This allows third-party themes to avoid accidentally being overwritten with an update of a theme of a similar name from the WordPress.org Theme Directory.
Additionally, introduce the `update_themes_{$hostname}` filter, which third-party themes can use to offer updates for a given hostname.
If set, the `Update URI` header field should be a URI and have a unique hostname.
Some examples include:
* `https://wordpress.org/themes/example-theme/`
* `https://example.com/my-theme/`
* `my-custom-theme-name`
`Update URI: false` also works, and unless there is code handling the `false` hostname, the theme will never get an update notification.
If the header is present, the WordPress.org API will currently only return updates for the theme if it matches the following format:
* `https://wordpress.org/themes/{$slug}/`
* `w.org/theme/{$slug}`
If the header has any other value, the API will not return a result and will ignore the theme for update purposes.
Follow-up to [50921].
Props dd32, meloniq, costdev, audrasjb, DavidAnderson, markjaquith, DrewAPicture, mweichert, design_dolphin, filosofo, sean212, nhuja, JeroenReumkens, infolu, dingdang, joyously, earnjam, williampatton, grapplerulrich, markparnell, apedog, afragen, miqrogroove, rmccue, crazycoders, jdgrimes, damonganto, joostdevalk, jorbin, georgestephanis, khromov, GeekStreetWP, jb510, Rarst, juliobox, Ipstenu, mikejolley, Otto42, gMagicScott, TJNowell, GaryJ, knutsp, mordauk, nvartolomei, aspexi, chriscct7, benoitchantre, ryno267, lev0, gregorlove, dougwollison, leemon, SergeyBiryukov.
See #14179, #23318, #32101.
Built from https://develop.svn.wordpress.org/trunk@53933
git-svn-id: http://core.svn.wordpress.org/trunk@53492 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2022-08-23 13:48:15 -04:00
// Support updates for any themes using the `Update URI` header field.
foreach ( $themes as $theme_stylesheet => $theme_data ) {
if ( ! $theme_data [ 'UpdateURI' ] || isset ( $new_update -> response [ $theme_stylesheet ] ) ) {
continue ;
}
2023-08-30 16:25:18 -04:00
$hostname = wp_parse_url ( sanitize_url ( $theme_data [ 'UpdateURI' ] ), PHP_URL_HOST );
Themes: Add support for `Update URI` header.
This allows third-party themes to avoid accidentally being overwritten with an update of a theme of a similar name from the WordPress.org Theme Directory.
Additionally, introduce the `update_themes_{$hostname}` filter, which third-party themes can use to offer updates for a given hostname.
If set, the `Update URI` header field should be a URI and have a unique hostname.
Some examples include:
* `https://wordpress.org/themes/example-theme/`
* `https://example.com/my-theme/`
* `my-custom-theme-name`
`Update URI: false` also works, and unless there is code handling the `false` hostname, the theme will never get an update notification.
If the header is present, the WordPress.org API will currently only return updates for the theme if it matches the following format:
* `https://wordpress.org/themes/{$slug}/`
* `w.org/theme/{$slug}`
If the header has any other value, the API will not return a result and will ignore the theme for update purposes.
Follow-up to [50921].
Props dd32, meloniq, costdev, audrasjb, DavidAnderson, markjaquith, DrewAPicture, mweichert, design_dolphin, filosofo, sean212, nhuja, JeroenReumkens, infolu, dingdang, joyously, earnjam, williampatton, grapplerulrich, markparnell, apedog, afragen, miqrogroove, rmccue, crazycoders, jdgrimes, damonganto, joostdevalk, jorbin, georgestephanis, khromov, GeekStreetWP, jb510, Rarst, juliobox, Ipstenu, mikejolley, Otto42, gMagicScott, TJNowell, GaryJ, knutsp, mordauk, nvartolomei, aspexi, chriscct7, benoitchantre, ryno267, lev0, gregorlove, dougwollison, leemon, SergeyBiryukov.
See #14179, #23318, #32101.
Built from https://develop.svn.wordpress.org/trunk@53933
git-svn-id: http://core.svn.wordpress.org/trunk@53492 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2022-08-23 13:48:15 -04:00
/**
* Filters the update response for a given theme hostname .
*
* The dynamic portion of the hook name , `$hostname` , refers to the hostname
* of the URI specified in the `Update URI` header field .
*
* @ since 6.1 . 0
*
* @ param array | false $update {
* The theme update data with the latest details . Default false .
*
* @ type string $id Optional . ID of the theme for update purposes , should be a URI
* specified in the `Update URI` header field .
* @ type string $theme Directory name of the theme .
* @ type string $version The version of the theme .
* @ type string $url The URL for details of the theme .
* @ type string $package Optional . The update ZIP for the theme .
* @ type string $tested Optional . The version of WordPress the theme is tested against .
* @ type string $requires_php Optional . The version of PHP which the theme requires .
* @ type bool $autoupdate Optional . Whether the theme should automatically update .
* @ type array $translations {
* Optional . List of translation updates for the theme .
*
* @ type string $language The language the translation update is for .
* @ type string $version The version of the theme this translation is for .
* This is not the version of the language file .
* @ type string $updated The update timestamp of the translation file .
* Should be a date in the `YYYY-MM-DD HH:MM:SS` format .
* @ type string $package The ZIP location containing the translation update .
* @ type string $autoupdate Whether the translation should be automatically installed .
* }
* }
* @ param array $theme_data Theme headers .
* @ param string $theme_stylesheet Theme stylesheet .
2022-09-21 16:24:12 -04:00
* @ param string [] $locales Installed locales to look up translations for .
Themes: Add support for `Update URI` header.
This allows third-party themes to avoid accidentally being overwritten with an update of a theme of a similar name from the WordPress.org Theme Directory.
Additionally, introduce the `update_themes_{$hostname}` filter, which third-party themes can use to offer updates for a given hostname.
If set, the `Update URI` header field should be a URI and have a unique hostname.
Some examples include:
* `https://wordpress.org/themes/example-theme/`
* `https://example.com/my-theme/`
* `my-custom-theme-name`
`Update URI: false` also works, and unless there is code handling the `false` hostname, the theme will never get an update notification.
If the header is present, the WordPress.org API will currently only return updates for the theme if it matches the following format:
* `https://wordpress.org/themes/{$slug}/`
* `w.org/theme/{$slug}`
If the header has any other value, the API will not return a result and will ignore the theme for update purposes.
Follow-up to [50921].
Props dd32, meloniq, costdev, audrasjb, DavidAnderson, markjaquith, DrewAPicture, mweichert, design_dolphin, filosofo, sean212, nhuja, JeroenReumkens, infolu, dingdang, joyously, earnjam, williampatton, grapplerulrich, markparnell, apedog, afragen, miqrogroove, rmccue, crazycoders, jdgrimes, damonganto, joostdevalk, jorbin, georgestephanis, khromov, GeekStreetWP, jb510, Rarst, juliobox, Ipstenu, mikejolley, Otto42, gMagicScott, TJNowell, GaryJ, knutsp, mordauk, nvartolomei, aspexi, chriscct7, benoitchantre, ryno267, lev0, gregorlove, dougwollison, leemon, SergeyBiryukov.
See #14179, #23318, #32101.
Built from https://develop.svn.wordpress.org/trunk@53933
git-svn-id: http://core.svn.wordpress.org/trunk@53492 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2022-08-23 13:48:15 -04:00
*/
$update = apply_filters ( " update_themes_ { $hostname } " , false , $theme_data , $theme_stylesheet , $locales );
if ( ! $update ) {
continue ;
}
$update = ( object ) $update ;
// Is it valid? We require at least a version.
if ( ! isset ( $update -> version ) ) {
continue ;
}
// This should remain constant.
$update -> id = $theme_data [ 'UpdateURI' ];
// WordPress needs the version field specified as 'new_version'.
if ( ! isset ( $update -> new_version ) ) {
$update -> new_version = $update -> version ;
}
// Handle any translation updates.
if ( ! empty ( $update -> translations ) ) {
foreach ( $update -> translations as $translation ) {
if ( isset ( $translation [ 'language' ], $translation [ 'package' ] ) ) {
$translation [ 'type' ] = 'theme' ;
$translation [ 'slug' ] = isset ( $update -> theme ) ? $update -> theme : $update -> id ;
$new_update -> translations [] = $translation ;
}
}
}
unset ( $new_update -> no_update [ $theme_stylesheet ], $new_update -> response [ $theme_stylesheet ] );
if ( version_compare ( $update -> new_version , $theme_data [ 'Version' ], '>' ) ) {
$new_update -> response [ $theme_stylesheet ] = ( array ) $update ;
} else {
$new_update -> no_update [ $theme_stylesheet ] = ( array ) $update ;
}
}
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
*
2020-06-26 14:34:03 -04:00
* Updates WordPress core plus any plugins and themes that have automatic updates enabled .
*
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 () {
Coding Standards: Replace `include_once` with `require_once` for required files.
Per [https://developer.wordpress.org/coding-standards/wordpress-coding-standards/php/#writing-include-require-statements WordPress PHP coding standards], it is ''strongly recommended'' to use `require[_once]` for unconditional includes. When using `include[_once]`, PHP will throw a warning when the file is not found but will continue execution, which will almost certainly lead to other errors/warnings/notices being thrown if your application depends on the file loaded, potentially leading to security leaks. For that reason, `require[_once]` is generally the better choice as it will throw a `Fatal Error` if the file cannot be found.
Follow-up to [1674], [1812], [1964], [6779], [8540], [10521], [11005], [11911], [16065], [16149], [25421], [25466], [25823], [37714], [42981], [45448], [47198], [54276], [55633].
Props kausaralm, SergeyBiryukov.
See #57839.
Built from https://develop.svn.wordpress.org/trunk@55641
git-svn-id: http://core.svn.wordpress.org/trunk@55153 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2023-04-09 07:57:22 -04:00
require_once ABSPATH . 'wp-admin/includes/admin.php' ;
2020-02-06 01:33:11 -05:00
require_once ABSPATH . 'wp-admin/includes/class-wp-upgrader.php' ;
2013-09-13 02:19:12 -04:00
2022-11-29 10:51:14 -05: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
*
2018-03-22 16:27:32 -04:00
* @ return object [] Array of translation objects that have available updates .
2013-10-16 10:34:10 -04:00
*/
function wp_get_translation_updates () {
2017-11-30 18:11:00 -05:00
$updates = array ();
$transients = array (
'update_core' => 'core' ,
'update_plugins' => 'plugin' ,
'update_themes' => 'theme' ,
);
2020-05-09 08:52:10 -04:00
2013-10-16 10:34:10 -04:00
foreach ( $transients as $transient => $type ) {
$transient = get_site_transient ( $transient );
2020-05-09 08:52:10 -04:00
2017-11-30 18:11:00 -05:00
if ( empty ( $transient -> translations ) ) {
2013-10-16 10:34:10 -04:00
continue ;
2017-11-30 18:11:00 -05:00
}
2013-10-16 10:34:10 -04:00
foreach ( $transient -> translations as $translation ) {
$updates [] = ( object ) $translation ;
}
}
2020-05-09 08:52:10 -04:00
2013-10-16 10:34:10 -04:00
return $updates ;
}
2013-11-11 08:32:10 -05:00
/**
2022-09-09 04:58:09 -04:00
* Collects counts and UI strings for available updates .
2011-07-26 14:39:57 -04:00
*
* @ since 3.3 . 0
*
* @ return array
*/
function wp_get_update_data () {
2017-11-30 18:11:00 -05:00
$counts = array (
'plugins' => 0 ,
'themes' => 0 ,
'wordpress' => 0 ,
'translations' => 0 ,
);
2011-07-26 14:39:57 -04:00
2019-07-02 19:42:58 -04:00
$plugins = current_user_can ( 'update_plugins' );
2020-05-09 08:52:10 -04:00
2019-07-02 19:42:58 -04:00
if ( $plugins ) {
2011-07-26 14:39:57 -04:00
$update_plugins = get_site_transient ( 'update_plugins' );
2020-05-09 08:52:10 -04:00
2017-11-30 18:11:00 -05:00
if ( ! empty ( $update_plugins -> response ) ) {
2011-07-26 14:39:57 -04:00
$counts [ 'plugins' ] = count ( $update_plugins -> response );
2017-11-30 18:11:00 -05:00
}
2011-07-26 14:39:57 -04:00
}
2019-07-02 19:42:58 -04:00
$themes = current_user_can ( 'update_themes' );
2020-05-09 08:52:10 -04:00
2019-07-02 19:42:58 -04:00
if ( $themes ) {
2011-07-26 14:39:57 -04:00
$update_themes = get_site_transient ( 'update_themes' );
2020-05-09 08:52:10 -04:00
2017-11-30 18:11:00 -05:00
if ( ! empty ( $update_themes -> response ) ) {
2011-07-26 14:39:57 -04:00
$counts [ 'themes' ] = count ( $update_themes -> response );
2017-11-30 18:11:00 -05:00
}
2011-07-26 14:39:57 -04:00
}
2019-07-02 19:42:58 -04:00
$core = current_user_can ( 'update_core' );
2020-05-09 08:52:10 -04:00
2019-07-02 19:42:58 -04:00
if ( $core && function_exists ( 'get_core_updates' ) ) {
2017-11-30 18:11:00 -05:00
$update_wordpress = get_core_updates ( array ( 'dismissed' => false ) );
2020-05-09 08:52:10 -04:00
2020-04-04 23:02:11 -04:00
if ( ! empty ( $update_wordpress )
&& ! in_array ( $update_wordpress [ 0 ] -> response , array ( 'development' , 'latest' ), true )
&& current_user_can ( 'update_core' )
) {
2011-07-26 14:39:57 -04:00
$counts [ 'wordpress' ] = 1 ;
2017-11-30 18:11:00 -05:00
}
2011-07-26 14:39:57 -04:00
}
2017-11-30 18:11:00 -05:00
if ( ( $core || $plugins || $themes ) && wp_get_translation_updates () ) {
2013-10-16 10:34:10 -04:00
$counts [ 'translations' ] = 1 ;
2017-11-30 18:11:00 -05:00
}
2013-10-16 10:34:10 -04:00
$counts [ 'total' ] = $counts [ 'plugins' ] + $counts [ 'themes' ] + $counts [ 'wordpress' ] + $counts [ 'translations' ];
2017-11-30 18:11:00 -05:00
$titles = array ();
2020-05-09 08:52:10 -04:00
2016-11-20 21:46:30 -05:00
if ( $counts [ 'wordpress' ] ) {
2019-09-02 20:41:05 -04:00
/* translators: %d: Number of available WordPress updates. */
2017-11-30 18:11:00 -05:00
$titles [ 'wordpress' ] = sprintf ( __ ( '%d WordPress Update' ), $counts [ 'wordpress' ] );
2016-11-20 21:46:30 -05:00
}
2020-05-09 08:52:10 -04:00
2016-11-20 21:46:30 -05:00
if ( $counts [ 'plugins' ] ) {
2019-09-02 20:41:05 -04:00
/* translators: %d: Number of available plugin updates. */
2012-09-16 16:51:51 -04:00
$titles [ 'plugins' ] = sprintf ( _n ( '%d Plugin Update' , '%d Plugin Updates' , $counts [ 'plugins' ] ), $counts [ 'plugins' ] );
2016-11-20 21:46:30 -05:00
}
2020-05-09 08:52:10 -04:00
2016-11-20 21:46:30 -05:00
if ( $counts [ 'themes' ] ) {
2019-09-02 20:41:05 -04:00
/* translators: %d: Number of available theme updates. */
2012-09-16 16:51:51 -04:00
$titles [ 'themes' ] = sprintf ( _n ( '%d Theme Update' , '%d Theme Updates' , $counts [ 'themes' ] ), $counts [ 'themes' ] );
2016-11-20 21:46:30 -05:00
}
2020-05-09 08:52:10 -04:00
2016-11-20 21:46:30 -05:00
if ( $counts [ 'translations' ] ) {
2013-10-16 10:34:10 -04:00
$titles [ 'translations' ] = __ ( 'Translation Updates' );
2016-11-20 21:46:30 -05:00
}
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
2017-11-30 18:11:00 -05:00
$update_data = array (
'counts' => $counts ,
'title' => $update_title ,
);
2013-10-06 11:31:09 -04:00
/**
2016-05-22 14:50:28 -04:00
* Filters the returned array of update data for plugins , themes , and WordPress core .
2013-10-06 11:31:09 -04:00
*
* @ 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
/**
2015-12-17 11:38:26 -05:00
* Determines whether core should be updated .
*
* @ since 2.8 . 0
*
2020-02-09 22:30:06 -05:00
* @ global string $wp_version The WordPress version string .
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
function _maybe_update_core () {
2010-01-08 15:49:55 -05:00
$current = get_site_transient ( 'update_core' );
2009-02-16 19:13:25 -05:00
2020-05-09 08:52:10 -04:00
if ( isset ( $current -> last_checked , $current -> version_checked )
&& 12 * HOUR_IN_SECONDS > ( time () - $current -> last_checked )
2024-07-26 20:27:16 -04:00
&& wp_get_wp_version () === $current -> version_checked
2020-05-09 08:52:10 -04:00
) {
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
}
2020-05-09 08:52:10 -04:00
2009-02-16 19:13:25 -05:00
wp_version_check ();
}
2008-09-18 13:32:18 -04:00
/**
2022-09-09 04:58:09 -04:00
* Checks the last time plugins were run before checking plugin versions .
2008-09-18 13:32:18 -04:00
*
* 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' );
2020-05-09 08:52:10 -04:00
if ( isset ( $current -> last_checked )
&& 12 * HOUR_IN_SECONDS > ( time () - $current -> last_checked )
) {
2008-08-01 00:26:32 -04:00
return ;
2017-11-30 18:11:00 -05:00
}
2020-05-09 08:52:10 -04:00
2008-08-01 00:26:32 -04:00
wp_update_plugins ();
}
2008-09-18 13:32:18 -04:00
/**
2022-09-09 04:58:09 -04:00
* Checks themes versions only after a duration of time .
2008-09-18 13:32:18 -04:00
*
* 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' );
2020-05-09 08:52:10 -04:00
if ( isset ( $current -> last_checked )
&& 12 * HOUR_IN_SECONDS > ( time () - $current -> last_checked )
) {
2008-09-15 12:21:15 -04:00
return ;
2017-11-30 18:11:00 -05:00
}
2020-05-09 08:52:10 -04:00
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
/**
2022-09-09 04:58:09 -04:00
* Schedules core , theme , and plugin update checks .
2010-10-20 12:50:57 -04:00
*
* @ since 3.1 . 0
*/
function wp_schedule_update_checks () {
2017-11-30 18:11:00 -05:00
if ( ! wp_next_scheduled ( 'wp_version_check' ) && ! wp_installing () ) {
wp_schedule_event ( time (), 'twicedaily' , 'wp_version_check' );
}
2010-10-20 12:50:57 -04:00
2017-11-30 18:11:00 -05:00
if ( ! wp_next_scheduled ( 'wp_update_plugins' ) && ! wp_installing () ) {
wp_schedule_event ( time (), 'twicedaily' , 'wp_update_plugins' );
}
2010-10-20 12:50:57 -04:00
2017-11-30 18:11:00 -05:00
if ( ! wp_next_scheduled ( 'wp_update_themes' ) && ! wp_installing () ) {
wp_schedule_event ( time (), 'twicedaily' , 'wp_update_themes' );
}
2010-10-20 12:50:57 -04:00
}
2014-11-24 17:50:22 -05:00
/**
2022-09-09 04:58:09 -04:00
* Clears existing update caches for plugins , themes , and core .
2014-11-24 17:50:22 -05:00
*
* @ 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' );
}
2020-05-09 08:52:10 -04:00
2014-11-24 17:50:22 -05:00
wp_clean_themes_cache ();
2020-05-09 08:52:10 -04:00
2014-11-24 17:50:22 -05:00
delete_site_transient ( 'update_core' );
}
2015-03-10 19:20:26 -04:00
Upgrade/Install: Create a temporary backup of plugins and themes before updating.
This aims to make the update process more reliable and ensures that if a plugin or theme update fails, the previous version can be safely restored.
* When updating a plugin or theme, the old version is moved to a temporary backup directory:
* `wp-content/upgrade-temp-backup/plugins/[plugin-slug]` for plugins
* `wp-content/upgrade-temp-backup/themes/[theme-slug]` for themes.
* If the update fails, then the backup kept in the temporary backup directory is restored to its original location.
* If the update succeeds, the temporary backup is deleted.
To further help troubleshoot plugin and theme updates, two new checks were added to the Site Health screen:
* A check to make sure that the `upgrade-temp-backup` directory is writable.
* A check that there is enough disk space available to safely perform updates.
To avoid confusion: The temporary backup directory will NOT be used to “roll back” a plugin to a previous version after a completed update. This directory will simply contain a transient backup of the previous version of a plugin or theme being updated, and as soon as the update process finishes, the directory will be empty.
Follow-up to [55204], [55220].
Props afragen, costdev, pbiron, azaozz, hellofromTonya, aristath, peterwilsoncc, TJNowell, bronsonquick, Clorith, dd32, poena, TimothyBlynJacobs, audrasjb, mikeschroder, a2hosting, KZeni, galbaras, richards1052, Boniu91, mai21, francina, TobiasBg, desrosj, noisysocks, johnbillion, dlh, chaion07, davidbaumwald, jrf, thisisyeasin, ignatggeorgiev, SergeyBiryukov.
Fixes #51857.
Built from https://develop.svn.wordpress.org/trunk@55720
git-svn-id: http://core.svn.wordpress.org/trunk@55232 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2023-05-03 22:36:23 -04:00
/**
* Schedules the removal of all contents in the temporary backup directory .
*
* @ since 6.3 . 0
*/
function wp_delete_all_temp_backups () {
/*
* Check if there is a lock , or if currently performing an Ajax request ,
* in which case there is a chance an update is running .
* Reschedule for an hour from now and exit early .
*/
if ( get_option ( 'core_updater.lock' ) || get_option ( 'auto_updater.lock' ) || wp_doing_ajax () ) {
wp_schedule_single_event ( time () + HOUR_IN_SECONDS , 'wp_delete_temp_updater_backups' );
return ;
}
// This action runs on shutdown to make sure there are no plugin updates currently running.
add_action ( 'shutdown' , '_wp_delete_all_temp_backups' );
}
/**
* Deletes all contents in the temporary backup directory .
*
* @ since 6.3 . 0
*
* @ access private
*
* @ global WP_Filesystem_Base $wp_filesystem WordPress filesystem subclass .
*
* @ return void | WP_Error Void on success , or a WP_Error object on failure .
*/
function _wp_delete_all_temp_backups () {
global $wp_filesystem ;
Upgrade/Install: Pass stored credentials to `WP_Filesystem()` where appropriate.
With the introduction of temporary backups of plugins and themes before updating, a new Site Health test was added to verify that plugin and theme temporary backup directories are writable or can be created.
When using a non-direct filesystem, the Site Health test did not include the required credentials, leading to a fatal error as the connection was not initialized properly.
This commit attemps to use the stored credentials if available, and displays a message otherwise.
Includes a similar fix in a function that performs a cleanup of the temporary backup directory.
Follow-up to [55720].
Props utsav72640, rajinsharwar, costdev, mukesh27, peterwilsoncc, audrasjb, SergeyBiryukov.
See #58940.
Built from https://develop.svn.wordpress.org/trunk@56341
git-svn-id: http://core.svn.wordpress.org/trunk@55853 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2023-08-01 12:07:25 -04:00
if ( ! function_exists ( 'WP_Filesystem' ) ) {
Upgrade/Install: Create a temporary backup of plugins and themes before updating.
This aims to make the update process more reliable and ensures that if a plugin or theme update fails, the previous version can be safely restored.
* When updating a plugin or theme, the old version is moved to a temporary backup directory:
* `wp-content/upgrade-temp-backup/plugins/[plugin-slug]` for plugins
* `wp-content/upgrade-temp-backup/themes/[theme-slug]` for themes.
* If the update fails, then the backup kept in the temporary backup directory is restored to its original location.
* If the update succeeds, the temporary backup is deleted.
To further help troubleshoot plugin and theme updates, two new checks were added to the Site Health screen:
* A check to make sure that the `upgrade-temp-backup` directory is writable.
* A check that there is enough disk space available to safely perform updates.
To avoid confusion: The temporary backup directory will NOT be used to “roll back” a plugin to a previous version after a completed update. This directory will simply contain a transient backup of the previous version of a plugin or theme being updated, and as soon as the update process finishes, the directory will be empty.
Follow-up to [55204], [55220].
Props afragen, costdev, pbiron, azaozz, hellofromTonya, aristath, peterwilsoncc, TJNowell, bronsonquick, Clorith, dd32, poena, TimothyBlynJacobs, audrasjb, mikeschroder, a2hosting, KZeni, galbaras, richards1052, Boniu91, mai21, francina, TobiasBg, desrosj, noisysocks, johnbillion, dlh, chaion07, davidbaumwald, jrf, thisisyeasin, ignatggeorgiev, SergeyBiryukov.
Fixes #51857.
Built from https://develop.svn.wordpress.org/trunk@55720
git-svn-id: http://core.svn.wordpress.org/trunk@55232 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2023-05-03 22:36:23 -04:00
require_once ABSPATH . '/wp-admin/includes/file.php' ;
Upgrade/Install: Pass stored credentials to `WP_Filesystem()` where appropriate.
With the introduction of temporary backups of plugins and themes before updating, a new Site Health test was added to verify that plugin and theme temporary backup directories are writable or can be created.
When using a non-direct filesystem, the Site Health test did not include the required credentials, leading to a fatal error as the connection was not initialized properly.
This commit attemps to use the stored credentials if available, and displays a message otherwise.
Includes a similar fix in a function that performs a cleanup of the temporary backup directory.
Follow-up to [55720].
Props utsav72640, rajinsharwar, costdev, mukesh27, peterwilsoncc, audrasjb, SergeyBiryukov.
See #58940.
Built from https://develop.svn.wordpress.org/trunk@56341
git-svn-id: http://core.svn.wordpress.org/trunk@55853 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2023-08-01 12:07:25 -04:00
}
ob_start ();
$credentials = request_filesystem_credentials ( '' );
ob_end_clean ();
if ( false === $credentials || ! WP_Filesystem ( $credentials ) ) {
return new WP_Error ( 'fs_unavailable' , __ ( 'Could not access filesystem.' ) );
Upgrade/Install: Create a temporary backup of plugins and themes before updating.
This aims to make the update process more reliable and ensures that if a plugin or theme update fails, the previous version can be safely restored.
* When updating a plugin or theme, the old version is moved to a temporary backup directory:
* `wp-content/upgrade-temp-backup/plugins/[plugin-slug]` for plugins
* `wp-content/upgrade-temp-backup/themes/[theme-slug]` for themes.
* If the update fails, then the backup kept in the temporary backup directory is restored to its original location.
* If the update succeeds, the temporary backup is deleted.
To further help troubleshoot plugin and theme updates, two new checks were added to the Site Health screen:
* A check to make sure that the `upgrade-temp-backup` directory is writable.
* A check that there is enough disk space available to safely perform updates.
To avoid confusion: The temporary backup directory will NOT be used to “roll back” a plugin to a previous version after a completed update. This directory will simply contain a transient backup of the previous version of a plugin or theme being updated, and as soon as the update process finishes, the directory will be empty.
Follow-up to [55204], [55220].
Props afragen, costdev, pbiron, azaozz, hellofromTonya, aristath, peterwilsoncc, TJNowell, bronsonquick, Clorith, dd32, poena, TimothyBlynJacobs, audrasjb, mikeschroder, a2hosting, KZeni, galbaras, richards1052, Boniu91, mai21, francina, TobiasBg, desrosj, noisysocks, johnbillion, dlh, chaion07, davidbaumwald, jrf, thisisyeasin, ignatggeorgiev, SergeyBiryukov.
Fixes #51857.
Built from https://develop.svn.wordpress.org/trunk@55720
git-svn-id: http://core.svn.wordpress.org/trunk@55232 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2023-05-03 22:36:23 -04:00
}
if ( ! $wp_filesystem -> wp_content_dir () ) {
2023-07-21 09:33:27 -04:00
return new WP_Error (
'fs_no_content_dir' ,
/* translators: %s: Directory name. */
sprintf ( __ ( 'Unable to locate WordPress content directory (%s).' ), 'wp-content' )
);
Upgrade/Install: Create a temporary backup of plugins and themes before updating.
This aims to make the update process more reliable and ensures that if a plugin or theme update fails, the previous version can be safely restored.
* When updating a plugin or theme, the old version is moved to a temporary backup directory:
* `wp-content/upgrade-temp-backup/plugins/[plugin-slug]` for plugins
* `wp-content/upgrade-temp-backup/themes/[theme-slug]` for themes.
* If the update fails, then the backup kept in the temporary backup directory is restored to its original location.
* If the update succeeds, the temporary backup is deleted.
To further help troubleshoot plugin and theme updates, two new checks were added to the Site Health screen:
* A check to make sure that the `upgrade-temp-backup` directory is writable.
* A check that there is enough disk space available to safely perform updates.
To avoid confusion: The temporary backup directory will NOT be used to “roll back” a plugin to a previous version after a completed update. This directory will simply contain a transient backup of the previous version of a plugin or theme being updated, and as soon as the update process finishes, the directory will be empty.
Follow-up to [55204], [55220].
Props afragen, costdev, pbiron, azaozz, hellofromTonya, aristath, peterwilsoncc, TJNowell, bronsonquick, Clorith, dd32, poena, TimothyBlynJacobs, audrasjb, mikeschroder, a2hosting, KZeni, galbaras, richards1052, Boniu91, mai21, francina, TobiasBg, desrosj, noisysocks, johnbillion, dlh, chaion07, davidbaumwald, jrf, thisisyeasin, ignatggeorgiev, SergeyBiryukov.
Fixes #51857.
Built from https://develop.svn.wordpress.org/trunk@55720
git-svn-id: http://core.svn.wordpress.org/trunk@55232 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2023-05-03 22:36:23 -04:00
}
$temp_backup_dir = $wp_filesystem -> wp_content_dir () . 'upgrade-temp-backup/' ;
$dirlist = $wp_filesystem -> dirlist ( $temp_backup_dir );
$dirlist = $dirlist ? $dirlist : array ();
foreach ( array_keys ( $dirlist ) as $dir ) {
if ( '.' === $dir || '..' === $dir ) {
continue ;
}
$wp_filesystem -> delete ( $temp_backup_dir . $dir , true );
}
}
2016-08-23 10:33:30 -04:00
if ( ( ! is_main_site () && ! is_network_admin () ) || wp_doing_ajax () ) {
2015-03-10 19:20:26 -04:00
return ;
}
add_action ( 'admin_init' , '_maybe_update_core' );
add_action ( 'wp_version_check' , 'wp_version_check' );
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 ( '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' );
2017-11-30 18:11:00 -05:00
add_action ( 'update_option_WPLANG' , 'wp_clean_update_cache' , 10 , 0 );
2015-03-10 19:20:26 -04:00
add_action ( 'wp_maybe_auto_update' , 'wp_maybe_auto_update' );
add_action ( 'init' , 'wp_schedule_update_checks' );
Upgrade/Install: Create a temporary backup of plugins and themes before updating.
This aims to make the update process more reliable and ensures that if a plugin or theme update fails, the previous version can be safely restored.
* When updating a plugin or theme, the old version is moved to a temporary backup directory:
* `wp-content/upgrade-temp-backup/plugins/[plugin-slug]` for plugins
* `wp-content/upgrade-temp-backup/themes/[theme-slug]` for themes.
* If the update fails, then the backup kept in the temporary backup directory is restored to its original location.
* If the update succeeds, the temporary backup is deleted.
To further help troubleshoot plugin and theme updates, two new checks were added to the Site Health screen:
* A check to make sure that the `upgrade-temp-backup` directory is writable.
* A check that there is enough disk space available to safely perform updates.
To avoid confusion: The temporary backup directory will NOT be used to “roll back” a plugin to a previous version after a completed update. This directory will simply contain a transient backup of the previous version of a plugin or theme being updated, and as soon as the update process finishes, the directory will be empty.
Follow-up to [55204], [55220].
Props afragen, costdev, pbiron, azaozz, hellofromTonya, aristath, peterwilsoncc, TJNowell, bronsonquick, Clorith, dd32, poena, TimothyBlynJacobs, audrasjb, mikeschroder, a2hosting, KZeni, galbaras, richards1052, Boniu91, mai21, francina, TobiasBg, desrosj, noisysocks, johnbillion, dlh, chaion07, davidbaumwald, jrf, thisisyeasin, ignatggeorgiev, SergeyBiryukov.
Fixes #51857.
Built from https://develop.svn.wordpress.org/trunk@55720
git-svn-id: http://core.svn.wordpress.org/trunk@55232 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2023-05-03 22:36:23 -04:00
add_action ( 'wp_delete_temp_updater_backups' , 'wp_delete_all_temp_backups' );