Recovery tools · Field guide 05
WordPress Settings History vs Activity Log vs Backup
The short answer.
Settings history explains which configuration values changed and can support a targeted undo. An activity log records events and actors. A backup restores a saved slice of site state. Each has a different evidence and restore scope.
Read the practical guideSettings history, activity logs, and backups answer three different questions.
Their labels overlap, but their evidence and restore scope do not. Identify the incident before choosing the recovery system.
Settings history
What values changed?
Investigates and can reverse one observed Core or plugin settings save.
Activity log
Who did what?
Establishes event sequence, actor accountability, and unusual administrative actions.
Backup
What state can we restore?
Restores a saved state after broad damage or failure across files and database layers.
One wrong option needs a smaller restore than unknown site damage.
A one-field mistake rarely justifies replacing a full database. An unknown compromise or corrupted site should not be treated as a one-option undo.
- 01
Narrow configuration error
Use settings evidence and a conflict-checked targeted reversal when the original save was observed.
- 02
Accountability question
Use an activity log to establish the actor and sequence, then pair it with deeper evidence if values matter.
- 03
Broad or unknown damage
Preserve the current state and recover a tested backup in a controlled environment.
Evidence stays in WordPress. A conflict, redacted value, incomplete observation, or unsupported storage path prevents automatic Undo.
Read the support contractRecovery procedure
Match the request. Check the current value. Choose the restore scope.
The tools compared
Before-and-after values caused by an observed save
Supported values that still pass a conflict check
Actor, event, and time, depending on coverage
Usually none by itself
A snapshot existed at a point in time
Files, tables, or site state included in the snapshot
The installed code version
Plugin or theme files, not necessarily configuration
Use settings history for a known configuration save
Use settings history when the incident began with a Core or plugin configuration save and you need to know the exact before-and-after values. The strongest record groups every supported write caused by that request and retains enough context to identify the user, time, screen, and component.
ConfigOps adds a recovery condition that historical logs usually lack: before Undo, it checks that the current database value still matches the recorded post-save state. This keeps an old observation from silently overwriting a legitimate newer edit.
Use an activity log for actor and event sequence
Use an activity log when accountability and event sequence matter: logins, role changes, content actions, plugin activation, or settings events. Coverage depends on the log and its integrations, so verify exactly what it records.
An event such as “settings updated” may locate the incident without revealing the affected values. Pair activity history with settings evidence when both actor attribution and value-level diagnosis are required.
Use a backup for broad or unknown damage
Use a tested backup when damage spans multiple layers, the site or admin is unavailable, the cause is uncertain, or there is no trustworthy targeted recovery path. Define whether the restore replaces files, database tables, uploads, or the entire environment.
Before restoring, preserve the current state and account for orders, submissions, comments, and content created since the backup. Test the recovery on staging when possible. A broad restore can fix broad damage, but it can also erase healthy post-backup work.
Use tested backups for broad recovery, activity evidence for accountability, and settings history for a specific configuration save.
Sources and next steps
Undo boundaries
Can ConfigOps undo this save?
Check whether the request was observed, its evidence is complete, and current values still match.
Can an activity log undo a WordPress setting?
Usually not by itself. It may identify the event and actor without storing the complete old value or a safe recovery condition.
Is a backup safer than a targeted settings undo?
It depends on incident scope. Backups are essential for broad recovery but can overwrite unrelated newer work when used for a narrow mistake.
Do I still need backups if I use ConfigOps?
Yes. ConfigOps deliberately does not restore files, content, code, custom tables without adapters, caches, or remote service state.