2025 Optimizely CMS 12 (PaaS) release notes

Follow this article to receive email notifications when new packages are available for Optimizely Content Management System (PaaS) products. Product packages are found on the Optimizely NuGet server and include the following products:

• Optimizely Content Management System (CMS 12)
• CMS Cloud Platform
• CMS+CMP integration
• Content Delivery API
• Optimizely Forms
• Optimizely Language Manager
• Marketing Automation
• TinyMCE
• Optimizely Digital Experience Platform (DXP)

You can find prior versions of user guides (2021 and older) and when functionality was released or deprecated at the following locations:

• Versioned user guides and release notes
• Released functionality
• Obsolete functionality

Most recent releases

CMS 12

EPiServer.CMS.Core

12.22.8—June 24, 2025

• Bug fix
  • CMS-42756 – Fixed an issue where IUrlResolver.GetUrl sometimes generated a relative URL for IContentMedia even when ForceAbsolute is set to true.

12.22.7—May 13, 2025

• Bug fixes
  • CMS-40312 – Fixed concurrency issues in HttpRequestCache.
  • CMS-40940 – Fixed the issue by improving the performance of the ClientResourceService, specifically optimizing the resource sorting functionality.

12.22.6—April 15, 2025

• Bug fixes
  • CMS-37561 – Fixed the issue with the index to exclude NULL values, as the most common value for tblContent.ArchiveContentGUID is NULL, making the existing index ineffective.
  • CMS-39486 – Fixed the issue with the setValue method of LazyPropertyValueLoader not providing enough information for troubleshooting.
  • CMS-40666 – Fixed a redirect issue that caused the error: InvalidOperationException: Invalid non-ASCII or control character in the header: 0xXXXX'.

12.22.5—March 4, 2025

• Bug fixes
  • CMS-37890 – Fixed an issue where audiences and visitor groups were not syncing across all servers.
  • CMS-39893 – Fixed an issue that let a user publish a page without filling in a required property in an Ilist. 
  • CMS-37156 – Fixed an issue where client resources fail to load in the CMS UI when using a redirect hostname.
  • CMS-39589 – Fixed an issue with routing not working with a language segment when it should generate URLs without a language segment and work both with and without a language segment.
  • CMS-39934 – Registering a custom IConstructorParameterResolver to handle ContentData constructors with one or more parameters will always result in a MissingMethodException when instances of the content type are constructed. 

12.22.4—February 11, 2025

• Bug fixes
  • CMS-39541 – Fixed an issue where changing a property from ContentArea to ContentAreaItem with multiple inline blocks could cause an infinite loading loop and halt site responsiveness.
  • CMS-37956 – Fixed an issue where the optimizations for Html.ContentLink() and Url.ContentUrl() methods made it harder to add general URL customizations. The optimizations have been removed.
  • CMS-39593 – Fixed an issue where images in the media asset panel were not sorted alphabetically.

12.22.3—January 21, 2025

• Bug fix
  • CMS-38813 – Fixed an issue where you could not create an audience when using .NET 9 due to an error occurring for the BinaryFormatter.

EPiServer.CMS.UI

12.33.1—June 4, 2025

• Bug fixes
  • CMS-39673 – Fixed the issue where unhandled exceptions occurred when accessing a Content instance from ContentDataStore could lead to the edit UI remaining in a loading state.
  • CMS-41227 – Fixed the iframe issue where is loads for a long time; it is not possible to use the mouse wheel to access the top bar properties.
  • CMS-42311 – Fixed a bug where it was not possible to export content items from CMS after changing the global serializer options.
  • CMS-42335 – Fixed the issue by adding a way to subscribe to the contentSaved event directly instead of relying on a global window.epi object.

12.33.0—May 20, 2025

• Bug fixes
  • CMS-41169 – Fixed the issue of inconsistent behavior in selecting the personalization pop-up.
  • CMS-41849 – Fixed the issue where the user cannot compare versions of a page.
  • CMS-41862 – Fixed the issue for pagination is not working for Link Validation.

12.32.5—April 15, 2025

• Enhancements
  • Improved export screen in admin mode to work more reliably when exporting very big data chunks.
  • Improved the import data view in the Settings to prevent potential timeout issues when importing large files or when the import HTTP request lasts an extended duration.
  • Improved error messages for file uploads will inform users about the source of the error. 

