gem-hunter
Language: PHP
Downloads, installs, updates, and manages a WordPress installation.
Downloads, installs, updates, and manages a WordPress installation.
Quick links: Using | Installing | Contributing | Support
This package implements the following commands:
Downloads, installs, updates, and manages a WordPress installation.
wp core
EXAMPLES
# 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
Checks for WordPress updates via Version Check API.
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.
OPTIONS
[--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
$ wp core check-update
+---------+-------------+-------------------------------------------------------------+
| version | update_type | package_url |
+---------+-------------+-------------------------------------------------------------+
| 4.5.2 | major | https://downloads.wordpress.org/release/wordpress-4.5.2.zip |
+---------+-------------+-------------------------------------------------------------+
Checks for the need for WordPress database updates.
wp core check-update-db [--network]
Compares the current database version with the version required by WordPress core to determine if database updates are needed.
OPTIONS
[--network]
Check databases for all sites on a network.
EXAMPLES
# Check if database update is needed
$ wp core check-update-db
Success: WordPress database is up to date.
# Check database update status for all sites on a network
$ wp core check-update-db --network
Success: WordPress databases are up to date on 5/5 sites.
Downloads core WordPress files.
wp core download [<download-url>] [--path=<path>] [--locale=<locale>] [--version=<version>] [--skip-content] [--force] [--insecure] [--extract] [--skip-locale-check]
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.
OPTIONS
[<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.
[--skip-locale-check]
If specified, allows downloading an older version of WordPress when the requested locale is not available for the latest release.
EXAMPLES
$ wp core download --locale=nl_NL
Downloading WordPress 4.5.2 (nl_NL)...
md5 hash verified: c5366d05b521831dd0b29dfc386e56a5
Success: WordPress downloaded.
Runs the standard WordPress installation process.
wp core install --url=<url> --title=<site-title> --admin_user=<username> [--admin_password|admin_pass=<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.
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.
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.
OPTIONS
--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|admin_pass=<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
# 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
Checks if WordPress is installed.
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.
OPTIONS
[--network]
Check if this is a multisite installation.
EXAMPLES
# 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
Transforms an existing single-site installation into a multisite installation.
wp core multisite-convert [--title=<network-title>] [--base=<url-path>] [--subdomains] [--skip-config]
Alias: install-network
Creates the multisite database tables, and adds the multisite constants to wp-config.php.
For those using WordPress with Apache, remember to update the .htaccess
file with the appropriate multisite rewrite rules.
Review the multisite documentation for more details about how multisite works.
OPTIONS
[--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
$ 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.
Installs WordPress multisite from scratch.
wp core multisite-install [--url=<url>] [--base=<url-path>] [--subdomains] --title=<site-title> --admin_user=<username> [--admin_password=<password>] --admin_email=<email> [--locale=<locale>] [--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.
For those using WordPress with Apache, remember to update the .htaccess
file with the appropriate multisite rewrite rules.
OPTIONS
[--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.
[--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.
[--skip-config]
Don't add multisite constants to wp-config.php.
EXAMPLES
$ 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.
Updates WordPress to a newer version.
wp core update [<zip>] [--minor] [--version=<version>] [--force] [--locale=<locale>] [--format=<format>] [--insecure]
Alias: upgrade
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.
OPTIONS
[<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.
[--format=<format>]
Render output in a particular format.
---
options:
- table
- csv
- json
---
[--insecure]
Retry download without certificate validation if TLS handshake fails. Note: This makes the request vulnerable to a MITM attack.
EXAMPLES
# 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 old files were removed.
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...
Cleaning up files...
No old files were removed.
Warning: Could not retrieve WordPress core checksums; skipping checksum-based cleanup. Files listed in $_old_files were still cleaned up.
Success: WordPress updated successfully.
Runs the WordPress database update procedure.
wp core update-db [--network] [--dry-run]
OPTIONS
[--network]
Update databases for all sites on a network
[--dry-run]
Compare database versions without performing the update.
EXAMPLES
# 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.
# Update databases for all sites on a specific network in a multinetwork install.
$ wp core update-db --network --url=network2.example.com
WordPress database upgraded successfully from db version 35700 to 29630 on network2.example.com/
Success: WordPress database upgraded on 50/50 sites.
Displays the WordPress version.
wp core version [--extra]
OPTIONS
[--extra]
Show extended version information.
Note: In a Multisite installation, `wp core version --extra` reports the expected database
revision from `wp-includes/version.php`, not the per-site `db_version` stored in each
subsite's options table. To retrieve a subsite's stored database revision, use
`wp option get db_version --url=<subsite>`. See also `wp core check-update-db`.
EXAMPLES
# 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
This package is included with WP-CLI itself, no additional installation necessary.
To install the latest version of this package over what's included in WP-CLI, run:
wp package install git@github.com:wp-cli/core-command.git
We appreciate you taking the initiative to contribute to this project.
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.
For a more thorough introduction, check out WP-CLI's guide to contributing. This package follows those policy and guidelines.
Think you’ve found a bug? We’d love for you to help us get it fixed.
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.
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.
Want to contribute a new feature? Please first open a new issue to discuss whether the feature is a good fit for the project.
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.
This project is licensed under the MIT License. See the LICENSE file for details.
GitHub issues aren't for general support questions. For support resources and next steps, see the WP-CLI Support page: https://make.wordpress.org/cli/handbook/support/
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.