Can I Reverse All WP Ghost Settings to Restore My Site?

Moved

This tutorial has moved to the new WP Ghost Knowledge Base where each feature is presented in detail.

View on new site

Yes. Every WP Ghost setting is fully reversible. You can revert individual settings, rollback all settings to defaults, or deactivate and delete the plugin entirely. In every case, your site returns to its exact pre-WP Ghost state. No files are modified, no database schema is changed, and no permanent traces are left behind.

Three Ways to Reverse Settings

Change individual settings. Every path, toggle, and configuration option in WP Ghost can be changed or turned off independently. If you want to keep WP Ghost active but revert a specific path to its default, go to the relevant settings page, clear the custom value, and save. That single path reverts to the WordPress default while all other WP Ghost protections stay active.

Rollback all settings to defaults. Go to WP Ghost > Change Paths and set the Level of Security to Default. Click Save. This removes all custom paths, disables all protection features, and returns WP Ghost to its initial unconfigured state. The plugin remains installed but inactive. You can reconfigure from scratch or load a preset at any time. For more recovery options, see the Rollback Settings tutorial.

Deactivate and delete the plugin. Deactivating WP Ghost from the Plugins page instantly reverts every path change, removes firewall rules from .htaccess, and restores all WordPress defaults. Your login page goes back to /wp-login.php, your admin returns to /wp-admin, and every plugin, theme, and asset path loads from its original location. Deleting the plugin afterward removes all WP Ghost data from the database. Your site is returned to its exact state before WP Ghost was installed.

Why It’s Fully Reversible

WP Ghost never modifies WordPress core files, plugin files, or theme files. All changes are applied at runtime through server rewrite rules (in .htaccess on Apache or config files on Nginx) and WordPress hooks. When WP Ghost is deactivated, the rewrite rules are removed and the hooks stop running. There is nothing to “undo” because nothing was permanently changed. The reversibility is a direct result of the architecture: runtime changes, not file modifications.

If You Cannot Access the Dashboard

If a setting causes a conflict and you cannot reach the WordPress admin to reverse it, WP Ghost provides multiple emergency recovery methods. Use the Safe URL parameter to bypass all protections for a single request. Use the Pause 5 Minutes button on the Plugins page. Or disable WP Ghost entirely via FTP by renaming the plugin folder or adding define('HMWP_DISABLE', true); to wp-config.php. All of these restore default WordPress paths immediately. For the full walkthrough, see the Emergency Disable tutorial.

Frequently Asked Questions

If I deactivate WP Ghost, are my settings saved for later?

Yes. Deactivating the plugin removes all runtime changes but preserves your configuration in the database. If you reactivate WP Ghost later, all your previous settings are restored automatically. Deleting the plugin removes the saved settings permanently.

Will deactivating cause 404 errors or broken links?

Not on your public pages. Posts, pages, and media URLs are not affected by WP Ghost, so they continue working normally. The only URLs that change are the WordPress-specific paths WP Ghost was managing (admin, login, plugin paths, etc.), which revert to their defaults. Clear all cache after deactivating to avoid stale references. See the Preventing 404 Errors After Deactivating guide for details.

Can I export my settings before reverting, in case I want them back?

Yes. Go to WP Ghost > Backup/Restore and create a backup before making any changes. The backup file saves your entire configuration. You can import it later to restore your previous setup.

Does WP Ghost modify WordPress core files?

No. This is precisely why everything is fully reversible. WP Ghost uses rewrite rules and WordPress filters at runtime. No files are modified, so deactivation leaves no trace.