loading table of contents...

8.1.13. Site-specific configuration of Document Forms

With the SiteAwareVisibilityPlugin, you can show or hide document form elements (for example, property fields) depending of the activation of a "feature" for a specific site.

The SiteAwareVisibilityPlugin takes a parameter called "feature", which is a name for the feature. You can group two or more plugins by giving them the same feature name.

If you configure any ExtJS Component to use this plugin, that component only becomes visible when this feature is configured to be active for the site that the current content belongs to.

By default, the configuration for features of a site is done in a CMSettings document, which has to be named <SITE_ROOT_FOLDER>/Options/Settings/Studio Features

This settings bundle consists of a StringList named "features" and contains the string values that in turn need to be configured as desired in the SiteAwareVisibilityPlugin.

Example Usage

This plugin is used in the demo content of the Brand Blueprint. It hides the property editors for the "Call-To-Action-Button" and "Externally Displayed Date" in the Perfect Chef site, because these properties are not used in these templates, but are only used in the Brand Blueprint.