1. Scott Winterroth

    Something new and useful! Thanks WordPress!


  2. John Blackbourn

    This is the first plugin on WordPress.org to make use of the new function

    Except Query Monitor of course ;-)

    It’s worth noting there are a couple of tickets in the 5.5.1 milestone which may potentially change the behaviour of this functionality, although they are yet to be discussed at length.

    Consider adding “local” as environment on WP_ENVIRONMENT_TYPE: https://core.trac.wordpress.org/ticket/51064
    Consider removing the ability to alter the list of environment types: https://core.trac.wordpress.org/ticket/50992


    • Anh Tran

      Interesting tickets! Thanks for sharing.

      Personally, I think defining a general list of environment types such as production, staging, development is crucial and it makes the terminology consistent between developers. Users also can be able to add their own environment types if needed, but not removing the core ones.


    • Brandon Kraft

      Jetpack too!

      Jetpack has had a “Staging Site” mode for sometime, but it was triggered through a list of known staging sites (e.g. the standard staging URL from a WP Engine site) or someone adding out specific filter/constant.

      I think it is a huge win that there is a standard way so now any non-production site will trigger Jetpack’s staging mode.



  3. Roy Tanck

    Thank you for writing about my plugin. Just to clarify, it does also show the environment type for staging (yellow) and development (green) servers.

    On the front end, it’ll only display the environment type for admins only, while within wp-admin it’ll display for all users. There’s a filter hook to further customize this behavior to fit your use case.


  4. Tim - Timdehoog.nl

    Thank you for sharing this information.

    It is also useful when using different database credentials, fixed paths or urls. You can store them all in one file, for example wp-config.php.

    The plugin is also very useful to tell clients on which environment they are working. This is to prevent that clients are working on staging but expect that they are working on production.


  5. Nigel

    This helps the gradual shift of power from developers to website implementers. It could make it easier to set up a staging site on cheap entry-level shared hosting.


Comments are closed.

%d bloggers like this: