DE

↑ ↓ select, Enter open, Esc close

Turn WordPress maintenance mode on and off

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 maintenance-mode activate --path=/var/www/vhosts/example.com/httpdocs

Creates the .maintenance file so visitors see a maintenance message with HTTP status 503. Turn it off with wp maintenance-mode deactivate, and wp maintenance-mode status shows the current state. A short 503 is harmless for search engines, but it should not last for days.

Note: If a site is stuck in maintenance mode after an aborted update, deactivate or deleting .maintenance in the web root is enough.

Also searched as

  • put wordpress in maintenance mode
  • wordpress stuck in maintenance mode
  • enable maintenance page wordpress

Related one-liners

All in WP-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

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

List installed themes with status and updates

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

Roll back a plugin to a specific version

$wp plugin install contact-form-7 --version=5.9.8 --force --path=/var/www/vhosts/example.com/httpdocs
cautionWP-CLI

Update all WordPress plugins at once

$wp plugin update --all --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.