Current long-term support hotfixes

  • Updated
Documentation is currently undergoing platform maintenance. Hotfix details for releases during this period will be published soon after maintenance is complete.

This article contains a list of hotfixes for the current long-term support branch. The most recent hotfix contains all previous hotfixes, so applying the latest hotfix automatically updates your environment to the current branch. 

Optimizely can hotfix the current LTS branch until code lock, which is one week before release.

Follow this article to receive email notifications when Optimizely Configured Commerce releases hotfixes for long-term support versions.

Current Long-Term Support branch version: 5.2.2604

Date Build Description
July 20, 2026 5.2.2604.794+lts
  • Fixed website-level cookies being reset on page navigation in Classic .NET Core storefronts after migrating to Linux.
  • Updated button font weight from Regular to Medium in the Admin Console as part of the ongoing rebranding, improving button label readability.
  • Fixed a NullReferenceException in RetrievePageService.GetUrlByTypeAndLanguageId that caused the first SSO login attempt to fail.
  • Fixed a validation error on the Admin Console website user profile page.
  • Added the Application Insights Enable Sql Command Text setting to the Admin Console. When enabled, Configured Commerce sends SQL command text to Azure Application Insights for query-level diagnostics. 
  • Fixed api/v1/catalogpages ignoring the Sign In Required to Browse setting, which allowed unauthenticated users to access product data through the API.
  • Fixed saved Spreedly payment profiles being submitted with required billing address fields left empty. 
  • Fixed the Cancel button on the Change Customer page not reverting Fulfillment Method changes made without clicking Apply.
  • Fixed integration jobs becoming stuck on .NET Core sites after a job timed out and was cancelled. An InvalidUnitOfWorkResolutionException prevented the recurring job from running again without a manual reset.
  • Added a data migration to preserve the V1 cart handler for existing sites during upgrade, preventing a silent switch to the V2 cart handler. Sites installed after this release default to V2.
  • Improved Spire storefront caching to prevent stale content after deployments. JavaScript bundles now use content-hash filenames for reliable cache invalidation. .NET Core storefronts now return correct Cache-Control headers for HTML pages when etag caching is disabled.
July 9, 2026 5.2.2604.756+lts
  • Fixed the issue where the Print button on the VMI location details page did not send an email on .NET 8 sites.
  • Fixed the issue where completing an order on .NET Core sites did not send an order event to Optimizely Data Platform (ODP).
  • Fixed the issue where partners could not run Admin.Api locally in development on .NET Core.
  • Fixed the issue where creating a restriction group with a customer rule skipped the Restriction step and then showed an unhandled error on the Summary step.
  • Added the Mobile Refresh Token Lifetime Minutes and Mobile Absolute Refresh Token Lifetime Minutes system settings on .NET Core, which let implementers control how long a mobile app stays signed in before a user must sign in again.
  • Fixed the issue where adding a new card in Saved Payments returned a 500 error for some payment gateways, such as Orbital and Payflow Pro.
  • Fixed the issue where a classic site on .NET Core threw an error when rendering a product list or product detail page that used a custom search engine optimization (SEO) view.
  • Fixed the issue where order history records were editable in the Admin Console on .NET Core sites, which let users save changes to completed orders. Order history fields are now read-only.
  • Fixed the issue where the nightly maintenance job could fail with an out-of-memory error on .NET Core sites that had a large backlog of records to delete. Batch deletes now run as set-based SQL deletes that honor the configured batch size and command timeout.
June 29, 2026 5.2.2604.725+lts
  • Updated the Admin Console color scheme and logo to reflect Optimizely's current branding.
  • Fixed an issue where deploying a version upgrade could fail due to assembly load failures during startup. Assembly binding redirects now run earlier so upgrades deploy reliably.
  • Fixed an issue where an error was intermittently logged in the Application Logs after running an index with Commerce Search v3.
  • Fixed an issue on .NET Core storefronts where a user prompted to change their password received an internal server error (HTTP 500) after submitting a new password instead of being logged in.
  • Fixed an issue in Commerce Search v3 where changing a product's type to Variant and rebuilding the index could cause variants to appear in search results with empty fields, breaking the Product Result widget on the search listing page. Affected variants are no longer shown in search results.
  • Fixed an issue where multi-threaded integration jobs using the FieldMap post-processor could fail with a database concurrency error on .NET Core. Each data table operation now runs in an isolated context.
  • Improved security across the platform.
June 18, 2026 5.2.2604.688+lts
  • Fixed an issue where launching the CMS from the Admin Console on non-Opti ID sites opened with the templated URL instead of the site vanity URL.
  • Improved security.
  • Fixed an issue where TinyMCE converted absolute URLs into relative URLs when saving content in the CMS admin.
  • Hid archived websites from the View Website admin menu and the CMS Dashboard. Content editors now see only active websites when going between sites.
  • Added an import prompt for standard Optimizely Data Platform (ODP) job definitions when the Enable ODP Tracking setting is turned on. The Admin Console now offers to install the ODP data-export job definitions, so administrators no longer need to create them manually. See Integrate Optimizely Data Platform.
June 11, 2026 5.2.2604.666+lts
  • Fixed an issue where CKFinder experienced performance degradation when loading root-level S3 folders containing a large number of files but no subfolders, caused by the system loading all objects before confirming no subfolders existed.
  • Fixed an issue where canceled jobs were still being processed after you migrated to NETCore.
  • Fixed an error when you used absolute URLs for redirects.
  • Made security improvements.