Thirty private versions
Configuration history stores up to thirty administrator-only versions. Save a named snapshot before a launch, mark important versions as favorites, or rely on automatic safety versions created by normal settings saves and imports.
- Named manual snapshots
- Automatic before-and-after safety versions
- Up to fifteen protected favorites
- Duplicate configurations reuse one record
Exact semantic diffs
Every non-current version shows how many values differ. Review changes groups machine-readable paths by design, components, Community Engine, Email Studio, routes, or shells. Export timestamps, plugin-version metadata, and CRLF-versus-LF browser differences do not create noisy changes.
Reversible rollback
Restore sanitizes every section again, resolves templates by slug, preserves unavailable routes as unmapped, and first saves the current state as a safety version. A rollback can therefore be reversed without rebuilding settings manually.
Safe bounded storage
Versions use the same secret-excluding portable contract as JSON export. License data, provider secrets, WebSocket addresses, two-factor credentials, passkeys, member records, and content never enter history. Payloads are compressed, stored with autoload disabled, deduplicated, and removed on uninstall unless data preservation is enabled.
Administrator protection
Only users with manage_options can save, favorite, restore, or delete versions. Each action has its own WordPress nonce, and configuration history adds no public REST endpoint.