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.2512
Date
Build
Description
April 2
5.2.2512.498+lts
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.
March 19
5.2.2512.476+lts
Updated the Export Product Feed job to generate fully qualified image URLs. The job now includes the CDN domain in image paths. Previously, only relative paths were exported, so product images did not display in Product Recommendations.
Added the Polly library to the allowed third-party libraries list. Developers can use Polly to implement retry, circuit breaker, and timeout policies in custom integrations.
Hardened the retry logic for IronPDF document generation. The updated logic handles transient gRPC connection failures more reliably. This prevents PDF email delivery from failing after the first attempt for a given user.
Updated the TinyMCE rich text editor license key to a version-locked key for TinyMCE 8.1.2. This replaces the previous time-limited key and prevents license warnings in the Admin Console.
Improved Spreedly payment token handling for the Cybersource gateway. The system now stores only the subscriptionId from the Cybersource response. This resolves checkout errors that occurred when saving a card through Spreedly.
Fixed the unhandled error that occurred when searching after signing in on sites using Commerce Search v3. A null facet value in the filter string caused the error. Commerce Search now falls back to Elasticsearch when attribute sync is incomplete. A descriptive log message replaces the unhandled exception.
Fixed the issue where the order source was set to Web instead of Punchout for orders created through a Punchout session. The system now assigns the correct order source for Punchout OrderRequests.
Fixed the issue where the recently purchased list did not update after a checkout. The list intermittently displayed stale data or appeared empty. Reloading the page did not resolve the problem. The list now refreshes correctly after a purchase.
Fixed the issue where customer segment groups did not apply to CMS content variants. Header variants targeted at a specific customer segment were not visible to those customers. Content variant rules based on customer segments now evaluate correctly.
Fixed the unhandled error that occurred when the Product.UrlSegment property was marked as non-translatable. The error message was "There was no propertyDefinition found for UrlSegment on Product type." Adding a product to the cart no longer throws an exception for this configuration.
March 3
5.2.2512.456+lts
Added the Application Insights Disable Database Tracking toggle within Admin Console > Developer. When enabled, the setting filters out SQL dependency telemetry before it leaves the application, reducing Azure data storage costs associated with high-volume database interaction logging.
Fixed the unhandled error that occurred when performing product searches with Commerce Search v3 enabled.
Fixed the unhandled error that occurred with Commerce Search v3 when sorting search results by price if the results contained unit of measure products.
Fixed the issue where Commerce Search v3 displayed duplicate products in search results after performing searches or sorting operations.
Fixed the issue where Product Recommendations incorrectly tracked child variants as their parent product in Cart and Checkout pages.
February 19
5.2.2512.437+lts
Improved the performance of v2 Products API calls with relevancy enabled for Commerce Search v3.
When using Commerce Search v3, you must review and update any existing custom product search extensions as needed. The product search pipeline has been updated, including changes to the order of execution and the pipes overridden by Google Retail Search. Review the Commerce Search v3 product search pipeline documentation to ensure your customizations align with the updated pipeline behavior.
Fixed an issue where the OrderPackagerStandard failed to save auto-created packages in .NET 4.8 environments and resolved a bug in ProcessShipSeparatelyOrderLines that incorrectly calculated package weights as zero when QtyPerShippingPackage was zero. These improvements apply to both Cart v1 and Cart v2.
Fixed an issue where you could select archived products when creating promotion codes.
February 5
5.2.2512.428+lts
Fixed vunerabilities with the react-router dependency.
Added a TinyMCE Editor control to the Application Dictionary for custom properties.
Improved HTML content on the server-side of Spire to prevent malformed HTML tags that cause unresponsive issues on the Product Detail page.
Updated the Block Anonymous Traffic feature to use information from Cloudflare to identify the user’s country.
Please sign in to leave a comment.