Getting started
Requirements
What Pruneline needs to run, where it keeps its data, and what it works alongside.
Server and WordPress
| Minimum | |
|---|---|
| WordPress | 6.5 |
| PHP | 7.4 (8.1 or later recommended) |
| WooCommerce | Not needed |
Tools → Pruneline and Settings → Pruneline are for administrators. The scan runs while Tools → Pruneline is open, a few seconds at a time, through the WordPress REST API (as the block editor does). On very big sites, you can scan from the command line instead: see WP-CLI.
Where Pruneline keeps its data
| What | Where |
|---|---|
| The scan's index: every block, widget, module and reference found, and where | The table {prefix}pruneline_refs (usually wp_pruneline_refs) |
| What each installed (and deleted) plugin and theme brings: its blocks, widgets, options, tables and scheduled events | The option pruneline_owners |
| The scan's progress | The option pruneline_scan |
| Blocks seen in the block editor in the last 30 days | The option pruneline_editor_blocks |
| Settings | The option pruneline_settings |
| The table's version | The option pruneline_db_version |
| How many rows a list shows | The user meta pruneline_per_page |
Pruneline never changes your content by itself. On multisite, each site has its own data.
Works alongside
- Page builders: Pruneline reads the layouts of Elementor, Beaver Builder, SiteOrigin Page Builder, Bricks, Oxygen, Divi and WPBakery. See Page builders and templates.
- Block themes and classic themes: both. With a block theme, template parts and the theme's template files are read too.
- WooCommerce: not needed. Products are scanned like pages. Orders aren't scanned.
- Action Scheduler: when a plugin brings it, pending actions without a handler are listed as leftover data.
- Bracketline: Pruneline doesn't audit shortcodes in general. With Bracketline, our free shortcode audit, active, What breaks also counts each plugin's shortcodes, and the Elementor editor panel links to Bracketline.
- WP-CLI: see WP-CLI.