Disclaimer: This website requires Please enable JavaScript in your browser settings for the best experience.

HomeDev GuideRecipesAPI Reference
Dev GuideAPI ReferenceUser GuideGitHubNuGetDev CommunityOptimizely AcademySubmit a ticketLog In
Dev Guide

Edit

Explore Optimizely CMS 13 Pre-release Edit view features: content editing, property highlighting, and direct editing of experience and section properties.

Get started with Edit

📘

Note

On-page edit (OPE) is disabled in the pre-release of CMS 13 in favor of Visual Builder.

  • The new Visual Builder editing view is enabled by default, but to get the full feature set, you must have content types that are experiences and create content items from them. You can still edit non-experiences in Visual Builder, but those will not have a dynamic layout.
  • Translate content is configured by default on DXP, and deployed projects will support translation of content automatically.
  • For external content (Compose experiences using Optimizely Graph sources) is not enabled for this first preview.

View page as audience

You can view a page as a specific audience to understand how content displays for different visitor segments. This reintroduces functionality similar to audiences (formerly called visitor groups) in CMS 12.

  • Any configured audience is available for selection.
  • The page is displayed in a preview that reflects the content tailored for the selected audience.
  • This feature is available for in-process sites running on PaaS, provided audiences is installed.
  • View as audience is accessible through a context menu located next to the Publish button.

Scheduled publish date in Version gadget

You can see when content scheduled for publication will go live with the scheduled publish date in the Version gadget, visible within the status only for the current version; previous versions do not show this information. The status text was updated from Scheduled for publish on to Scheduled to publish on.

Increased default upload size and enhanced error handling

Increased the default file upload size, aligning with Microsoft's recommended settings for optimal performance on Kestrel and Azure platforms. This update also includes improved error messaging for file upload failures. These changes apply to all file upload methods, including uploads to the assets folder, drag-and-drop functionality, and uploads within TinyMCE.

  • The default file upload size now matches Microsoft's default settings.
  • Uploads will fail if the size of a single file or the total size of multiple files exceeds the new limit.
  • If an upload fails due to exceeding the size limit, an error message Upload failed because file exceeded the size limit of X is displayed, accompanied by an HTTP status code 413 Content Too Large.
  • The upload timeout was increased to accommodate users with slower connections.
  • In the event of a timeout, a fallback message Upload failed due to a timeout issue is displayed, with an HTTP status code 500 Internal Server Error or 408 Timeout.

Blocks were renamed Shared Blocks

Blocks were renamed to Shared Blocks in the user interface.

Restricted file upload by extension

CMS prevents the upload of unsafe file extensions, enhancing security within CMS.

  • A whitelist of allowed file extensions is enforced for uploads to the Asset panel, single property editors, drag-and-drop areas (including TinyMCE), and the Content Manager API.
  • If an unsupported file extension is uploaded, a clear error message is displayed, stating that the file extension is not allowed.
  • Developers can configure the whitelist through Settings > Applications or an options class.

Content GUID display in Edit view

Added the display of the content's GUID (Globally Unique Identifier) in Edit view. The GUID is visible alongside the content ID, providing a consistent identifier for content items.