Various parts and features of Studio can be configured to suit your needs. This can be done in the following ways:
- By enabling or disabling features in the Management Console. This is a user-friendly way of changing some of the configuration settings.
- By manually modifying configuration files. Through these files all settings can be configured and easily transferred when upgrading to a newer version of Studio.
Enabling or disabling features in the Management Console
To ease the process of configuring Studio, certain features can be enabled or disabled by using the Management Console.
Step 1. In Studio Server, access the Management Console for Studio by clicking Integrations > Studio.
Step 2. In the menu, choose Features.
The Features page appears, showing all features that can be enabled or disabled through this page.
Figure: The Features page in the Management Console can be used for enabling or disabling specific features.
Step 3. For each feature, verify if it needs to be enabled or disabled.
Notes:
|
Step 4. Let the Studio users log out and log back in for these changes to take effect.
Manually modifying configuration files
Info: Performing the described steps requires direct server access. Depending upon how your system is hosted and the level of access you have to that system, coordination may be required with your Partner or WoodWing Support team. For a full overview of the steps that need to be done by WoodWing and how to request them, see WoodWing Cloud - Change management.
Configuring Studio can also be done by directly modifying the configuration files that are part of Studio and the Studio Server instance in which Studio is installed.
Notes:
|
Tip: To edit these files, open them in a plain-text editor such as Notepad, TextEdit, or TextWrangler.
Files as part of Studio
The following files are part of the installation of Studio:
File | Remarks |
---|---|
config.js |
This file is used for configuring general Studio settings. This is typically done when installing Studio. The file is part of the Studio installation on Studio Server: <Studio Server path>/contentstation |
config.php |
This file is used for configuring various settings for Studio. It is part of the Studio plug-in that is installed on Studio Server: <Studio Server path>/config/plugins/ContentStation |
config-glyphs.js |
This file is used for configuring the glyphs in the Print editor. It is part of the Studio installation on Studio Server: <Studio Server path>/contentstation |
config-white-spaces.js |
This file is used for configuring the white spaces in the Print editor. It is part of the Studio installation on Studio Server: <Studio Server path>/contentstation |
Files as part of Studio Server
The following files are part of the installation of Studio Server:
File | Remarks |
---|---|
configserver.php |
This file for Studio Server is used for configuring settings for all Studio users who log in to that server: <Studio Server path>/StudioServer/config |
confiig_overrule.php |
The config_overrule.php file overrules any settings that are configured in various configuration files of Studio Server such as those mentioned above. This way, configuration can be done in a central location, and the configured settings can be easily migrated whenever Studio Server is upgraded. It is therefore recommended to use the config_overrule file instead of any specific configuration files. |
The following tables shows how the features as shown in the Management Console are mapped to Studio Server options:
Note: These features need to be configured as part of the SERVERFEATURES option.
Example: Here, the feature PublicationOverviewMaxGridViewZoom has been added to the configserver.php file:
|
For the Digital editor
Feature | Studio Server option |
---|---|
Keep the article checked-out as long as it is opened | ContentStationDigitalEditorLockWhenOpen |
Images have to be stored in Assets | ContentStationDigitalEditorEnforceElvis |
Disable cropping for images stored in Assets Server | ContentStationDigitalEditorCroppingDisabled |
Disable uploading files | ContentStationDigitalEditorUploadDisabled |
For the Print editor
Feature | Studio Server option |
---|---|
Keep the article checked-out as long as it is opened | ContentStationPrintEditorLockWhenOpen |
Accept all Tracked Changes when opening the article | ContentStationDisableEditorAutoSave |
Disable the article preview | ContentStationDisableEditorPreview |
Disable the article preview auto refresh | ContentStationDisableAutoRefreshPreview |
Disable auto save | ContentStationDisableEditorAutoSave |
For the Publication Overview Application
Feature | Studio Server option |
---|---|
Prevent page previews from being used as thumbnails1 | PublicationOverviewGridPreventPreviewLoading |
Control the maximum zoom level for page thumbnails | PublicationOverviewMaxGridViewZoom |
Disable automatic updating of publication information | PublicationOverviewDisableBroadcastMessaging |
1 To make sure that the page thumbnails do not become too pixelated by zooming in on them too much, limit the maximum zoom level by setting the 'Control the maximum zoom level for page thumbnails' option).
Where to find information
For information about the settings see the comments in the configuration files as well as the articles in the following sections of the Help Center:
- Studio
- General configuration
- Digital articles
- General configuration
- Digital editor
- Print articles
- General configuration
- Print editor
- Publication Overview
- General configuration
- Studio Server
- General configuration
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.