This section describes how to configure Content Studio via the config file.
The file should be called
com.enonic.app.contentstudio.cfg and placed into the
$XP_HOME/config folder of your XP installation.
Defines matching mode for content type patterns. Can be
MATCH. See description.
contentTypePatternMode = MATCH
Used for setting size limit on attachments, media content and both project and content thumbnail uploads
uploadMaxFileSize = 100mb
Turn off automatic transliteration of content path when generating it based on a value typed into the display name field in the Content form.
|You may need to tweak CSP settings in Content Studio only if you are building a widget which will be embedded inside Content Studio where you want to allow references to external resources or other potentially unsafe (from the CSP point of view) actions. If CSP errors appear when your content is rendered (when you preview or edit content in Content Studio), then you need to configure CSP settings in XP admin config.|
You can provide your own header for Content Security Policy using
contentSecurityPolicy.header property. For example, Google Analytics injects its own scripts referring to external domains, so we are using the following CSP headers for the Google Analytics widget not to be blocked in Content Studio:
contentSecurityPolicy.header=default-src 'self'; connect-src 'self' ws: wss: https://*.gstatic.com https://*.googleapis.com; script-src 'self' 'unsafe-eval' 'unsafe-inline' https://*.google.com https://*.googleapis.com https://*.gstatic.com; object-src 'none'; style-src 'self' 'unsafe-inline' https://*.gstatic.com; img-src 'self' data:; frame-src 'self' https://*.googleapis.com
Turn off Content Security Policy by setting
contentSecurityPolicy.enabled property to
Default Content Project is not shown in Content Studio by default.
If you need the Default project (for example, you already have content in it and want to continue working with it after upgrading to Content Studio 5), enable it by setting
settings.hideDefaultProject property to
|If the Default project is hidden (default behaviour) and a logged-in user doesn’t have access to any projects and has necessary permissions, he/she will be asked to create a new content project using multistep wizard.|
Whenever the Publishing Wizard contains at least one item that is "Work in progress", publishing will be disabled. The editor can solve this by clicking the "Mark as ready" link on top of the dialog, which will mark all such items as "Ready for Publishing".
To add another level of restriction and prevent accidental publishing of items that are not ready for publishing, the "Mark as ready" bulk action can be disabled by adding the following parameter to the config file:
publishingWizard.allowContentUpdate = false
By default, all dependencies of content items staged for publishing will also be included to ensure no broken references will appear online. Some of these (for example, all the ascendants of selected items or their inbound dependencies) are required for publishing and cannot be excluded from the publishing batch, while others (like outbound dependencies) are optional.
It’s possible to overrule the default behaviour of including all the dependencies by setting the
publishingWizard.excludeDependencies config property to
publishingWizard.excludeDependencies = true
With this flag turned on, only mandatory dependencies will be included, while optional can be added from the "Show excluded" mode.
|Use this flag with caution. It makes it very simple to publish a content without its outgoing dependencies which may result in broken references, missing images etc.|