Area: Optimizely CMS
Applies to versions: 10.2 and higher
Other versions:

Configuring the CMS user interface

Recommended reading 

This topic describes available configuration options for the Optimizely user interface, with the purposes of enhancing performance and improving the user experience.

Iframe response timeout [New in 10.2]

If you get this message in edit view it means that you have hit the response timeout for our editing iframe:

Preview Unavailable

Failed to load the preview within the given time constraints.

The default time to load a preview is 15 seconds. You can increase it by adding an appSetting in your web.config with this key: episerver:ui:PreviewTimeout. The value should be in milliseconds.

To set the preview timeout to 20 seconds, add this configuration:

    <!-- Set iframe timeout to 20 seconds -->
    <add key="episerver:ui:PreviewTimeout" value="20000" />

This timeout was added in the EPiServer.CMS.UI 10.2.0 package to solve a bug and make the iframe load more reliable.

ApprovalStepRoleUserLimit configuration [New in 10.10]

If you are using large user groups in content approvals, there is a risk of performance issues (and unhappy users) due to the high number of notifications in the system. Therefore, there is an appSetting in the web.config, called episerver:ui:ApprovalStepRoleUserLimit, which triggers a validation warning when an administrator adds a group with members exceeding this setting. It will also limit the amount of notifications sent to the users in the group. The default setting is 100 users per group, but it can be configured in this key:

    <add key="episerver:ui:ApprovalStepRoleUserLimit" value="100" />
Do you find this information helpful? Please log in to provide feedback.

Last updated: Jun 12, 2017

Recommended reading