• Bug fixes
  • CMS-39707 – Fixed an issue where the select image button does not work.
  • CMS-32843 – Fixed an issue where the editor got a bad request from /activity/ controller when selecting multiple project items.
  • CMS-33725 – Fixed an issue where uploading a file larger than UploadOptions.FileSizeLimit in an instance on DXP results in an HTTP status of 405 (Method not allowed) instead of the intended 413 (Content too large).
  • CMS-40071 – Fixed an issue where the SaaS CMS could not drag and drop content blocks into the content area if the display name contained spaces.
  • CMS-40012 – Fixed an issue when the focus was lost after editing an inline-block.
  • CMS-40101 – Fixed an issue where the Catalog entry search from the Assets panel takes a much longer time compared to the left on Navigation panels.

12.32.4—February 11, 2025

• Bug fixes
  • CMS-37958 – Fixed an issue where personalization groups incorrectly let you configure the same audience for multiple variants or fragments, even though only single variants of fragments were allowed.
  • CMS-39324 – Fixed an issue where the quick navigator rendered only for the default authentication scheme (instead of the specified authentication scheme) when you used mixed-mode authentication.
  • CMS-39103 – Fixed an issue that did not restrict file types for upload. Now the Import Data function allows uploads of only files with the .episerverdata extension.
  • CMS-38847 – Fixed an issue that let a user publish a page without filling in a required property in an Ilist. (You should be able to save the content that contains a list of blocks with some required values missing but you should not be able to publish it.)

12.32.3—January 21, 2025

• Bug fixes
  • CMS-37388 – Fixed an issue that did not display a pop-up window when you selected an image in the ImageRef property.
  • CMS-35323 – Fixed an issue that caused a blank screen in CMS edit. This happened in some rare conditions when shared resources could not be parsed on time, or dojo.getObject caused the exception multipleDefine that led to an exception in other places that tried to access epi.resources.action.
  • CMS-35654 – Fixed an issue in the date that displayed incorrectly when you used scheduled publishing.
  • CMS-37919 – Fixed an issue in subcategories that included &nbps; instead of a space when you created an audience with a Site Criteria on Visited category.
  • CMS-38508 – Fixed an issue where errors were logged because not all schemas can handle sign out. If you did not use OptimizelyIdentity or CmsAspNetIdentity, there was no registered implementation of EPiServer.Shell.Security.UISignInManager. In this scenario, when logging out from CMS UI, you should only call SignOutAsync on the default schema.

EPiServer.ImageLibrary.ImageSharp

2.0.5—April 22, 2025

• Bug fix
  • CMS-37774 – Fixed an issue where it was not possible to crop a large image while zooming out to see the whole image.
  • CMS-41356 – Fixed the vulnerability in SixLabors.ImageSharp 3.1.5.

1.0.4—April 22, 2025

• Bug fix
  • CMS-37774 – Fixed an issue where it was not possible to crop a large image while zooming out to see the whole image.
  • CMS-41358 – Fixed the vulnerability in SixLabors.ImageSharp 2.1.9.

CMS Cloud Platform

EPiServer.CloudPlatform.Cms

1.7.2—July 3, 2025

• Bug fixes
  • CMS-40733 – Fixed the issue where CloudPlatform health check should not use ISchemaUpdater.
  • CMS-42528 – Fixed an issue by skipping the processing of database queries to epicms and epicommerce that happened frequently and consumed large amounts of Log Analytics.

1.7.1—March 21, 2025

• Enhancements
  • CloudPlatform now supports using connection string to configure the application insights tracking script.
    The Instrumentation key will be unsupported from 31 March 2025.
  • Updated the following CloudPlatform dependencies to void a known issue with Microsoft packages. See [DataProtection] Hang at application start when trying to get DataProtection key from Azure KeyVault #53989.
    • Azure.Extensions.AspNetCore.DataProtection.Blobs 1.3.3
    • Azure.Extensions.AspNetCore.DataProtection.Keys 1.2.3

CMS + CMP

EPiServer.Cms.WelcomeIntegration

2.1.5—July 16, 2025

