This article is part of a series that describes how to use Elvis 6 with Adobe InDesign.
In this article, the process of enabling logging is described.
Enabling logging
To troubleshoot technical issues that may occur when using the Elvis InDesign client, logging can be enabled.
The features and functionality depends on the installed plug-ins:
- Only the Elvis InDesign client is installed, not Smart Connection
- The Elvis InDesign client as well as Smart Connection is installed
Each scenario is described below.
Only Elvis InDesign client is installed
When only the Elvis InDesign client is installed, the following features are available:
- Enabling or disabling logging is done through the preferences of InDesign.
- Default logging areas and logging levels are used which cannot be modified.
- The names of the log files are Log_InDesign.txt and Log_InDesignServer.txt.
- The Logging folder can be quickly accessed through the preferences of InDesign.
Enabling or disabling logging
Enabling or disabling logging is done through the following Preferences in InDesign:
Preferences > WoodWing > Enable Logging
Quickly accessing the log folder
The log folder can be quickly accessed through the following option in the Preferences of InDesign:
Preferences > WoodWing > Open Log Folder
Location of the log files
The log files are stored in the following location:
- Mac OS X: /Users/<user_name>/Library/Application Support/WoodWing.noindex
- Windows: c:\Users\<user_name>\AppData\Local\WoodWing
Elvis InDesign client and Smart Connection are installed
When the Elvis InDesign client is installed together with Smart Connection, the following features are available:
- Enabling or disabling logging is done by modifying the WWSettings.xml file or through the preferences of InDesign.
- When logging is enabled through the WWSettings.xml file, the logging areas and logging levels to use can be specified.
- When logging is enabled by setting the Preference, default logging areas and logging levels are used.
- Depending on the installed plug-ins, separate log files are created for Elvis and Smart Connection or the logging is combined into one file.
- The names of the log files are:
- For Smart Connection: WWLog_InDesign.txt and WWLog_InDesignServer.txt
- For Elvis or Elvis and Smart Connection combined: Log_InDesign.txt, and Log_InDesignServer.txt.
- The Logging folder can be quickly accessed through the preferences of InDesign.
Enabling or disabling logging
Enabling or disabling logging is done by modifying the WWSettings.xml file (by system administrators), through the Preferences in InDesign (by end users), or through scripting (for InDesign Server).
This method is for system administrators who want to make sure that users use a specific method. When setting the method through the WWSettings.xml file, the corresponding Preference in InDesign (see below) is disabled, thereby preventing these users from changing the setting.
Enabling logging is done by enabling the logging for Smart Connection. For more information, see Logging Smart Connection activity.
Enable or disable logging through the following Preference in InDesign:
Preferences > WoodWing > Enable Logging
Note: When the system administrator has configured the setting through the WWSettings.xml file, the Preference cannot be changed.
To enable or disable logging through scripting, set the following option to 'true' or 'false':
Application.woodwingLogging
After setting the option, logging is immediately affected.
Quickly accessing the log folder
The log folder can be quickly accessed through the following option in the Preferences of InDesign:
Preferences > WoodWing > Open Log Folder
Location of the log files
The log files are stored in the following location:
- MacOS: /Users/<user_name>/Library/Application Support/WoodWing.noindex
- Windows: c:\Users\<user_name>\AppData\Local\WoodWing
Log file creation
By default, the log files for the Elvis InDesign client and for Smart Connection are created separately but can combined into a single file named: Log_ through either the Preferences or 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.