Log in
Pruneline documentation1.x
Using Pruneline

WP-CLI

Scan, list any audit and print the handover report from the command line.

If your host gives you WP-CLI, you can run Pruneline from the command line. That's handy on very big sites, or to check several sites in one go. The commands only read: cleaning up is done on Tools → Pruneline, after an export.

Scan

wp pruneline scan

Runs a full scan with a progress bar, then prints "Scan finished." The results show on Tools → Pruneline too.

List an audit

wp pruneline list blocks --view=missing
wp pruneline list templates --view=none --format=csv > templates.csv
wp pruneline list blocks --item=acme/slider

Prints one list, with an id column first and then the same columns as on the screen. If no scan has finished yet, it warns you to run wp pruneline scan first.

Audit Tab on the screen Views (--view)
blocks Blocks missing, unsure (needs confirmation)
builders Page builders → Missing widgets & modules elementor, beaver, siteorigin, bricks, oxygen, divi, wpbakery
templates Page builders → Templates none (no reference found), used, conditions
patterns Patterns & parts none, used
usage Elementor → Widget usage none
hidden Elementor → Hidden everywhere none
plugins What breaks active, inactive, deleted
data Leftover data option, table, events, meta, unknown
Option Values
--view One of the views above. Leave it out for every row.
--item One row's detail, by the value in its id column: a block name (acme/slider), a builder and widget (elementor|acme-price-table), a template's ID, a pattern (pattern:12, part:mytheme//header, navigation:34), a page (post:56) or a plugin (plugin:acme-slider/acme-slider.php). The hidden and data audits have no detail.
--format table (the default), csv, json or count 
wp pruneline report > report.json

Prints the handover report's data as JSON.