2025 CMS 12 release notes

  • Updated

Follow this article to receive email notifications when new Optimizely Content Management System (CMS 12) packages are available for 2025. Product packages are found on the Optimizely NuGet server

Are you looking for release notes before January 2024? See the Optimizely Release Notes on the Optimizely World site.

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

February 11, 2025

EPiServer.CMS.Core 12.22.4

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.

EPiServer.CMS.UI 12.32.4

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.)

EPiServer.CMS.UI 11.37.4

Bug fixes

  • CMS-38861 – Fixed a type issue in the tooltip dialog for installations using sv-SE culture.

January 21, 2025

EPiServer.CMS.UI 12.32.3

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.CMS.Core 12.22.3

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.

CMP.Client 1.2.0

Enhancement

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

EPiServer.Cms.WelcomeIntegration 2.1.0

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.

January 7, 2025

EPiServer.Azure 11.2.1

Bug fixes

  • CMS-38103 – Fixed an issue by restoring two methods, AzureBlobProvider.Initialize() and AzureBlobProvider.Validate(string connectionString, string containerName) to avoid breaking changes.
  •