In this topic
Note: 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, such as to activate globalization, change the error handling, and configure version management of content.
|Path to CSS file for the rich-text editor||Controls the styling options (such as heading levels and so on) 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.
Default value is 20 versions. The scheduled job Trim content versions checks this setting and removes any Previously published versions above this number. Oldest versions are removed first.
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 (for example, images 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, if this check box is selected and an editor (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 and the editor has a project selected when uploading media, this setting is ignored. The uploaded media is associated with the project instead, and must be manually published or published via scheduling.
Sorry about that
Why wasn't this helpful? (check all that apply)
Thanks for your feedback.
Want to tell us more?
Send an email to our authors to leave your feedback.
Thanks for taking the time to give us some feedback.