• Bug fixes
  • CMS-42759 – Fixed an issue where the DAM metadata maintenance job may run too fast for the CMP API threshold of 10 requests per second.
  • CMS-42582 – Fixed a CMS installation issue with Commerce: a scheduled asset tracking job fails with a 'Unexpected metadata type argument' error if metadata is missing. Non-Commerce installations are unaffected.
  • CMS-42853 –Fixed an issue where DAM image metadata wasn't retrieved during page or block publishing. 

EPiServer.Cms.WelcomeIntegration

2.1.4—April 22, 2025

• Bug fixes
  • CMS-41339 – Fixed an issue where the DAM metadata maintenance job may run too fast for the CMP API threshold of 10 requests per second.
  • CMS-41132 – Fixed an issue when attempting to add some assets from DAM to an IList. An error states, You do not have access rights to publish this content.

2.1.3—April 15, 2025

• Bug fixes
  • CMS-40931 – Fixed the threading issue in DAM integration.
  • CMS-41129 – Fixed the issue of DAM maintenance job for the graph ending early.

2.1.2—April 1, 2025

• Bug Fixes
  • Fixed an issue in the CMP metadata maintenance scheduled job that failed when trying to remove assets.

    The scheduled job, CMP asset metadata maintenance, divided the used assets into chunks while retrieving metadata from the DAM. When one image used in CMS was removed in CMP, that chunk failed to update. If the asset was properly tracked, then CMP would also give the option to cancel the removal with a warning that the image was in use, and where, prior to deleting it.

    This affected only installations using the REST API integration and not the Graph integration. See CMP DAM in CMS for information about Optimizely Graph integration.

  • Fixed an issue that opened CMS assets incorrectly when you replaced DAM assets on ContentReference properties. ContentReference properties that did not specify UIHint opened the CMS content tree even if DAM assets were currently referenced. You can workaround this by removing the reference and choosing a new one instead of replacing it.
  • Fixed an issue where duplicate references to DAM caused a malfunction in the scheduled job for maintaining metadata that has been resolved.

2.1.0—January 21, 2025

• Enhancement
  • Reduced the number of requests performed against the CMP DAM API to increase performance in retrieving metadata for referenced assets.
• Bug fixes
  • CMS-38213 – Fixed an issue that caused a scheduled job failure when neither the CMP API nor Optimizely Graph was integrated and configured. Logs contained errors that indicated CMP integration was not configured: Client Id and Client Secret are required in CmpClientOptions.

    See CMP DAM in CMS.

  • CMS-38272 – Fixed an issue that caused the graph query to fail when CMS was configured to index content into Optimizely Graph and CMP DAM assets were also being retrieved from Optimizely Graph. Workaround: Configure the OptiGraphOptions.TransformActionBehaviour option and set it to Clone to let CMS use two different sources in Optimizely Graph. Note that DAM and CMS have their own SingleKey used to query Graph.

Cmp.Client

1.2.0—January 21, 2025

• Enhancement
  • Added ICmpClient EnsureConfiguration to validate configuration without calling actual endpoints.

Content Delivery API

EPiServer.ContentDeliverApi

3.12.1—March 11, 2025

• Bug fix
  • HAPI-2871 – Fixed an issue where users can still access content even if it does not match the RequiredRole.
  • HAPI-2878 – Resolved an issue where EPiServer.ContentManagementApi version 3.11.0 could not find the service for IContentApiRequiredRoleFilter.
  • HAPI-2831 – Fixed an issue where the ContentDeliveryApiOptions.RequiredRole setting did not take effect when the ContentSearchApiOptions.RequiredRole was configured.
  • HAPI-2880 – Fixed an issue that caused an exception in the ExpandedContentPropertyModel.ExpandProperty method.

3.12.0—January 21, 2025

• Enhancement
  • Added support for the ContentAreaItem property. You can GET, CREATE, UPDATE, and PATCH the ContentAreaItem property through Content Management API.
• Bug fix
  • HAPI-2846 – Fixed an issue in ErrorsStartupFilter that redirected 4nn responses to the corresponding view /Util/Errors/Error4xx. This caused a problem when the partner challenged a 401 response, the filter caught it and redirected it to the Error401 view (which does not even exist) and other weird behavior.

Optimizely Forms

Optimizely.CMS.Forms.*

1.2.0—February 18, 2025

• Bug fix
  • AFORM-4594 – Fixed a compability issue between Optimizely.ContentGraph.Cms 3.14.3 and Optimizely.Cms.Forms.ContentGraph 1.1.0.

