Understand every change before you undo it.
Learn how ConfigOps observes WordPress settings saves, separates decisions from technical noise, removes probable secrets, and refuses Undo when the evidence is no longer safe.
- Runtime
- WordPress 7.0+ · PHP 8.2–8.5
- Storage
- Your WordPress database
- Retention
- 30 days by default
- Account
- None required
Follow the evidence.
The shortest useful path from activation to a safe decision.
Install and make one reversible save.
Confirm the runtime contract, activate ConfigOps, and begin with a setting you can verify.
Get startedRead what WordPress actually wrote.
Separate likely decisions, derived state, redacted values, and unmanaged effects.
Read the evidenceUndo only matching current state.
Understand conflict checks, reference validation, adapter versions, and refusal conditions.
Review the Undo contract
The documentation follows the product evidence.
ConfigOps groups one request into a readable review. The docs explain what each layer means and where certainty stops—using the same settings, classifications, and safety states you see in the plugin.
Learn the review anatomy
Evidence is not a backup.
ConfigOps does not promise transactional rollback, reconstruct secrets, deploy content, or invent support for unknown custom tables. When evidence is incomplete, capability disappears instead of uncertainty being hidden.