Context
When importing a production site into a staging or development environment, sensitive data comes along for the ride: API keys, payment gateway credentials, user emails, WooCommerce orders, and more. The Safety Net plugin by Team 51 is purpose-built for exactly this scenario — it scrubs dangerous options, deactivates risky plugins, deletes user data, blocks outgoing emails, and pauses subscription renewals.
Proposal
After a successful site import, offer to install and activate Safety Net on the destination site. This would protect staging/dev environments from accidentally sending real emails, processing payments, or leaking data.
Possible integration points:
- Post-import hook: Once the import completes, automatically install and activate Safety Net if the destination environment type is
staging, development, or local.
- CLI flag: Something like
--safety-net that triggers Safety Net activation as a final import step.
- Interactive prompt: Ask the user whether to activate Safety Net after import finishes.
Safety Net already has WP-CLI commands (wp safety-net scrub-options, wp safety-net deactivate-plugins, wp safety-net delete) that could be invoked programmatically after import.
Why this matters
Today, anyone using the importer to clone a production site into a dev environment has to manually remember to sanitize it. Forgetting means real emails go out, real payments get processed, and search engines index staging content. Integrating Safety Net makes the safe path the default path.
Context
When importing a production site into a staging or development environment, sensitive data comes along for the ride: API keys, payment gateway credentials, user emails, WooCommerce orders, and more. The Safety Net plugin by Team 51 is purpose-built for exactly this scenario — it scrubs dangerous options, deactivates risky plugins, deletes user data, blocks outgoing emails, and pauses subscription renewals.
Proposal
After a successful site import, offer to install and activate Safety Net on the destination site. This would protect staging/dev environments from accidentally sending real emails, processing payments, or leaking data.
Possible integration points:
staging,development, orlocal.--safety-netthat triggers Safety Net activation as a final import step.Safety Net already has WP-CLI commands (
wp safety-net scrub-options,wp safety-net deactivate-plugins,wp safety-net delete) that could be invoked programmatically after import.Why this matters
Today, anyone using the importer to clone a production site into a dev environment has to manually remember to sanitize it. Forgetting means real emails go out, real payments get processed, and search engines index staging content. Integrating Safety Net makes the safe path the default path.