Embedding the EnvBar as the first element in the body tag doesn't always work well for all sites.

What do you think of providing the EnvBar via a template variable, e.g. $EnvBar and providing a config option to disable the automatic embedding.

On the front end, the environment indicator bar doesn't appear for pages which use a controller that extends the index method and return an array.

If a header (or some other element, for that matter) is fixed to the top of the page, the environment indicator will be hidden.

Hey, I just noticed this module pop up and overlap with this SS3 module, and just wanted to share a thought on the meaning of environments in SilverStripe. From the docs of that module:

Note: SilverStripe has a concept of 'environment type' (SS_ENVIRONMENT_TYPE) which can be set to 'live', 'test' or 'dev'. This is more like a 'mode' than a type though, because there is nothing to stop you temporarily setting your production environment type to 'dev' to get some debugging information, or your development environment to 'live' to simulate production configuration locally. So you can't really rely on the environment type to know which server environment you're interacting with. SS_ENVIRONMENT_LABEL is intended to be a genuine constant, so you can have clarity about which environment you are working on.

In that other module I decided to introduce a SS_ENVIRONMENT_LABEL to account for that and also make the naming and number of environments more flexible.

Anyways feel free to delete this, just wanted to point that out :) Nice to see an SS4 solution for this problem in the wild.

It would be nice to have a setting in the SilverStripe admin area that allows users to turn the environment indicator off.

The admin user needs to be able to disable the bar from a setting in the cms in case there is an issue in production.