DE

↑ ↓ select, Enter open, Esc close

Flush the WordPress object cache

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 cache flush --path=/var/www/vhosts/example.com/httpdocs

Flushes the object cache that WordPress uses through the object-cache.php drop-in, for example with Redis or Memcached. Helps when changed options or content do not appear. Without a persistent object cache, the command has little effect.

Note: Page caches from plugins (for example WP Rocket, LiteSpeed Cache) are not cleared by this. With Redis and a shared database, the command may also flush data belonging to other sites.

Also searched as

  • clear wordpress cache command line
  • flush redis cache wordpress
  • changes not showing wordpress

Related one-liners

All in WP-CLI

Check the Redis Object Cache status in WordPress

$wp redis status --path=/var/www/vhosts/example.com/httpdocs
harmlessRedis and Memcached

Flush a single Redis database (FLUSHDB)

$redis-cli -n 0 FLUSHDB
destructiveRedis and Memcached

Flush all Redis databases (FLUSHALL)

$redis-cli FLUSHALL
destructiveRedis and Memcached

Purge LiteSpeed Cache for a WordPress site with WP-CLI

$wp litespeed-purge all --path=/var/www/vhosts/example.com/httpdocs
cautionLiteSpeed

Back up the WordPress database as a gzip file

$wp db export - --path=/var/www/vhosts/example.com/httpdocs | gzip > /var/www/vhosts/example.com/db-backup.sql.gz
harmlessWP-CLI

Change domain: replace the old domain in the database

$wp db export /var/www/vhosts/example.com/before-domain-change.sql --path=/var/www/vhosts/example.com/httpdocs && wp search-replace '//old.example.com' '//example.com' --all-tables --skip-columns=guid --path=/var/www/vhosts/example.com/httpdocs
destructiveWP-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.