When working with Content Station results in unexpected behavior, errors or crashes, error logging can be enabled to assist with troubleshooting the cause of the problems.
Setting the debug level
In case working with Content Station results in unexpected behavior or errors, SQL queries and Web service details can often provide an indication of where it goes wrong.
This information can be logged by enabling the following option:
- File: WWSettings.xml file
- Name of option: DebugLevel
-
Area: Between the
tags<SCEnt:ContentStation> </SCEnt:ContentStation>
- Possible values:
- NONE
- ERROR
- WARN
- INFO
- DEBUG
The amount of information that is stored increases with each option: NONE saves no information while DEBUG stores the highest amount of information.
Note: Fatal errors are logged in the php.log file. Normally, this file is not present in the server log folder, indicating that there are no fatal errors.
- Default value: NONE
- Example:
<Setting name=”DebugLevel” value=”NONE”/>
Important: Make sure to validate the WWSettings.xml file for correct content. See Validating the WWSettings.xml file.
Setting the log folder location
The folder where the log file of the current session (named ContentStation_yymmdd_hhmmss.log) is written to is defined through the following option:
- File: WWSettings.xml file
- Name of option: LogFolder
-
Area: Between the
tags<SCEnt:ContentStation> </SCEnt:ContentStation>
- Possible value: the path to the folder in which the files should be stored.
Note: When no path is defined, the feature is disabled.
- Example:
<Setting name=”LogFolder” value=”/Users/username/logs/”/>
Important: Make sure to validate the WWSettings.xml file for correct content. See Validating the WWSettings.xml file.
Related Tasks
Location of the Content Station 9 configuration files
Logging Enterprise Server 9 activity
Reference Materials
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.