A practical recovery boundary
Devenia Revision Retention: Recover the Revisions You Need, Weeks Later
A rollback is useful only when the revision history still holds a state close enough to undo the change or old enough to restore missing context.
Only a site administrator with permission to manage WordPress settings can use the retention controls.
Default retention
Two recovery horizons in one policy
A useful record serves both the edit you need to reverse and the earlier state you may need to reconstruct.
Latest 10 revisions
Use the ten newest records for ordinary recovery after a content change.
Five older anchor revisions
At roughly 1, 2, 3, 4, and 10 weeks back, these spaced positions preserve context when the close window cannot reconstruct what the page contained.
Read the boundary
Inspect the policy before a run
In Tools > Revision Retention, the read-only settings view shows the configured scope and current status without changing or deleting a revision.
Supported post types
The default scope covers posts and pages.
Parent selection limit
A run examines no more than 100 parent items.
Revision deletion limit
One run can delete no more than 500 revisions by default.
Schedule interval
Retention is enabled by default and runs every 1,440 minutes.
Current status
Use the status field to decide whether a manual dry run adds useful evidence.
Dry run before cleanup
Know what remains before you act
The cleanup run starts as a dry run, so it assesses the policy without deleting a revision. Permanent cleanup requires an explicit request after that assessment.
Read the candidate list
Start without deletion to see which records the policy would retain and which it would exclude.
Check what must stay
Compare the keep side with the states your site may need later.
Carry the reviewed decision forward
Inspection and execution follow one policy result, so the selected keep side cannot change between the two modes.
Authorize permanent cleanup
The dry run and cleanup use the same retention policy decision, so the decision reviewed before cleanup remains the basis for an explicit deletion request.
Respect the configured batch
The cleanup pass stops at its configured ceilings rather than exceeding the approved batch.
Required runtime and optional connection
What the package needs to run
Check the environment and connection requirements before installation.
WordPress 6.9 or later
WordPress Abilities API in WordPress 6.9 or laterProvides revision, scheduling, settings, and native ability registration surfaces.
PHP 7.2 or later
PHP 7.2 or laterSupplies the PHP runtime used by the package.
Optional for MCP client access
WordPress MCP AdapterExposes registered WordPress abilities to MCP clients.
One useful first action
Put the recovery boundary into practice
Download the stable self-hosted package if your site needs both a close rollback window and older reference points.
After installation, start with the no-deletion assessment so the first cleanup decision is based on the records the policy selects.