Documentation · 0.7.0
Settings history · conflict-checked Undo
The undo button
WordPress forgot.
ConfigOps records the option writes behind authorized WordPress settings saves and reverses only values that still match. Version 0.7.0 adds tested WooCommerce settings evidence and explicitly authorized, guarded agent Undo for one site mutation at a time.
- Release
- 0.7.0 · WooCommerce + guarded agent Undo
- Runtime
- WordPress 7.0–7.1 · PHP 8.2–8.5
- Storage
- Local database · no account
- Test coverage
- 78.90% production lines · 79.92% trust-boundary lines
Actual product evidence · no mockup
Save normally. ConfigOps appears with the evidence.
A WordPress Reading Settings save produced six writes: one likely decision and five housekeeping writes. Review and safe Undo appeared without starting a Change Session.
Automatic evidence card · tap for the full settings screen
Available since 0.5.0 · structural proof before action
Undo plugin settings without waiting for an adapter.
Enable Smart Undo per site. ConfigOps offers it only when the complete associative-array patch agrees with both snapshots, every target still matches, and no adapter owns the option.
Smart Undo policy · tap for the full Plugin support screen
From settings save to Undo decision
Read the evidence in order.
- 01
Save one setting
Use wp-admin normally. ConfigOps opens an isolated observation on the first Options API write.
Observation boundaries → - 02
Read what actually happened
Separate intended settings from housekeeping writes, secrets, and unmanaged effects.
Review anatomy → - 03
Undo only matching state
ConfigOps checks current values, snapshots, ownership, references, and observation completeness before writing. Human confirmation remains the default; an explicitly authorized service user can request one guarded mutation Undo through the same checks.
Undo contract →
The line ConfigOps will not cross
Evidence is not a backup.
ConfigOps does not promise transactional rollback, copy media, deploy content, synchronize databases, or invent support for unknown custom tables. If evidence is incomplete or option ownership is ambiguous, ConfigOps hides Undo and leaves the current value untouched.