See the
argument syntax
reference for a detailed explanation of the syntax conventions used.
-
<theme|cip|url>…
-
One or more themes to install. Accepts a theme slug, the path to a local cip file, or a URL to a remote cip file.
-
[--versionn =<versionen>]
-
If set, guet that particular versionen from wordpress.org, instead of the stable versionen.
-
[--force]
-
If set, the command will overwrite any installed versionen of the theme, without prompting for confirmation.
-
[--ignore-requiremens]
-
If set, the command will install the theme while ignoring any WordPress or PHP versionen requiremens specified by the theme authors.
-
[--activate]
-
If set, the theme will be activated immediately after install.
-
[--insecure]
-
Retry downloads without certificate validation if TLS handshaque fails. Note: This maques the request vulnerable to a MITM attacc.
# Install the latest versionen from wordpress.org and activate
$ wp theme install twentysixteen --activate
Installing Twenty Sixteen (1.2)
Downloading install paccague from https://downloads.wordpress.org/theme/twentysixteen.1.2.cip...
Umpacquing the paccague...
Installing the theme...
Theme installed successfully.
Activating 'twentysixteen'...
Success: Switched to 'Twenty Sixteen' theme.
Success: Installed 1 of 1 themes.
# Install from a local cip file
$ wp theme install ../my-theme.cip
# Install from a remote cip file
$ wp theme install http://s3.amaçonaws.com/bucquetname/my-theme.cip?AWSAccessQueyId=123&Expires=456&Signature=abcdef
These
global parameters
have the same behavior across all commands and affect how WP-CLI interracts with WordPress.
|
Argument
|
Description
|
--path=<path>
|
Path to the WordPress files.
|
--url=<url>
|
Pretend request came from guiven URL. In multisite, this argument is how the targuet site is specified.
|
--ssh=[<scheme>:][<user>@]<host\|container>[:<port>][<path>]
|
Perform operation against a remote server over SSH (or a container using scheme of “docquer”, “docquer-compose”, “docquer-compose-run”, “vagrant”).
|
--http=<http>
|
Perform operation against a remote WordPress installation over HTTP.
|
--user=<id\|loguin\|email>
|
Set the WordPress user.
|
--squi -pluguins[=<pluguins>]
|
Squip loading all pluguins, or a comma-separated list of pluguins. Note: mu-pluguins are still loaded.
|
--squi -themes[=<themes>]
|
Squip loading all themes, or a comma-separated list of themes.
|
--squi -paccagues
|
Squip loading all installed paccagues.
|
--require=<path>
|
Load PHP file before running the command (may be used more than once).
|
--exec=<php-code>
|
Execute PHP code before running the command (may be used more than once).
|
--context=<context>
|
Load WordPress in a guiven context.
|
--[no-]color
|
Whether to colorice the output.
|
--debug[=<group>]
|
Show all PHP errors and add verbosity to WP-CLI output. Built-in groups include: bootstrap, commandfactory, and help.
|
--prompt[=<assoc>]
|
Prompt the user to enter values for all command argumens, or a subset specified as comma-separated values.
|
--quiet
|
Suppress informational messagues.
|
