Repository navigation
Upgrade from WPHouse
Use this page if a site runs WPHouse, the name SafeHouse had before version 0.2.0. Version 0.2.0 renamed the plugin folder and file, the WP-CLI command, the wp-config.php constants and everything stored in the database to the shouse prefix. SafeHouse moves an existing site's data over on its own when you activate it.
| Before (WPHouse) | From 0.2.0 (SafeHouse) |
|---|---|
| WPHouse plugin | shouse/shouse.php |
wp wphouse … |
wp shouse … |
WPHOUSE_* constants |
SHOUSE_* constants |
wp-content/wphouse-safe-mode |
wp-content/shouse-safe-mode |
wphouse_* options and tables |
shouse_* options and tables |
wp-admin/admin.php?page=wphouse |
wp-admin/admin.php?page=shouse |
Warning
Activate SafeHouse before you delete WPHouse. Deleting WPHouse removes everything stored under the old names, so deleting it first would delete your settings, the activity log and the login limit records.
-
Back up the database.
-
Install SafeHouse 0.2.0 or later from its ZIP. It goes into its own folder,
wp-content/plugins/shouse, next to WPHouse. -
Deactivate WPHouse.
-
Activate SafeHouse.
On activation, SafeHouse renames every
wphouse_option and transient toshouse_, renames the activity log and login limit tables, and replaces the old scheduled tasks with its own. If an option already exists under the new name, the new one is kept. -
Open SafeHouse and check that your modules and settings are as before, and that the Activity log shows the earlier entries.
-
Delete WPHouse on the Plugins screen.
If the migration cannot finish on activation, SafeHouse retries it on every page load until it has finished.
If the site used the WPHouse Redis object cache, install the SafeHouse loader once:
wp shouse object-cache enableUntil you do, WordPress uses its own cache and the site keeps working, only slower. See Redis object cache.
You do not have to change everything at once:
-
WPHOUSE_*constants inwp-config.phpkeep working. SafeHouse reads each one as itsSHOUSE_*twin. If both are defined, theSHOUSE_*one wins. Rename them when convenient. - A
wp-content/wphouse-safe-modefile still turns safe mode on, andwp shouse safe-mode offremoves it. - Login limits still accepts the device cookies browsers got from WPHouse, until they expire.
- The old settings page address redirects to the new one.
Update scripts that call wp wphouse: that command no longer exists.
These pages describe SafeHouse 0.2.0 and were last reviewed on 2026-10-07. · Repository · Releases · Changelog · Report a problem with these pages
Search every page and heading in the Pages box.
Start here
Modules
- All modules
- Security: Hardening · Login limits · Bot protection · Install lockdown
- Alerts: Change alerts · Plugin health · Vulnerability alerts
- Performance: LiteSpeed page cache · Cloudflare cache · Redis object cache
- WooCommerce: Omnibus price history
- Site tools: SMTP mail · Header and footer scripts · Duplicate posts and pages · Maintenance mode · Tweaks
Guides
- Behind Cloudflare or a proxy
- Running with Wordfence
- Configure in wp-config
- Deploy with git or CI
- Replacing other plugins
- Upgrade from WPHouse
Reference
Trust
Help