Hey, this site is undergoing a redesign process in the open, so things may look weird from time to time.

Hide WP Engine Legacy Staging

Published on

I haven't published a plugin to the WordPress plugin repository in a while, since I hurried to push out Update Privacy (when I found out the data WordPress sends on every update check). Anyway. WP Engine is generally great for WordPress hosting* but they have confused things with Legacy Staging.

Staging used to mean you'd get a copy of the Production site that you could copy to and from, accessible from within the WP dashboard. So far so simple. Then they moved to "1 site contains 3 environments", namely Production, Staging and Development. These have different CNAMEs. Which is cool, as that fits even better with our workflow. But those old staging sites can still be created, and now they're called Legacy Staging. Each environment can have a legacy staging copy, meaning one website can have 6 versions kicking around. Now when people refer to staging, which one do they mean? Which one are your clients talking about?

We're solving this at work with process and good communications, but I also want to remove the confusion by hiding "Legacy Staging" from within the WordPress dashboard, so everyone's clear that we're talking about the staging environment, not a legacy copy.

Hence another WordPress plugin: Hide WP Engine Legacy Staging. It simply hides the Legacy Staging links from within the WordPress dashboard, which will reduce confusion and hopefully avoid deploying to the wrong staging copy (it has been known...). All the details are on the plugin page. If it helps, or if you get any issues, do let me know.

By the way, Dominik Schilling's plugin deploy script takes the pain out of using interacting with SVN :)

We found out this week that WPE's migration / backup restore tool chokes on DB stored procedures. Sometimes it fails but actually says it suceeds, and sometimes the other way round. But either way it won't copy the stored precedure.