Updates WordPress to a newer version.
Defaults to updating WordPress to the latest version.
If you see “Error: Another update is currently in progress.”, you may need to run
wp option delete core_updater.lock after verifying another update isn’t actually running.
- Path to zip file to use, instead of downloading from wordpress.org.
- Only perform updates for minor releases (e.g. update from WP 4.3 to 4.3.3 instead of 4.4.2).
- Update to a specific version, instead of to the latest version. Alternatively accepts ‘nightly’.
- Update even when installed WP version is greater than the requested version.
- Select which language you want to download.
- Retry download without certificate validation if TLS handshake fails. Note: This makes the request vulnerable to a MITM attack.
# Update WordPress $ wp core update Updating to version 4.5.2 (en_US)... Downloading update from https://downloads.wordpress.org/release/wordpress-4.5.2-no-content.zip... Unpacking the update... Cleaning up files... No files found that need cleaning up Success: WordPress updated successfully. # Update WordPress to latest version of 3.8 release $ wp core update --version=3.8 ../latest.zip Updating to version 3.8 ()... Unpacking the update... Cleaning up files... File removed: wp-admin/js/tags-box.js ... File removed: wp-admin/js/updates.min. 377 files cleaned up Success: WordPress updated successfully. # Update WordPress to 3.1 forcefully $ wp core update --version=3.1 --force Updating to version 3.1 (en_US)... Downloading update from https://wordpress.org/wordpress-3.1.zip... Unpacking the update... Warning: Checksums not available for WordPress 3.1/en_US. Please cleanup files manually. Success: WordPress updated successfully.
GLOBAL PARAMETERS GLOBAL PARAMETERS
These global parameters have the same behavior across all commands and affect how WP-CLI interacts with WordPress.
||Path to the WordPress files.|
||Pretend request came from given URL. In multisite, this argument is how the target site is specified.|
||Perform operation against a remote server over SSH (or a container using scheme of “docker”, “docker-compose”, “docker-compose-run”, “vagrant”).|
||Perform operation against a remote WordPress installation over HTTP.|
||Set the WordPress user.|
||Skip loading all plugins, or a comma-separated list of plugins. Note: mu-plugins are still loaded.|
||Skip loading all themes, or a comma-separated list of themes.|
||Skip loading all installed packages.|
||Load PHP file before running the command (may be used more than once).|
||Execute PHP code before running the command (may be used more than once).|
||Load WordPress in a given context.|
||Whether to colorize the output.|
||Show all PHP errors and add verbosity to WP-CLI output. Built-in groups include: bootstrap, commandfactory, and help.|
||Prompt the user to enter values for all command arguments, or a subset specified as comma-separated values.|
||Suppress informational messages.|
Command documentation is regenerated at every release. To add or update an example, please submit a pull request against the corresponding part of the codebase.