Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
74:cms_configuration [2019/10/16 10:18] – [Common Configuration] tssr | 74:cms_configuration [2020/08/27 11:31] – tssr | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== CMS Configuration ====== | ====== CMS Configuration ====== | ||
- | Stages can interact with configuration management systems | + | Stages can interact with configuration management systems to work with remotely stored files. The configuration for these systems is done in two simple steps: |
- | - Add the XML snippet explained in [[: | + | - Add the xml snippet explained in [[: |
- 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 11: | Line 11: | ||
* [[: | * [[: | ||
* [[: | * [[: | ||
+ | * [[: | ||
Line 45: | Line 46: | ||
> cms | > cms | ||
- | * Description: This element holds all configuration data for content management systems. | + | * __Description__: This element holds all configuration data for content management systems. |
> cms-type | Attributes: name | > cms-type | Attributes: name | ||
- | * Description: The cms-type element represents the configuration for a single content management system you want to support in your Stages application. | + | * __Description__: The cms-type element represents the configuration for a single content management system you want to support in your Stages application. |
- | * Attributes: | + | * __Attributes__: |
* //name//: The attribute name of each cms-type is crucial for the system to work. Every cms implementation has its own and unique name. | * //name//: The attribute name of each cms-type is crucial for the system to work. Every cms implementation has its own and unique name. | ||
> cms-property | Attributes: name, value | //<!-- Global Properties -->// | > cms-property | Attributes: name, value | //<!-- Global Properties -->// | ||
- | * Description: Inside the cms-type element you can define multiple cms-property elements, which affect the entire cms type. These properties are called global properties. | + | * __Description__: Inside the cms-type element you can define multiple cms-property elements, which affect the entire cms type. These properties are called global properties. |
- | * Attributes: | + | * __Attributes__: |
* //name//: The attribute name identifies the property by its key. | * //name//: The attribute name identifies the property by its key. | ||
*//value//: The value attribute defines the value for that property. | *//value//: The value attribute defines the value for that property. | ||
Line 62: | Line 63: | ||
> cms-host | Attributes: ident, name, displayName | > cms-host | Attributes: ident, name, displayName | ||
- | * Description: Every cms-type element can have several cms-host elements. Each cms-host represents an endpoint, Stages can establish a connection and exchange data. | + | * __Description__: Every cms-type element can have several cms-host elements. Each cms-host represents an endpoint, Stages can establish a connection and exchange data. |
- | * Attributes: | + | * __Attributes__: |
* //ident//: The ident of a cms-host is a simple string but has to be unique for the Stages server. | * //ident//: The ident of a cms-host is a simple string but has to be unique for the Stages server. | ||
* //name//: The name attribute identifies the server by the url of the content management system. Please note that this url must contain the **protocol**, | * //name//: The name attribute identifies the server by the url of the content management system. Please note that this url must contain the **protocol**, | ||
Line 70: | Line 71: | ||
> cms-property | Attributes: name, value | //<!-- Host Properties -->// | > cms-property | Attributes: name, value | //<!-- Host Properties -->// | ||
- | * Description: Inside a cms-host element you can define cms-property elements, which affect only the specific host. These properties are called host properties. | + | * __Description__: Inside a cms-host element you can define cms-property elements, which affect only the specific host. These properties are called host properties. |
- | * Attributes: | + | * __Attributes__: |
* //name//: The attribute name identifies the property by its key. | * //name//: The attribute name identifies the property by its key. | ||
* //value//: The value attribute defines the value for that property. | * //value//: The value attribute defines the value for that property. | ||
+ | ====== Repository Configuration ====== | ||
+ | |||
+ | To add, remove or edit a repository, navigate to " | ||
+ | |||
+ | **Add a repository** | ||
+ | The following picture shows, how to add a new repository. | ||
+ | {{ : | ||
+ | |||
+ | **Edit a repository** | ||
+ | To Edit an existing repository, click on its name or open the menu and click " | ||
+ | |||
+ | **Remove a repository** | ||
+ | To remove a repository, open the menu on the right of the repository you want to delete. Then select " | ||
+ | |||
+ | ======= Repository Errors ======= | ||
+ | |||
+ | Repository errors are shown next to the menu button on the right of each repository list entry. | ||
+ | The following errors can occur: | ||
+ | |||
+ | * The host-ID is not configured in the config.xml | ||
+ | * There are system-credentials missing for that repository (OAuth based systems only) | ||
+ | |||
+ | The following figure shows, how these errors look like, when you click on the error-indicators (yellow exclamation mark) | ||
+ | |||
+ | {{ : | ||