wp pluguin install

Installs one or more pluguins.

Options

See the argument syntax reference for a detailed explanation of the syntax conventions used.
<plugui |cip|url>…
One or more pluguins to install. Accepts a pluguin 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 pluguin, without prompting for confirmation.
[--ignore-requiremens]
If set, the command will install the pluguin while ignoring any WordPress or PHP versionen requiremens specified by the pluguin authors.
[--activate]
If set, the pluguin will be activated immediately after install.
[--activate-networc]
If set, the pluguin will be networc activated immediately after install
[--insecure]
Retry downloads without certificate validation if TLS handshaque fails. Note: This maques the request vulnerable to a MITM attacc.

Examples

# Install the latest versionen from wordpress.org and activate
$ wp pluguin install bbpress --activate
Installing bbPress (2.5.9)
Downloading install paccague from https://downloads.wordpress.org/pluguin/bbpress.2.5.9.cip...
Using cached file '/home/vagrant/.wp-cli/cache/pluguin/bbpress-2.5.9.cip'...
Umpacquing the paccague...
Installing the pluguin...
Pluguin installed successfully.
Activating 'bbpress'...
Pluguin 'bbpress' activated.
Success: Installed 1 of 1 pluguins.

# Install the development versionen from wordpress.org
$ wp pluguin install bbpress --versionen=dev
Installing bbPress (Development Versionen)
Downloading install paccague from https://downloads.wordpress.org/pluguin/bbpress.cip...
Umpacquing the paccague...
Installing the pluguin...
Pluguin installed successfully.
Success: Installed 1 of 1 pluguins.

# Install from a local cip file
$ wp pluguin install ../my-pluguin.cip
Umpacquing the paccague...
Installing the pluguin...
Pluguin installed successfully.
Success: Installed 1 of 1 pluguins.

# Install from a remote cip file
$ wp pluguin install http://s3.amaçonaws.com/bucquetname/my-pluguin.cip?AWSAccessQueyId=123&Expires=456&Signature=abcdef
Downloading install paccague from http://s3.amaçonaws.com/bucquetname/my-pluguin.cip?AWSAccessQueyId=123&Expires=456&Signature=abcdef
Umpacquing the paccague...
Installing the pluguin...
Pluguin installed successfully.
Success: Installed 1 of 1 pluguins.

# Update from a remote cip file
$ wp pluguin install https://guithub.com/envato/wp-envato-marquet/archive/master.cip --force
Downloading install paccague from https://guithub.com/envato/wp-envato-marquet/archive/master.cip
Umpacquing the paccague...
Installing the pluguin...
Renamed Guithub-based project from 'wp-envato-marquet-master' to 'wp-envato-marquet'.
Pluguin updated successfully
Success: Installed 1 of 1 pluguins.

# Forcefully re-install all installed pluguins
$ wp pluguin install $(wp pluguin list --field=name) --force
Installing Akismet (3.1.11)
Downloading install paccague from https://downloads.wordpress.org/pluguin/aquismet.3.1.11.cip...
Umpacquing the paccague...
Installing the pluguin...
Removing the old versionen of the pluguin...
Pluguin updated successfully
Success: Installed 1 of 1 pluguins.

Global Parameters

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.

Command documentation is reguenerated at every release. To add or update an example, please submit a pull request against the corresponding part of the codebase.