Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
72:cms_configuration [2019/03/19 17:09] – [Sharepoint] tssr72:cms_configuration [2019/03/20 07:39] – [Common Configuration] tssr
Line 6: Line 6:
 The configuration for these systems is done in two simple steps: The configuration for these systems is done in two simple steps:
  
-  - Add the XML snippet explained in [[72:cms_configuration#Common Configuration | this section]] to your Stages configuration file for each configuration management system you want to work with+  - Add the XML snippet explained in [[72:cms_configuration#Common Configuration | this section]] to your Stages configuration for each configuration management system you want to work with
   - Adjust this snippet for the specific configuration management system according to the explanations below   - Adjust this snippet for the specific configuration management system according to the explanations below
  
Line 41: Line 41:
 The configuration has to have one **<cms-type>** element for every content management system you want to support in your Stages application. The attribute __name__ of each **<cms-type>** is crucial for the system to work. Every CMS implementation has its own and unique __name__. The configuration has to have one **<cms-type>** element for every content management system you want to support in your Stages application. The attribute __name__ of each **<cms-type>** is crucial for the system to work. Every CMS implementation has its own and unique __name__.
  
-Right after the **<cms-type>** element you can define multiple **<cms-property>** elements, which are in effect for the entire type.+Right after the **<cms-type>** element you can define multiple **<cms-property>** elements, which affect the entire type. These properties are called global properties.
 The attribute __name__ identifies the property by its key. The __value__ attribute defines the value for that property. The attribute __name__ identifies the property by its key. The __value__ attribute defines the value for that property.
  
Line 49: Line 49:
 The __ident__ of a **<cms-host>** has to be unique for this stages server. The __name__ attribute identifies the server name of the content management system. This name has to have a protocol and the host name (without any path e.g. /some/path). The display name of the host will be shown in the host dropdown selection field in the Stages Web-GUI. The __ident__ of a **<cms-host>** has to be unique for this stages server. The __name__ attribute identifies the server name of the content management system. This name has to have a protocol and the host name (without any path e.g. /some/path). The display name of the host will be shown in the host dropdown selection field in the Stages Web-GUI.
  
-Inside of a **<cms-host>** element you can define **<cms-property>** elements, which are in effect only for the specific host.+Inside of a **<cms-host>** element you can define **<cms-property>** elements, which affect only the specific host. These properties are called host properties.
  
 ==== Subversion ==== ==== Subversion ====