1.1.0—January 24, 2025

• Bug fixes
  • AFORM-4550 – Fixed an issue with custom element types that inherit from SelectionElementBlock so they will work with the feed provider.
  • AFORM-4300 – Fixed an issue that had the wrong access right for the submission API, causing an error: 403 Forbidden with detail: Unable to view form submission with key submissionKey, associated with the form key.
  • AFORM-4234 – Fixed an issue on a form where SubmissionKey is not a submission key, which returned an error (500) instead of the expected 400.
  • AFORM-3907 – Fixed an issue that caused an error (500) when the system tried to redirect to an image after form submission.
  • AFORM-4254 – Fixed an issue with Get default language that was missing the submitSuccessMessage.

EPiServer.Forms.*

4.2.7—March 4, 2025

• Bug fix
  • AFORM-4513 – Fixed an issue where the DatePicker in Forms.Sample displayed the incorrect date format.

5.10.4—February 26, 2025

• Bug fix
  • AFORM-4601 – Fixed an issue that occurred when renaming the form element if the email template was empty.

Optimizely Language Manager

EPiServer.Labs.LanguageManager

5.5.0—March 18, 2025

• Enhancement

  • Added support for local blocks in import or export xliff documents.

    When you export to xliff from a content that contains a BlockProperty, Language Manager supports one level of BlockProperty with no limit of inline block levels. For example:

    • Page
      • BlockProperty
        • ContentArea
          • InlineBlock 1
          • InlineBlock 2
            • ContentArea
              • InlineBlock 2-1
              • InlineBlock 2-2

5.4.1—February 27, 2025

• Enhancement
  • Added support for inline blocks to be translated when you import the Xliff content that contains inline blocks.

5.4.0—January 7, 2025

• Enhancements

  • Extended auto-translation capabilities to LinkItem and LinkItemCollection properties.

  • Extended auto-translation capabilities to inline blocks.
• Bug fixes
  • LM-615 – Fixed an issue to translate special characters in URLs. Use UrlSegmentOptions.ValidCharacters for a set of valid characters. Otherwise, only alphabetic characters, hyphens (-), and underscores (_) are accepted.
  • LM-508 – Fixed an issue where you exported a null JSON translation package file if the content contained an inline block.
  • LM-507 – Fixed an issue where you exported a null JSON translation package file if the content contained an inline block inside a content area.
  • LM-503 – Fixed an issue in IList<T> that duplicated or translated an inline block improperly.

TinyMCE

EPiServer.CMS.TinyMce

5.0.2—June 17, 2025

• Bug fix
  • CMS-39848 – Fixed an issue where dragging and dropping pages from the recent gadget into XhtmlString properties using TinyMCE did not work.

5.0.1—May 7, 2025

• Bug fix
  • CMS-41834 – Fixed an incorrect initialization of Optimizely's commercial license key for TinyMCE.

5.0.0—April 1, 2025

• Enhancement
  • Upgraded TinyMCE to version 7. See also Migrating from TinyMCE 6 to TinyMCE 7. See also  blog post by Grzegorz Wiechec: TinyMCE 7 editor upgrade.

4.8.3—March 25, 2025

• Bug fixes

  • CMS-39004 – Fixed an issue where the Global menu displayed above the TinyMCE toolbar.

  • CMS-39467 – Fixed minor bugs by updating TinyMce to the 6.8.5 version.
  • CMS-39055 – Fixed an issue where the Spellchecker service returned an error from AutoValidateAntiforgeryTokenAttribute.

Personalization

July 8, 2025

• Bug fix
  • Fixed an issue where MaxMindGeolocationProvider did not resolve IP address to a geolocation result.

DXP

April 10, 2025

• Enhancement
  • DXP now supports the HTTP/3 protocol, which is the latest version of the HTTP protocol used for transferring data on the web. The HTTP/3 protocol entails:
    • Improved Performance – HTTP/3 is built on the QUIC transport protocol, which is designed to reduce latency and improve the speed of web connections, especially on unreliable networks.
    • Enhanced Security – HTTP/3 includes encryption as a fundamental part of the protocol, enhancing the security of data in transit without the need for additional layers.
    • Better user experience – By enabling HTTP/3, websites can offer faster page loads and smoother interactions, leading to a better overall user experience.