Configuring Content Station 9 is done through the following files:
- configserver.php file. This file is part of Enterprise Server and is used for configuring settings for all Content Station users who log in to that Server.
- componentDefs.xml file. This file is part of Enterprise Server and controls paragraph styles, character styles, and/or CSS styles that can be applied to text in an article, as well as the article components that can be added to an article. Settings made in this file affect all Content Station users who log in to that Server.
- WWSettings.xml file. This file is located on the same system on which Content Station is run. Configuring settings in this file only affects Content Station on that system. It is used for configuring general Content Station settings.
- ApplicationMapping.xml. This file is located on the same system on which Content Station is run. Configuring settings in this file only affects Content Station on that system. It is used for configuring the applications that are opened when double-clicking a file in Content Station.
Tip: To edit these files, open them in a plain-text editor such as Notepad, TextEdit, or TextWrangler.
Note: When editing PHP, always use forward slashes ‘/’ as path separators, and make sure to keep the correct PHP syntax.
The locations of these files are as follows:
configserver.php file and componentDefs.xml file
These files are stored on Enterprise Server:
- <Enterprise Server path>/Enterprise/config
WWSettings.xml file and ApplicationMapping.xml file
These files are stored locally on each system on which Content Station is installed:
Mac OS X
- /Library/Application Support/WoodWing
Windows
- c:\ProgramData\WoodWing
Note: This folder is hidden by default. To display this folder, change the folder options. (See the Windows Help file.)
Important: Make sure to validate the WWSettings.xml file for correct content. See Validating the WWSettings.xml file.
Comment
Do you have corrections or additional information about this article? Leave a comment! Do you have a question about what is described in this article? Please contact Support.
0 comments
Please sign in to leave a comment.