BetterShield
Appearance
Activity logSettingsRecovery

Undo WordPress setting changes: save old values and put them back

· · 9 min read

To undo a WordPress setting change, you need to know what the setting was before someone changed it, and BetterShield can keep that for you. Turn on Save old values so I can undo changes and it saves the earlier value of a few key settings, roles, plugins and administrator accounts. Each saved change can then be reviewed and, where it is supported, put back with one confirmed click.

The activity log already tells you that something changed. Our guide to the WordPress activity log covers what it records and how its sealed days work. This post is about the next step: keeping the old value so a surprise does not have to be solved from memory.

Quick summary

  • The feature is called Undo important setting changes, on BetterShield › Activity › Site activity. Saving old values is off until you turn it on.
  • It saves the earlier value of the default role for new accounts, public registration, the administration email address, the WordPress address, a role’s permissions, a plugin that was turned on and an account made an administrator.
  • Review Change shows the old value, the new value and the current value side by side.
  • Restore Old Value puts a supported value back, and Suspend This Account blocks a new administrator without deleting it. Undo the Restore and Lift Suspension reverse them.
  • Nothing is restored on its own, and a later edit is never overwritten.

Why it matters

Most settings changes are ordinary. A colleague turns on registration for an event, a developer activates a plugin to test something, an email address is updated after a handover. The trouble is the one that nobody remembers making. When a site starts behaving differently, the useful question is not who to blame but what the value was before.

Without a saved old value, you rebuild it from a backup, a screenshot or a guess. With one, the log row carries the before and after, and the way back is one confirmation away. It also keeps the calm tone this plugin tries to hold: a listed change is not necessarily harmful, and BetterShield says so on the screen.

What the feature does

Open BetterShield › Activity › Site activity. Above the activity list is a panel called Undo important setting changes. Select the small chevron button, labelled Show details, to open it. The panel explains itself in two sentences: it saves the old value when key settings, roles, plugins or admin accounts change so you can put them back, and nothing changes automatically.

Here is what it can keep, and how each one appears in the list:

What changedHow it reads in the list
Default role for new accountsDefault role for new accounts changed
Public registrationPublic registration changed
Administration email addressAdministration email address changed
WordPress addressWordPress address changed
A role’s permissionsThe role’s permissions changed
A pluginPlugin turned on
A new administratorAccount made an administrator

The panel keeps up to 1,000 saved changes, and the counter in it shows how many you have used. The documentation adds two limits: 20 captures in one request and 100 in one hour. Busy moments and checkout pages are not saved.

Set it up

  1. Open BetterShield › Activity › Site activity and select Show details on the Undo important setting changes panel.
  2. Tick Save old values so I can undo changes.
  3. Select Save. The button stays disabled until you change the checkbox, so a saved state is easy to tell from an unsaved one.
  4. Make sure a recovery method works before you rely on responses. A working recovery method is required for them, and safe mode must be off. Set up recovery walks through it.

Only changes made after you turn it on are saved. Nothing from before can be reconstructed.

Review a recorded change

Rows that have a saved value gain a Review Change button. Selecting it opens Review recorded change, which shows three things for a setting: the Old value, the New value and the Current value. For a role, it lists what the role can now do and what it can no longer do. For a new administrator, it says that a new administrator was recorded.

Reading this is safe. It changes nothing. If no old value was saved, the panel says so and suggests checking the related WordPress screen and who made the change. It also says not to delete an account just because it is listed.

Put a setting back

On a supported setting, select Restore Old Value. BetterShield asks you to confirm with Yes, Put It Back, saves the current state first so the restore can itself be undone, and then puts the old value in place. The activity entry names what was put back.

Two cases are handled differently on purpose:

  • A plugin. Restoring turns the plugin off, but it does not undo anything the plugin already changed. Undo the Restore turns it back on.
  • The WordPress address. The documentation says BetterShield never restores this one automatically. Open the settings screen it points to, check the current value yourself and change it there if you need to.

