Keep the database clean, on a schedule.
Post revisions, contact-form spam, and duplicate drafts bloat your database quietly. Cap the growth, clear the cruft, then let the cleanup run itself every week, with no extra plugin to stack.
It grows in the dark. Until queries crawl.
A page edited fifty times keeps fifty revisions. Contact Form 7 with Flamingo stores every submission, spam included. Duplicate drafts linger in the tables. None of it shows day to day, but it slows queries and bloats every backup you take.
The cleanup tools, in one bar.
Every command runs from the navigator, fits into a macro, and can be put on a schedule.
Revision control
Cap revisions with limit revisions, then clear the backlog with clear revisions.
Form-spam cleanup
Clear Contact Form 7 and Flamingo messages with clear flamingo, with a dry-run preview.
Duplicate finder
find duplicate content surfaces duplicate posts, pages, and products by title or content.
One macro
Chain the recurring steps into a single Macro Command you run, or schedule, as a unit.
On a schedule
Scheduled Commands runs the macro on the cron slot you pick, overnight when traffic is low.
Execution logs
Each scheduled run is logged, so you can confirm the cleanup ran and what it removed.
Set it up once. Then forget it.
The cap is a one-time setting; the recurring cleanup is a macro the scheduler runs for you.
Cap revisions
Run
limit revisions -total=5once. WordPress now keeps only the last five revisions per post.Build the cleanup macro
In the Macro Builder, chain clear revisions, clear flamingo, and find duplicate content.
Schedule it weekly
Hand the macro to Scheduled Commands, pick a quiet overnight slot, and the database stays lean on its own.
One plugin. Cleanup and nine more modules.
Scheduled database cleanup is not a separate purchase. It is one workflow inside TrueCommander.
Questions, answered.
limit revisions -total=5 first means you always keep the five most recent.clear flamingo -type=spam -dry-run=true and it reports what it would remove without deleting anything. When you are happy, run the same command without -dry-run. You can also limit it to a date range with -from and -to.A leaner database, every week.
Cap the growth, chain the cleanup, and let the scheduler keep it lean, on one install.