DE

↑ ↓ select, Enter open, Esc close

Update all WordPress plugins at once

cautionWP-CLIalle

Caution: This command changes the system. Understand what it does before you run it.

Adjust the values, the command updates live
user@server
wp plugin update --all --path=/var/www/vhosts/example.com/httpdocs

Downloads and installs the new version for every plugin with an available update. At the end, a table shows the old and new versions. Use --dry-run beforehand to see what would be updated.

Note: A broken plugin update can take the site down. Create a backup first, and update themes the same way with wp theme update --all.

Also searched as

  • update all plugins wp cli
  • update wordpress plugins command line
  • install plugin updates

Related one-liners

All in WP-CLI

List installed plugins with status and updates

$wp plugin list --fields=name,status,version,update_version --path=/var/www/vhosts/example.com/httpdocs
harmlessWP-CLI

Compare plugin files with the originals from wordpress.org

$wp plugin verify-checksums --all --path=/var/www/vhosts/example.com/httpdocs
harmlessWP-CLI

Deactivate a single plugin despite a PHP fatal error

$wp plugin deactivate woocommerce --skip-plugins --skip-themes --path=/var/www/vhosts/example.com/httpdocs
cautionWP-CLI

Deactivate all plugins and save the active list

$wp plugin list --status=active --field=name --path=/var/www/vhosts/example.com/httpdocs > /var/www/vhosts/example.com/active-plugins.txt && wp plugin deactivate --all --path=/var/www/vhosts/example.com/httpdocs
cautionWP-CLI

Enable automatic updates for a plugin

$wp plugin auto-updates enable wordfence --path=/var/www/vhosts/example.com/httpdocs
cautionWP-CLI

Install a specific WordPress core version

$wp core update --version=6.6.2 --force --path=/var/www/vhosts/example.com/httpdocs
cautionWP-CLI

Read first, then run.

The commands on myline.de act directly on servers, files and databases. A wrong path or placeholder can delete data irreversibly or make a server unreachable.

  • All commands are provided without warranty and are not tested on every system.
  • Understand what a command does before running it, and check every placeholder.
  • Make a backup first and, if possible, try it on a test system.
  • You run commands at your own risk. Liability for damages is excluded to the extent permitted by law.