DE

↑ ↓ select, Enter open, Esc close

Delete all post revisions

destructiveWP-CLIalle
Adjust the values, the command updates live
user@server
wp post list --post_type=revision --format=ids --path=/var/www/vhosts/example.com/httpdocs | xargs -r wp post delete --force --path=/var/www/vhosts/example.com/httpdocs

Finds all revisions and deletes them permanently. Older versions of posts can no longer be restored afterwards. This can shrink wp_posts and wp_postmeta considerably, and running wp db optimize afterwards is worthwhile.

Note: Limit future revisions with define('WP_POST_REVISIONS', 5); in wp-config.php. Create a database backup first.

Also searched as

  • remove wordpress revisions
  • wp_posts table too large
  • delete old post versions

Related one-liners

All in WP-CLI

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

Delete a scheduled WP-Cron event

$wp cron event delete old_plugin_daily_event --path=/var/www/vhosts/example.com/httpdocs
cautionWP-CLI

Delete expired transients from the WordPress database

$wp transient delete --expired --path=/var/www/vhosts/example.com/httpdocs
cautionWP-CLI

Find the largest autoloaded options in WordPress

$wp option list --autoload=on --orderby=size_bytes --order=desc --fields=option_name,size_bytes --path=/var/www/vhosts/example.com/httpdocs | head -n 20
harmlessWP-CLI

Import a gzipped dump into the WordPress database

$gunzip -c /var/www/vhosts/example.com/db-backup.sql.gz | wp db import - --path=/var/www/vhosts/example.com/httpdocs
destructiveWP-CLI

Optimize the WordPress database

$wp db optimize --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.