Environment Tagging
Environment tags allow to have specific behaviours only in specific context. Environment of blocks/pages allows you to create blocks visible only on some websites using the theme.
Page / Blocks tagging
If you have blocks / pages that should be visible in some context, for example you only want to show Guest Portal blocks for clients using the Guest Portal, you can use the field "environment".
Variable tagging
With variables environment tagging, you can control the visibility of a CMS variable in the backoffice.
The local website will still receive the variable if there is a value stored
Indeed you could have a variable visible only for a specific role, but not for other roles for example.
Manually add environments to a website
In an effort to standardize how environments are added, the "Environment" field in Website Parameters is no longer editable (exept for Admins).
Environments can now only be added via Automations. Please contact us on Asana for more details.
Extension Environment tag
Sometimes, you want specific sections of the backoffice to be visible automatically when adding the Extension to the website
For example, for IBE project, some sections in the unit should only be visible when in the context of an "IBE website"
For this, add the extension key inside Testeur for the global setting (don't forget to commit the file theme/data modified by Testeur)
When the extension will be added to a website, it will automatically add to it the environment and show the sections.
Create new environment in the backoffice
This is only available for admin team of the environment. On your dev environment you can add new environments, on production / preprod you have to do a request to an admin.
Galaxy > System > Environments
Each environment has:
a key (the one used inside testeur)
a name (the one visible in the website settings)
To create a new environment, click on the "ADD" button.
From this list you can see:
the environments
where they are used
Last updated