Issue: When opening an article that was created with InDesign CS4 or InCopy CS4 in Content Station 9, an 'unexpected' error appears.
Solution: Use temporary folders as defined by the WEBEDITDIR setting in Enterprise Server for investigating the stored files, and optionally send them to WoodWing Support.
WEBEDITDIR
- File: configserver.php file
-
Name of option: WEBEDITDIR
- Possible values: the location where the Enterprise Server will put files for use by the InDesign Server(s)
- Default setting: a folder as defined by WOODWINGSYSTEMDIRECTORY
- Example: (for all platforms)
define ('WEBEDITDIR', WOODWINGSYSTEMDIRECTORY.'/WebEdit/');
The default values for the WOODWINGSYSTEMDIRECTORY are:
- Mac OS: /FileStore/_SYSTEM_
- Windows: c:\FileStore\_SYSTEM_
Therefore, the resolved default location of WEBEDITDIR is:
- Mac OS: /FileStore/_SYSTEM_/WebEdit
- Windows: c:\FileStore\_SYSTEM_\WebEdit
Note: It is important that Enterprise Server has Read and Write access to the following folder:
|
WEBEDITDIRIDSERV
- File: configserver.php file
-
Name of option: WEBEDITDIRIDSERV
- Possible values: The location where the InDesign Server(s) will look up files that have been made available by the Enterprise Server. Typically this is a mounted (network) folder. Physically the folder is the same folder as defined in the WEBEDITDIR setting. The InDesign Server process must be able to read existing files and write new files to this folder.
- Default setting: a folder as defined by WOODWINGSYSTEMDIRECTORY
- Examples:
In these examples, WebEdit is a share created on the Enterprise Servers machine mounted on the InDesign Servers machine. The share gives read/write access to the InDesign Server process and is mapped onto the WEBEDITDIR location on the Enterprise servers machine.
define ('WEBEDITDIRIDSERV', WOODWINGSYSTEMDIRECTORY.'/WebEdit/');
define (WEBEDITDIRIDSERV, /Volumes/WebEdit/);
define (WEBEDITDIRIDSERV, //170.0.0.101/WebEdit/);
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.