wp-cli

A bloated EWWW IO image backup folder appears when the disk fills. Learn the backup mechanism, official trimming paths, and safety criteria before deleting.

TL;DR: A production server hit 100 percent disk usage, and the EWWW Image Optimizer backup folder turned out to hold 14 gigabytes. The folder grows from pre-optimization originals, downscaled originals, and WebP copies, each with its own official cleanup command. Verify an independent, restorable backup first, map the folder composition, then run the matching command.

WP_HOME only fools new pages; old URLs live in the database. WP-CLI search-replace with dry-run and skip-columns=guid is the fix.

TL;DR: Moving a WordPress production dump locally means changing WP_HOME and WP_SITEURL won't fix URLs already stored across posts, meta, and serialized options. Raw SQL REPLACE() is risky because it breaks PHP serialized length prefixes and can overflow column limits. Instead, use wp search-replace with a --dry-run first, always skipping the guid column since those permalinks must never change.