by
pyrra
1 (0 reviews)
ConfigOps – Configuration Management
Capture, reproduce, and safely undo WordPress configuration with redacted evidence and private portable Packs.
ConfigOps ranks #56,401 among WordPress.org plugins with 1+ active installations, a 1/5 rating from 0 reviews, and was last updated Aug 25, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Compatible with WP 7.1
v0.7.0
Current Version v0.7.0
Updated 2 months ago
Last Update on 25 Aug, 2026
Refreshed 1 week ago
Last Refreshed on
Rank
#56,401
—
No change
Active Installs
1+
—
No change
KW Avg Position
175
6 worse
Downloads
443
+1 today
Support Resolved
0%
—
No change
Rating
20%
Review 1 out of 5
1
(0 reviews)
Next Milestone 10
0+
10+
43,464
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 7 more installs to reach 10+
Rank Changes
Current
#56,401
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
1.0
0 reviews
Overall
20%
5
0
(0%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 0.7.0
- Last Updated
- Aug 25, 2026
- Requires WP
- 7.0+
- Tested Up To
- 7.1
- PHP Version
- 8.2 or higher
- Author
- pyrra
Support & Rating
- Rating
- ★ ☆ ☆ ☆ ☆ 1
- Reviews
- 0
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade Now
Frequently Asked Questions
Common questions about ConfigOps – Configuration Management
Not generically. ConfigOps records a value-free warning when it observes a direct database write, but understanding or reversing a custom table requires an explicit adapter.
No. An activity log records events, a backup restores a broad site state, and plugin rollback replaces code. ConfigOps explains the supported setting writes behind a save and restores only values that still pass its safety checks.
ConfigOps observes supported Options API mutations in authorized WordPress admin, REST, and WP-CLI requests. It does not record anonymous front-end traffic as settings evidence. Named Change Sessions are available when you want to group several requests into one investigation. WP-CLI's optional --user parameter is not required for observation. A shell-authorized command without a WordPress user is recorded with actor ID 0. If another plugin virtualizes a site or network target through an Options API read filter, ConfigOps refuses undo before writing instead of treating the virtual value as stored database state.
Yes. Version 0.7 supports network activation, isolated per-site evidence, lifecycle and retention across sites, Multi-Network ownership boundaries, and a separate Network Admin ledger for supported Network Options changes. Named Network Change Sessions can group a planned task, and complete network additions and updates can be undone one mutation at a time. Packs remain site-scoped; Network Packs, network deletes, whole-network-change undo, cross-site aggregation, and bulk actions are not supported.
A Pack is strict JSON containing a format and schema version, stable Pack identity and version, a name and description, WordPress/plugin requirements, and a list of desired option states pinned to adapter schemas. It contains no before-state, database metadata, SQL, PHP, callbacks, or executable templates. Reserved variable and extension objects must remain empty in schema version 1. Export is conservative: only complete, restorable, non-secret options owned by a currently available tested adapter are selectable. Import repeats those checks against the destination. A warning is not an automatic rewrite; remove a questionable setting from the preview or configure that value explicitly after Apply.
Yes. ConfigOps is agent-ready through site-scoped native WordPress Abilities and machine-readable JSON WP-CLI commands for authenticated state, capture and mutation reads, named capture control, restore planning, and deliberately authorized single-mutation undo. The same discoverable abilities can be exposed by compatible MCP adapters. Use a dedicated least-privilege WordPress service user. Mutation evidence may contain non-secret configuration values, even though probable credentials are removed before storage. Do not grant configops_apply unless the agent may actually change settings. The danger acknowledgement skips human confirmation but never the normal safety checks. Generic option-writing tools are not available. Example commands: wp --user=configops-agent configops state wp --user=configops-agent configops captures list --limit=20 wp --user=configops-agent configops restore plan --mutation=842 wp --user=configops-agent configops restore apply --mutation=842 --dangerously-run-undo
Complete generic Options API values already use exact current-value checks. Site administrators can additionally enable Verified key undo for plugin arrays under Support contracts. For unclaimed associative wp_options updates, it cross-checks the complete patch against both typed snapshots, reverses only captured target keys, and preserves unrelated later keys. Current adapter ownership and current parent shapes are checked again before apply. It refuses secrets, root replacements, integer-keyed parent arrays, list-index edits, redacted or truncated evidence, malformed or overlapping paths, autoload drift, adapter-owned options, and any target key that changed again.
Probable secret fields and options are replaced before persistence. Supported adapters may undo neighboring non-secret fields while preserving the current credential. ConfigOps never reconstructs a redacted secret.
No. ConfigOps restores supported Options API values after a conflict check. Side effects in files, caches, remote services, or custom tables may remain. The interface states when undo is limited or unavailable. If earlier referenced media or content has since been deleted or moved to the trash, ConfigOps refuses to restore its local ID.
The host settings request is allowed to finish. ConfigOps marks the observation incomplete through a value-free emergency marker and disables whole-save undo after storage recovers.