CMS > CMS for administrators > System settings

Episerver CMS iconSystem settings

This topic is intended for administrators and developers with administration access rights in Episerver.

System settings let you define certain settings for the Episerver CMS installation, for instance, to activate globalization, change the error handling, and configure version management of content.

General tab

Setting Description
Error handling in Episerver CMS Select how you want errors to be handled; active for all visitors, remote visitors, or disabled.
Handler for subscription updates The subscription function in Episerver lets visitors receive information about new and updated pages. Depending on whether multi-language is supported, you can select how the subscription dispatch is managed. This list also can include your own solutions for the subscription function.
Encrypt the connectionStrings.config file Select to encrypt the connectionStrings.config file, which contains sensitive information sent to and from the database.
Enable globalization Select to activate management of content in multiple languages (globalization).
Detect language via browser’s language preference Select to activate languages to be shown based upon the visitor’s browser settings.
Disable deletion of content versions Select to disable the ability of editors to delete versions of pages, blocks and files. Selecting this also disables the automatic deletion of versions caused by the Maximum number of versions field on the Editing tab.

Editing tab

Setting Description
Path to CSS file for the rich-text editor Controls the styling options (such as heading levels etc) available to the editor in the rich-text editor. This can be the same or similar CSS file as the site uses for styling content so that the editors get the same appearance as the site when editing content.
Maximum number of versions Specify the number of previously-published versions of content items (for example, pages or blocks) that are stored. The currently-published version and draft versions are not counted.
For example, if you enter 3, Episerver CMS stores three previously-published versions. If that is the case for a content item and you publish a new version, the oldest version is removed.
Default value is 20 versions.
This field is ignored if the Unlimited versions or Disable deletion of content versions box is selected.
Unlimited versions Stores an unlimited number of versions of content items (such as pages or blocks). This option may result in a large version list, which can be difficult to use unless you manually delete unwanted versions.
If you check this, the value in the Maximum number of versions field is ignored.
Auto publish media on upload Select to automatically publish and index media when uploaded to the website. Note: If a user uploads media but does not have publishing rights in the folder to which the media is uploaded, then the uploaded documents are not published (images, for instance, are not displayed when used in content). Ensure that editors who upload media also have the proper access rights set in the media folder structure.

Also note that if this check box is selected and a user (with the proper access rights) uploads media, it is published and indexed immediately, so can be found by search engines, even if no published page contains links to the media.

If The projects feature is enabled in your system, this setting is ignored. Uploaded media that is associated with a project is not published until it is manually published or published via scheduling, even if this setting is turned on.

back to top Episerver image

Help topics   Need help?   FAQs   Glossary   Site map   Videos

Episerver User Guide 17-2 | Released: 2017-03-13 | © Episerver 2017 | Send feedback to us