This section features community-contributed technical resources, including Viet Anh Nguyen's detailed guide for upgrading Optimizely Commerce to version 15 preview on .NET 10.0. Readers should note that these external tutorials provide practical insights for testing new releases but are independent contributions and not official Optimizely announcements.
Community member Viet Anh Nguyen shared a step-by-step guide for upgrading Optimizely Commerce from version 14 to Commerce 15 preview and CMS 12 to version 13. The process involves upgrading to .NET 10.0 and updating project configurations to use explicit package references instead of metapackages. Developers can use this resource to prepare their environments for testing the new preview release.
This week's NewPackages section features the official release of version 13.0.0 for core Optimizely CMS framework packages, including updates for Azure and blob storage. It also highlights community-driven extensions that enhance forms, headless capabilities, and third-party DAM integrations.
Optimizely has officially released version 13.0.0 of the EPiServer.ApplicationModules package via NuGet, which includes framework implementations for Episerver CMS. Developers are advised to review the changelog to assess how these framework updates affect their existing modules. This update is now available for download.
Optimizely has officially released version 13.0.0 of the EPiServer.Blobs package via the Optimizely NuGet feed. This update delivers the latest iteration of blob handling support for the Optimizely Content Management System. Developers can now install this official release to keep their environments up to date.
Optimizely has officially published version 13.0.0 of the EPiServer.CloudPlatform.Cms package through their official NuGet feed. This update makes the latest version of the Content Management System available to developers for integration. Teams should verify compatibility when installing this major version release.
Community member Mark Stott announced the release of Stott Robots Handler v7 for Optimizely CMS 13, adapting to the shift from Site-based to Application-based architecture. While CMS 12 support continues via version 6, developers migrating to CMS 13 must reconfigure robots.txt and llms.txt settings due to identifier changes. The extension is now available on NuGet with updated APIs for headless solutions and Opal integration.
Optimizely has officially released version 13.0.0 of the EPiServer.Azure package, available now via NuGet. This update serves as an umbrella package enabling framework providers to run Optimizely CMS on Azure.
Optimizely has released version 13.0.0 of the EPiServer.Blobs.Azure NuGet package. This update provides the blob storage provider necessary to run Optimizely CMS in an Azure environment.
Community developer szolkowski released OptiPowerTools.Hangfire, a drop-in NuGet package designed to simplify the integration of Hangfire into Optimizely CMS 12. This library replaces the manual boilerplate work previously required for authorization filters, controllers, views, and startup configuration.
Community member Scott Reed released an open-source NuGet package that extends Optimizely CMS 12 Forms with dynamic email routing and conditional submission logic. This custom actor allows developers to define recipient mappings and apply AND/OR conditions via a CMS UI editor, overcoming the static limitations of the built-in email actor without requiring code changes. The package is available now on NuGet and GitHub for anyone looking to manage complex form workflows.
Optimizely has officially released EPiServer.Cache v13.0.0 via the NuGet feed for the Optimizely Content Management System. Developers are encouraged to update their caching dependencies and review the release notes for any compatibility changes included in this version.
Frontify has released version 3.3.0 of their third-party Optimizely NuGet plugin, facilitating integration between Frontify DAM and Optimizely CMS and Commerce. Optimizely developers should review this community release for new capabilities, noting it is a third-party addon rather than an official update.
This section highlights community-sourced technical solutions for Optimizely CMS 12, covering fixes for URL casing, SSO attribution, and search indexing. External contributions also discuss experimentation holdout strategies and report on a known regression in CMS tab scrolling.
Community developer Stuart Greig outlined how to resolve URL segment issues in Optimizely CMS 12, such as incorrect casing and punctuation during LanguageManager auto-translation. The solution requires implementing a custom IUrlSegmentGenerator and event-based tracking to enforce lowercase URLs.
Community member Stuart Greig outlined how to automate Optimizely CMS block translations using the `TranslateOrCopyContentAreaChildrenBlockForTypes` configuration. This third-party guide offers developers a way to bypass manual block-by-block workflows and streamline content management processes. While not an official product announcement, it provides a practical solution for optimizing translation tasks.
Community member Sanjay Katiyar shared a solution for Optimizely CMS where enabling Okta SSO resulted in technical IDs displaying in the "Published By" field instead of user names. The article outlines a custom C# `PublishedByTransform` that resolves these IDs to readable emails or names, enabling developers to restore clear author attribution while maintaining SSO security.
Community member Sarahs Blog shared insights on utilizing Holdout groups in Optimizely Feature Experimentation to validate the net lift of an entire program rather than individual tests. This approach reserves a percentage of traffic as a global control group, allowing developers to configure a 1-5% holdout via the Flags > Holdouts tab for better ROI measurement. It is particularly useful for mature programs running concurrent experiments where individual test metrics no longer provide a clear baseline.
Community member gulla.net shared a guide on Optimizely World Blogs explaining how to temporarily disable automatic event-based indexing in Optimizely Search & Navigation. This tutorial outlines the indexing behavior and provides steps for developers needing manual control over the process. Please note this is a community contribution rather than an official Optimizely product announcement.
Community member TreSmith reported that scrolling through tabs in the CMS is broken on EPiServer.CMS Version 12.34.2. Developers using this version should be aware of this regression while awaiting a fix.