Title: ConfigOps – Undo Settings Changes Author: pyrra Published: 16 Agoosto, 2026 Last modified: 16 Agoosto, 2026 --- Raadi kaabayaal ![](https://ps.w.org/configops/assets/banner-772x250.png?rev=3650204) ![](https://ps.w.org/configops/assets/icon.svg?rev=3649955) # ConfigOps – Undo Settings Changes Qore [pyrra](https://profiles.wordpress.org/pyrra/) [Soo Rog](https://downloads.wordpress.org/plugin/configops.0.3.0.zip) * [Faahfaahin](https://so.wordpress.org/plugins/configops/#description) * [Dibu-eegisyo](https://so.wordpress.org/plugins/configops/#reviews) * [Rakibaad](https://so.wordpress.org/plugins/configops/#installation) * [Horumarinta](https://so.wordpress.org/plugins/configops/#developers) [Taageero](https://wordpress.org/support/plugin/configops/) ## Sharraxaad #### 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. ## Sawir-shaashado [⌊Save a supported setting normally and ConfigOps immediately shows the observed writes, likely decision, housekeeping, Review, and safe Undo.⌉⌊Save a supported setting normally and ConfigOps immediately shows the observed writes, likely decision, housekeeping, Review, and safe Undo.⌉[ Save a supported setting normally and ConfigOps immediately shows the observed writes, likely decision, housekeeping, Review, and safe Undo. [⌊See the supported WP Mail SMTP decisions behind one save while the changed SMTP password is removed before storage.⌉⌊See the supported WP Mail SMTP decisions behind one save while the changed SMTP password is removed before storage.⌉[ See the supported WP Mail SMTP decisions behind one save while the changed SMTP password is removed before storage. [⌊See one Yoast SEO toggle as one understandable XML sitemaps decision with its conflict-checked Undo action.⌉⌊See one Yoast SEO toggle as one understandable XML sitemaps decision with its conflict-checked Undo action.⌉[ See one Yoast SEO toggle as one understandable XML sitemaps decision with its conflict- checked Undo action. ## Rakibaad 1. Upload the ConfigOps ZIP through Plugins > Add Plugin > Upload Plugin. 2. Activate ConfigOps. 3. Change one WordPress or plugin setting as usual. 4. Use the ConfigOps evidence card to review the hidden writes or undo a fully safe save. 5. For a multi-request task, open ConfigOps and start a named Change Session. ## SBI ### Does ConfigOps observe custom plugin tables? 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. ### Is ConfigOps an activity log, backup, or plugin rollback tool? 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. ### What does ConfigOps record automatically? 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. ### Are secrets stored in the mutation history? 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. ### Is rollback guaranteed? 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. ### What happens when observation storage fails? 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. ### How long is local history kept? While ConfigOps is active, completed and interrupted observations are kept for 30 days by default. Cleanup is bounded and never selects an active Change Session. Developers may change the window with the `configops_retention_days` filter. Uninstalling ConfigOps removes its observation history, installation options, scheduled cleanup, and capabilities. ### How do I report a security issue? Email felix@pyrra.net. Do not post credentials, configuration values, database exports, or customer data in a public support thread. ## Dibu-eegisyo Ma jiraan wax dibu-eegis ah oo ku saabsan kaabahan. ## Ka-qaybgalayaasha & Horumariyayaasha “ConfigOps – Undo Settings Changes” waa softiweer il furan. Dadka soo socda ayaa wax ku biiriyay kaabahan. Ka-qaybgalayaasha * [ pyrra ](https://profiles.wordpress.org/pyrra/) [Ku tarjun “ConfigOps – Undo Settings Changes” luqaddaada.](https://translate.wordpress.org/projects/wp-plugins/configops) ### Ma xiisaynaysaa horumarinta? [Baadh koodka](https://plugins.trac.wordpress.org/browser/configops/), fiiri [bakhaarka SVN](https://plugins.svn.wordpress.org/configops/), ama iska qor [diiwaanka horumarinta](https://plugins.trac.wordpress.org/log/configops/) adigoo adeegsanaya [RSS](https://plugins.trac.wordpress.org/log/configops/?limit=100&mode=stop_on_copy&format=rss). ## Isbeddellada #### 0.3.0 * Records authorized settings saves automatically in isolated request-local observations. * Shows immediate evidence with write, decision, technical, and protected-secret counts plus direct Review and safe Undo actions. * Keeps named Change Sessions as the focused mode for planned multi-request work. * Preserves automatic observations and named Change Sessions as distinct modes through the schema, review, retention, and uninstall lifecycle. * Repositions ConfigOps as the undo and evidence layer for WordPress settings with a new directory title, description, and artwork. #### 0.2.0 * Supports PHP 8.2 through 8.5 with full minimum-runtime and endpoint browser contracts. * Enforces 70% production and 75% trust-boundary PHP line coverage in CI. * Adds hostile-input, warning/deprecation, dependency-advisory, and runtime-lifecycle gates. * Builds a byte-reproducible release archive before WordPress Plugin Check. * Publishes a complete operator, safety, support, and development documentation site through GitHub Pages. #### 0.1.0 * First technical preview by pyrra. * Explicit local captures with request grouping and source attribution. * Local intent correlation matches touched admin-field names and labels to saved option paths without reading field values or expanding undo permissions. * Same-request option-write chains collapse to their original and final state; complete same-owner reverts disappear from review. * Typed nested diffs, conservative noise classification, and secret redaction before persistence. * A WordPress Core 7.0 settings contract for General, Writing, Reading, Discussion, Media, and Permalink settings. * Conflict-checked field and session undo with value-free audit records and compensating recovery. * Exact deep-field contracts for every bundled WP Mail SMTP Free 4.9.0 mailer and the Yoast SEO Free 28.2 feature, crawl, schema, search, social, and LLMs.txt families. * Media and content identity review for WordPress site icons/logos and supported Yoast image/page fields, including missing-target undo protection. * Fail-closed capture finalization, schema recovery, bounded 30-day retention, and integrity warnings. * Performance-budgeted React review interface with responsive and keyboard-tested states. ## Meta * Version **0.3.0** * Last updated **11 saac kahor** * Active installations **In ka yar 10** * WordPress version ** 7.0 ama ka sareeya ** * Tested up to **7.0.4** * PHP version ** 8.2 ama ka sareeya ** * Language * [English (US)](https://wordpress.org/plugins/configops/) * Tags * [configuration](https://so.wordpress.org/plugins/tags/configuration/)[developer-tools](https://so.wordpress.org/plugins/tags/developer-tools/) [history](https://so.wordpress.org/plugins/tags/history/)[rollback](https://so.wordpress.org/plugins/tags/rollback/) [settings](https://so.wordpress.org/plugins/tags/settings/) * [Aragti Sare](https://so.wordpress.org/plugins/configops/advanced/) ## Qiimeynta No reviews have been submitted yet. [Your review](https://wordpress.org/support/plugin/configops/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/configops/reviews/) ## Ka-qaybgalayaasha * [ pyrra ](https://profiles.wordpress.org/pyrra/) ## Taageero Ma heysaa waxaad dhahdo? Caawimaad ma u baahan tahay? [Eeg madasha taageerada](https://wordpress.org/support/plugin/configops/)