wp-cli/core-command
Downloads, installs, updates, and manages a WordPress installation., (*1)
, (*2)
Quick links: Using | Installing | Contributing | Support, (*3)
Using
This package implements the following commands:, (*4)
wp core
Downloads, installs, updates, and manages a WordPress installation., (*5)
wp core
EXAMPLES, (*6)
# Download WordPress core
$ wp core download --locale=nl_NL
Downloading WordPress 4.5.2 (nl_NL)...
md5 hash verified: c5366d05b521831dd0b29dfc386e56a5
Success: WordPress downloaded.
# Install WordPress
$ wp core install --url=example.com --title=Example --admin_user=supervisor --admin_password=strongpassword --admin_email=info@example.com
Success: WordPress installed successfully.
# Display the WordPress version
$ wp core version
4.5.2
wp core check-update
Checks for WordPress updates via Version Check API., (*7)
wp core check-update [--minor] [--major] [--force-check] [--field=<field>] [--fields=<fields>] [--format=<format>]
Lists the most recent versions when there are updates available,
or success message when up to date., (*8)
OPTIONS, (*9)
[--minor]
Compare only the first two parts of the version number.
[--major]
Compare only the first part of the version number.
[--force-check]
Bypass the transient cache and force a fresh update check.
[--field=<field>]
Prints the value of a single field for each update.
[--fields=<fields>]
Limit the output to specific object fields. Defaults to version,update_type,package_url.
[--format=<format>]
Render output in a particular format.
---
default: table
options:
- table
- csv
- count
- json
- yaml
---
EXAMPLES, (*10)
$ wp core check-update
+---------+-------------+-------------------------------------------------------------+
| version | update_type | package_url |
+---------+-------------+-------------------------------------------------------------+
| 4.5.2 | major | https://downloads.wordpress.org/release/wordpress-4.5.2.zip |
+---------+-------------+-------------------------------------------------------------+
wp core download
Downloads core WordPress files., (*11)
wp core download [<download-url>] [--path=<path>] [--locale=<locale>] [--version=<version>] [--skip-content] [--force] [--insecure] [--extract]
Downloads and extracts WordPress core files to the specified path. Uses
current directory when no path is specified. Downloaded build is verified
to have the correct md5 and then cached to the local filesystem.
Subsequent uses of command will use the local cache if it still exists., (*12)
OPTIONS, (*13)
[<download-url>]
Download directly from a provided URL instead of fetching the URL from the wordpress.org servers.
[--path=<path>]
Specify the path in which to install WordPress. Defaults to current
directory.
[--locale=<locale>]
Select which language you want to download.
[--version=<version>]
Select which version you want to download. Accepts a version number, 'latest' or 'nightly'.
[--skip-content]
Download WP without the default themes and plugins.
[--force]
Overwrites existing files, if present.
[--insecure]
Retry download without certificate validation if TLS handshake fails. Note: This makes the request vulnerable to a MITM attack.
[--extract]
Whether to extract the downloaded file. Defaults to true.
EXAMPLES, (*14)
$ wp core download --locale=nl_NL
Downloading WordPress 4.5.2 (nl_NL)...
md5 hash verified: c5366d05b521831dd0b29dfc386e56a5
Success: WordPress downloaded.
wp core install
Runs the standard WordPress installation process., (*15)
wp core install --url=<url> --title=<site-title> --admin_user=<username> [--admin_password=<password>] --admin_email=<email> [--locale=<locale>] [--skip-email]
Creates the WordPress tables in the database using the URL, title, and
default admin user details provided. Performs the famous 5 minute install
in seconds or less., (*16)
Note: if you've installed WordPress in a subdirectory, then you'll need
to wp option update siteurl after wp core install. For instance, if
WordPress is installed in the /wp directory and your domain is example.com,
then you'll need to run wp option update siteurl http://example.com/wp for
your WordPress installation to function properly., (*17)
Note: When using custom user tables (e.g. CUSTOM_USER_TABLE), the admin
email and password are ignored if the user_login already exists. If the
user_login doesn't exist, a new user will be created., (*18)
OPTIONS, (*19)
--url=<url>
The address of the new site.
--title=<site-title>
The title of the new site.
--admin_user=<username>
The name of the admin user.
[--admin_password=<password>]
The password for the admin user. Defaults to randomly generated string.
--admin_email=<email>
The email address for the admin user.
[--locale=<locale>]
The locale/language for the installation (e.g. `de_DE`). Default is `en_US`.
[--skip-email]
Don't send an email notification to the new admin user.
EXAMPLES, (*20)
# Install WordPress in 5 seconds
$ wp core install --url=example.com --title=Example --admin_user=supervisor --admin_password=strongpassword --admin_email=info@example.com
Success: WordPress installed successfully.
# Install WordPress without disclosing admin_password to bash history
$ wp core install --url=example.com --title=Example --admin_user=supervisor --admin_email=info@example.com --prompt=admin_password < admin_password.txt
wp core is-installed
Checks if WordPress is installed., (*21)
wp core is-installed [--network]
Determines whether WordPress is installed by checking if the standard
database tables are installed. Doesn't produce output; uses exit codes
to communicate whether WordPress is installed., (*22)
OPTIONS, (*23)
[--network]
Check if this is a multisite installation.
EXAMPLES, (*24)
# Bash script for checking if WordPress is not installed.
if ! wp core is-installed 2>/dev/null; then
# WP is not installed. Let's try installing it.
wp core install
fi
# Bash script for checking if WordPress is installed, with fallback.
if wp core is-installed 2>/dev/null; then
# WP is installed. Let's do some things we should only do in a confirmed WP environment.
wp core verify-checksums
else
# Fallback if WP is not installed.
echo 'Hey Friend, you are in the wrong spot. Move in to your WordPress directory and try again.'
fi
wp core multisite-convert
Transforms an existing single-site installation into a multisite installation., (*25)
wp core multisite-convert [--title=<network-title>] [--base=<url-path>] [--subdomains] [--skip-config]
Creates the multisite database tables, and adds the multisite constants
to wp-config.php., (*26)
For those using WordPress with Apache, remember to update the .htaccess
file with the appropriate multisite rewrite rules., (*27)
Review the multisite documentation
for more details about how multisite works., (*28)
OPTIONS, (*29)
[--title=<network-title>]
The title of the new network.
[--base=<url-path>]
Base path after the domain name that each site url will start with.
---
default: /
---
[--subdomains]
If passed, the network will use subdomains, instead of subdirectories. Doesn't work with 'localhost'.
[--skip-config]
Don't add multisite constants to wp-config.php.
EXAMPLES, (*30)
$ wp core multisite-convert
Set up multisite database tables.
Added multisite constants to wp-config.php.
Success: Network installed. Don't forget to set up rewrite rules.
wp core multisite-install
Installs WordPress multisite from scratch., (*31)
wp core multisite-install [--url=<url>] [--base=<url-path>] [--subdomains] --title=<site-title> --admin_user=<username> [--admin_password=<password>] --admin_email=<email> [--skip-email] [--skip-config]
Creates the WordPress tables in the database using the URL, title, and
default admin user details provided. Then, creates the multisite tables
in the database and adds multisite constants to the wp-config.php., (*32)
For those using WordPress with Apache, remember to update the .htaccess
file with the appropriate multisite rewrite rules., (*33)
OPTIONS, (*34)
[--url=<url>]
The address of the new site.
[--base=<url-path>]
Base path after the domain name that each site url in the network will start with.
---
default: /
---
[--subdomains]
If passed, the network will use subdomains, instead of subdirectories. Doesn't work with 'localhost'.
--title=<site-title>
The title of the new site.
--admin_user=<username>
The name of the admin user.
---
default: admin
---
[--admin_password=<password>]
The password for the admin user. Defaults to randomly generated string.
--admin_email=<email>
The email address for the admin user.
[--skip-email]
Don't send an email notification to the new admin user.
[--skip-config]
Don't add multisite constants to wp-config.php.
EXAMPLES, (*35)
$ wp core multisite-install --title="Welcome to the WordPress" \
> --admin_user="admin" --admin_password="password" \
> --admin_email="user@example.com"
Single site database tables already present.
Set up multisite database tables.
Added multisite constants to wp-config.php.
Success: Network installed. Don't forget to set up rewrite rules.
wp core update
Updates WordPress to a newer version., (*36)
wp core update [<zip>] [--minor] [--version=<version>] [--force] [--locale=<locale>] [--insecure]
Defaults to updating WordPress to the latest version., (*37)
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., (*38)
OPTIONS, (*39)
[<zip>]
Path to zip file to use, instead of downloading from wordpress.org.
[--minor]
Only perform updates for minor releases (e.g. update from WP 4.3 to 4.3.3 instead of 4.4.2).
[--version=<version>]
Update to a specific version, instead of to the latest version. Alternatively accepts 'nightly'.
[--force]
Update even when installed WP version is greater than the requested version.
[--locale=<locale>]
Select which language you want to download.
[--insecure]
Retry download without certificate validation if TLS handshake fails. Note: This makes the request vulnerable to a MITM attack.
EXAMPLES, (*40)
# 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 using zip file.
$ wp core update ../latest.zip
Starting update...
Unpacking the update...
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.
wp core update-db
Runs the WordPress database update procedure., (*41)
wp core update-db [--network] [--dry-run]
OPTIONS, (*42)
[--network]
Update databases for all sites on a network
[--dry-run]
Compare database versions without performing the update.
EXAMPLES, (*43)
# Update the WordPress database.
$ wp core update-db
Success: WordPress database upgraded successfully from db version 36686 to 35700.
# Update databases for all sites on a network.
$ wp core update-db --network
WordPress database upgraded successfully from db version 35700 to 29630 on example.com/
Success: WordPress database upgraded on 123/123 sites.
wp core version
Displays the WordPress version., (*44)
wp core version [--extra]
OPTIONS, (*45)
[--extra]
Show extended version information.
EXAMPLES, (*46)
# Display the WordPress version
$ wp core version
4.5.2
# Display WordPress version along with other information
$ wp core version --extra
WordPress version: 4.5.2
Database revision: 36686
TinyMCE version: 4.310 (4310-20160418)
Package language: en_US
Installing
This package is included with WP-CLI itself, no additional installation necessary., (*47)
To install the latest version of this package over what's included in WP-CLI, run:, (*48)
wp package install git@github.com:wp-cli/core-command.git
Contributing
We appreciate you taking the initiative to contribute to this project., (*49)
Contributing isnât limited to just code. We encourage you to contribute in the way that best fits your abilities, by writing tutorials, giving a demo at your local meetup, helping other users with their support questions, or revising our documentation., (*50)
For a more thorough introduction, check out WP-CLI's guide to contributing. This package follows those policy and guidelines., (*51)
Reporting a bug
Think youâve found a bug? Weâd love for you to help us get it fixed., (*52)
Before you create a new issue, you should search existing issues to see if thereâs an existing resolution to it, or if itâs already been fixed in a newer version., (*53)
Once youâve done a bit of searching and discovered there isnât an open or fixed issue for your bug, please create a new issue. Include as much detail as you can, and clear steps to reproduce if possible. For more guidance, review our bug report documentation., (*54)
Creating a pull request
Want to contribute a new feature? Please first open a new issue to discuss whether the feature is a good fit for the project., (*55)
Once you've decided to commit the time to seeing your pull request through, please follow our guidelines for creating a pull request to make sure it's a pleasant experience. See "Setting up" for details specific to working on this package locally., (*56)
Support
GitHub issues aren't for general support questions, but there are other venues you can try: https://wp-cli.org/#support, (*57)
This README.md is generated dynamically from the project's codebase using wp scaffold package-readme (doc). To suggest changes, please submit a pull request against the corresponding part of the codebase., (*58)
Wallogit.com