If someone edited the setting again after the recorded change, BetterShield refuses to overwrite that newer value. It tells you that some changes, such as later edits or protected accounts, cannot be restored from here.

Suspend a new administrator

A new administrator you do not recognize is a good reason to act quickly and a bad reason to delete anything. On a row that shows an account made an administrator, Suspend This Account blocks that administrator from signing in or using application passwords. Nothing is deleted. It pauses while safe mode is on, and it will not run when no other administrator would remain.

Suspended accounts appear in their own list, Account suspensions, with Let Back In beside each one. Lift Suspension does the same from the review panel. Suspension also pauses while recovery mode or another sign-in protection is active, and the list says so next to the account.

What an AI assistant can do with it

This panel is a screen for administrators who sign in, so it is not a route for an assistant. What a connected assistant may read or change is set separately, and WordPress MCP write access: approvals, limits and undo covers it.

What it can break, and how to undo

Restoring a value changes live configuration, so treat it like any other change to the site. BetterShield protects you from the obvious mistake by refusing to overwrite a later edit, and it saves the current state before it restores, so Undo the Restore works while the setting stays unchanged.

If a restore does not finish, the panel says so: it did not finish, so check the setting before trying again. Nothing is half-applied behind your back. If you restored the wrong value, undo it, and the recorded entry shows the sequence.

Saved values can include administration email addresses, and they are kept after the log entry ends. Treat them as personal data. Privacy and personal data explains what BetterShield keeps and how to remove it, and an uninstall with data removal turned on deletes these saved values too.

Check it is working

  1. Turn on Save old values so I can undo changes and select Save.
  2. Make a safe test change that the feature supports, for example the Default role for new accounts on a staging copy.
  3. Return to Activity › Site activity and find the row for it.
  4. Select Review Change and confirm the Old value, New value and Current value all appear.
  5. Select Restore Old Value, confirm, and check the setting is back. Then use Undo the Restore if you want the new value again.

The panel’s counter also moves by one for each saved change, which is a quick sign that saving is working.

We recommend turning on Save old values so I can undo changes on sites where more than one person can change settings, or where an administrator might be added in a hurry. The saved values wait in the panel until you need them.

We recommend looking at Review Change before Restore Old Value, every time. The review is the point: it shows the old, new and current value, and you decide. Pair it with asking for a password before removing a protection, so a protection cannot be lowered without a check in the first place. For a wider routine when an administrator account looks wrong, a first-hour response plan lays out what to do next. If you are cleaning up after a change that locked you out, recovery mode and a recovery link explain how to get back in.

WordPress itself describes how permissions are built from roles and capabilities in the developer handbook on roles and capabilities, which helps when you are reading a role’s Can now and Can no longer lists.

Frequently asked questions

Is saving old values on by default?

No. It is off until you tick Save old values so I can undo changes and select Save. Only changes made after that are saved.

Does BetterShield restore anything automatically?

No. It saves old values and shows them. A person has to choose Restore Old Value or Suspend This Account and confirm it. The WordPress address is never restored automatically.

What happens if someone changed the setting again after the recorded change?

BetterShield will not overwrite the newer value. Some changes, such as later edits or protected accounts, cannot be restored from this panel, and the review says so.

Does suspending an administrator delete the account?

No. It blocks that account from signing in or using application passwords, nothing is deleted, and Lift Suspension or Let Back In reverses it.

Where can I find the entry afterwards?

In the activity log. The row for a restored setting names what was put back, and undoing a restore is recorded too. Filter and search site activity shows how to find it.

Conclusion

Saving old values turns a surprise setting change into something you can read and, where it is supported, reverse. Review the Old value, the New value and the Current value, restore only what you mean to, and suspend a new administrator rather than deleting it.

BetterShield is free on WordPress.org. The docs cover the details: Record previous values and respond to changes and Activity log.

Close the open doors today

Install the free plugin. The first audit runs when you activate it, and all but one of the fixes wait for your choice.

Requires WordPress 6.7 or newer and PHP 8.0 or newer.

Get BetterShield