Current short-term support hotfixes

  • Updated

This article contains a list of hotfixes for the current cloud release. Be aware that the most recent hotfix contains all previous hotfixes, so applying the latest hotfix automatically updates your environment to the current cloud release.

Optimizely has set a deadline for hotfix submissions each release to allow the Configured Commerce team time to prepare the upcoming release. See the hotfix submission deadline notice for more details.

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

Current Cloud Release Version: 5.2.2603

Date Build Description
April 2 5.2.2603.411+sts
  • Fixed an Index was outside the bounds of the array exception that occurred during payment gateway response parsing when a cardholder name contained an ampersand character. The response parser incorrectly split field values on the & delimiter, causing fields without an = separator to throw an index error. As a result, orders failed to create despite a successful payment authorization, leading to an incomplete checkout flow.
  • Fixed an error that occurred in the Rebuild Sitemap integration job when the GetDealerUrls pipe executed the ShouldAddDealerDetailsPages method with a null reference. The exception caused the sitemap post processor to fail, preventing successful sitemap generation. See Manually configured integration jobs.
  • Fixed an exception that prevented the application from starting. The error occurred in AsyncPipeline.Register when scanning the ExtensionsAssembly for types without exception handling, causing startup to fail before dependency registration could complete. 
  • Fixed a timezone-related issue where published CMS page versions appeared up to several hours in the future on Configured Commerce instances whose SQL server ran in a timezone with a negative UTC offset (for example, EST, CST, or PST). 
  • Fixed an error that prevented Vendor Managed Inventory (VMI) users from emailing order details from the VMI Order Details page. The VMI order details page was not included in the list of pages allowed for PDF generation, causing the email action to fail. Added the VMI Order Details page to the allowed list so that order confirmation emails can be sent successfully.
  • Added an Application Insights page view event tracking to the Spire storefront. Previously, page view telemetry was not emitted from the Spire site, leaving teams without visibility into storefront page traffic within Azure Application Insights. 
  • Added a binding redirect for Microsoft.IdentityModel.Tokens to resolve an assembly version conflict that caused deployment failures.
  • Fixed a Cannot access a closed file error that caused the S3 image upload integration job to fail. The Transfer method disposed file streams before the yielded async upload tasks completed, resulting in closed streams at the point of read. Restructured stream handling so that non-zip files open and close their own streams per upload, and zip archive entries are eagerly extracted into memory before the upload task executes, ensuring streams remain accessible throughout the upload operation.
  • Fixed an issue where page views on the 404 Page Not Found page were not tracked by Product Recommendations, preventing that page from contributing to recommendation data and behavioral analytics.
  • Fixed a regression in the Admin Console where the website-specific value indicator icon and tooltip no longer displayed on global default settings that had been overridden at the website level. 
  • Fixed an issue in SqlExecuteStoredProcedure where the commandTimeout parameter was accepted but never applied to the underlying SQL command, causing all stored procedure executions to fall back to the default 30-second database timeout.