ConfigOps – Undo Settings Changes
The undo button WordPress forgot
WordPress shows you the settings form. ConfigOps shows you what the save actually changed.
Change a supported WordPress or plugin setting as usual. ConfigOps automatically opens an isolated observation for that save, groups the resulting writes, and reduces repeated writes to the same option into the original-to-final change.
A compact evidence card then tells you how many values WordPress wrote, links directly to an understandable review, and offers whole-save Undo only when the complete change is still safe to restore.
One action. The hidden writes behind it. A clear diff. A conflict-checked undo.
WordPress Change Intelligence
ConfigOps is not a generic activity log. It does more than report that somebody clicked Save: it records the supported Options API writes caused by the request, separates likely decisions from plugin housekeeping, and attributes the responsible component and code path where possible.
ConfigOps is not a backup. It restores only supported setting values that still match the recorded state, so a later legitimate change is not silently overwritten.
ConfigOps is not plugin-version rollback. It works with configuration values, not plugin or theme code.
What you get
- Automatic local evidence for authorized settings changes made through WordPress admin, REST, and WP-CLI requests.
- Plain-language nested diffs that turn option arrays into recognizable settings.
- Immediate Review and safe Undo feedback after a settings save.
- Named Change Sessions for planned maintenance, support cases, and investigations that span several requests.
- Provenance for the user, request, component, and code path where ConfigOps can determine it.
- Secret redaction before mutation history is stored.
- Conflict checks before every restore.
Safety before convenience
Probable credentials are removed before mutation history is stored. Undo first checks that the current value still matches the observed value. An interrupted or incomplete observation loses whole-save undo instead of pretending its evidence is safe.
Direct writes to custom plugin tables are recorded as value-free warnings. ConfigOps does not store raw SQL and does not claim it can reverse data it does not understand.
Site icons, site logos, and supported Yoast logo and social-image settings show the referenced attachment name, file type, dimensions, thumbnail, and missing state. Yoast publisher-policy, content-ignore, and LLMs.txt page IDs show bounded page identity instead of a bare database ID. ConfigOps never copies or deletes referenced media or content.
All evidence remains in the website database. ConfigOps does not send observation data to pyrra or another external service. Suggested disclosure text is added to WordPress’s privacy-policy guide.
Tested component contracts
The current release includes pinned adapters for:
- WordPress Core 7.0
- WP Mail SMTP Free 4.9.0
- Yoast SEO Free 28.2
The Plugin support screen states exactly which WordPress and plugin capabilities are supported, limited, or not available. An untested component version keeps its observed evidence but disables automatic undo.
Version 0.3 scope
Version 0.3 is a local, single-site undo and evidence layer for supported WordPress settings. It is not a staging plugin, backup, content migration, database synchronization, fleet manager, or generic activity log.