Linux 软件免费装
Banner图

Dotance Settings History and Restore

开发者 dotance
更新时间 2026年10月9日 07:32
PHP版本: 7.4 及以上
WordPress版本: 7.1
版权: GPLv2 or later
版权网址: 版权信息

标签

restore history settings rollback undo

下载

1.1.0

详情介绍:

WordPress keeps revisions for posts and pages. It keeps nothing for settings. Save the wrong value on a plugin's options screen, or watch a colleague change something on Friday evening, and there is no history to go back to. Dotance Settings History and Restore is that history. It records every real change to the options table made by a logged-in user – in WordPress itself, in any plugin, in any theme – and puts a timeline under Tools → Settings Undo with an Undo button on every entry. What you see for each change Undo and roll back Know when something critical changes Designed to be quiet A settings log is only useful if it is readable, so the plugin does not record everything. Transients, cron state, rewrite rules, update-check timestamps, cache keys and plugin version bumps are ignored. One settings form save that writes twelve options is one card in the timeline, not twelve. A plugin that changes a value and puts it straight back within the same request leaves no entry. Changes made by cron, WP-CLI or anonymous requests are off by default and can be switched on, and you can add your own option names (with * wildcards) to the ignore list on the Settings tab. Safe by default Export, WP-CLI and REST For developers Not in this version: multisite network options, and post content (WordPress revisions already cover that).

安装:

  1. Upload the settings-undo folder to /wp-content/plugins/, or install it from the Plugins screen.
  2. Activate it. The history tables are created on activation.
  3. Go to Tools → Settings Undo. Save any settings page and it will appear there.

屏幕截图:

  • Inside a change set: every option the save touched, with Diff and Undo per row.
  • A key-level diff of an array option, collapsed to the keys that changed.
  • Undoing a protected option asks you to type its name.
  • Rolling back to a checkpoint: a preview of every option before anything changes.
  • Settings: retention, what is recorded, noisy options, critical-change alerts.

升级注意事项:

1.1.0 Adds checkpoints and rollback, update markers, critical-change alerts, export, WP-CLI and a redesigned screen. A second table is created automatically on upgrade. 1.0.2 Recreates the history table automatically if a migration or restore dropped it. 1.0.0 First release.

常见问题:

Does it slow the site down?

No. Nothing runs on the front end for visitors, apart from the admin-bar menu for logged-in administrators, which you can switch off. Recording happens only when an option actually changes, and only after a cheap check that the option is not on the ignore list. Reading the timeline is a handful of queries per page.

Why does a change I made not appear?

Either the option is on the ignore list (transients, cron, caches, version numbers and similar noise), or the value was written by a background process – cron, WP-CLI or an anonymous request – which is not recorded unless you switch that on under Settings.

How does a checkpoint work?

It records a position in the history, not a copy of your database. Rolling back replays the earliest recorded value of every option changed since then, shows you the result first, and lets you untick anything you want to keep. It can only restore settings the plugin recorded, so a checkpoint is only as complete as the history behind it.

Can I undo activating or deactivating a plugin?

The active_plugins option is recorded and can be restored, with a typed confirmation. Note that restoring the list does not run a plugin's own activation or deactivation routines.

Where is the data stored?

In two tables, {prefix}settings_undo_log and {prefix}settings_undo_marks (checkpoints, update markers and notes). Uninstalling the plugin leaves them in place unless "delete data on uninstall" is enabled.

Is the diff available for every change?

Values larger than 512 KB (serialised) are logged as "too large to store": you can see that the option changed, who changed it and when, but not the values, and they cannot be undone. The cap can be raised with the settings_undo_max_value_size filter.

Does it work on multisite?

This version is built and tested for single sites. Network options are not recorded.

更新日志:

1.1.0 1.0.2 1.0.1 1.0.0