| | - Fixed the issue where Opti ID users could not sign in to the Admin Console when another account shared their email.
- Fixed the issue where the Rebuild Product Search Index job returned Arithmetic overflow error converting expression to data type int. when a product's Basic List Price or Basic Sale Price was 2,147,483,648 or higher.
- Fixed the issue where exporting Users with the Roles column returned An item with the same key has already been added. when a user belonged to more than one customer.
- Improved security – Optimizely recommends that all customers on .NET Core versions update to this build.
|
| | - Fixed an issue where bearer-token-only sessions (such as from a mobile app) appeared signed out and showed Sign in for pricing after the browser cookie was cleared.
- Fixed an issue where a malformed or empty PayFlow Pro (TokenEx) gateway response was recorded as a successful transaction even though the payment failed.
- Fixed an issue where client-disconnect exceptions were logged as Error on the Admin Console's Application Logs page; these now log as Debug so they no longer appear during normal operation.
- Fixed an issue where the application displayed a generic error page instead of the custom error page when handling certain exceptions.
- Fixed an issue where the Export Historical Orders and Export Offline Orders jobs timed out on sites with a large number of orders. The underlying query now completes significantly faster.
- Fixed an issue where the dealer location details page displayed content in the wrong language after switching the site locale multiple times.
- Fixed several visual issues left over from the CMS rebranding, including an outdated color on the scheduled-page indicator, misaligned page tree item titles, and old-style buttons in list fields.
- Added a File Picker field for CMS widgets, letting editors click Add File to attach non-image files like PDFs. The Image Picker field now clears its selection when a non-image file is chosen, instead of leaving a stale path.
|
| | - Fixed the issue where menus, filters, radio buttons, and version history still used the old styling in the Spire CMS.
- Fixed the issue where concurrent integration jobs failed intermittently, stayed stuck InProgress, and dropped off their recurring schedule.
- Fixed the issue where Asynchronous JavaScript and XML (AJAX) requests to a redirected URL returned a 500 error.
- Fixed the issue where the DeactivateInactiveUsers job timed out on sites with large order volumes.
- Fixed the issue where the storefront Create User modal ignored Translation Dictionary entries for role names.
|
| | - Fixed the issue where Spire server-side rendering sent duplicate request headers differing only in case, breaking requests behind Cloudflare.
- Fixed the issue where completing PunchOut checkout on .NET Core storefronts returned JSON instead of redirecting to the procurement site.
- Fixed the issue where server-side rendering logged a spurious setSessionCookies called with empty cookies warning on every cookie-less request.
|
| | - Added a redirect allow-list so Spire sites can redirect visitors to approved external domains again, restoring the cross-domain URL redirects that an earlier security change had blocked.
- Fixed the issue where Rebuild Index could fail to complete on Commerce Search v2 and v3, leaving the product, category, or content index incomplete.
- Fixed the issue where a search index rebuild failed during content indexing on .NET Framework 4.8 sites.
- Fixed the issue where category navigation links and menu items intermittently displayed Cache_Item_Empty instead of the category name.
- Fixed the issue where a real-time Order Submit job stayed In Progress indefinitely when the integration connector threw an exception. The job now ends with a Failure status.
- Fixed the issue where Spire logs were flooded with Failed to load font css errors for Google Fonts requests that actually succeeded.
- Fixed the issue where buttons in the Search micro-frontend (MFE) did not match the updated Optimizely branding.
- Fixed the issue where custom front-end packages did not work in local Spire development after the move to pnpm
- Fixed the issue where Commerce Search v3 searches were slow to return on sites with a large number of attribute values.
|
| | - Fixed the issue where product detail pages returned Page Not Found instead of redirecting to the Sign In page when Sign In Required was enabled.
- Fixed the issue where a Spire production build failed when a dependency package was missing its license file.
- Fixed the issue where uploading a larger image (about 30 MB or more) to the Media Library failed on .NET Core storefronts.
- Fixed the issue where asynchronous widgets did not receive their default field values on cloud-hosted sites.
- Refreshed the Spire CMS interface with updated Optimizely branding, giving content editors a look and feel consistent with the rest of the platform.
|
| | - Fixed the issue where the administration console failed to load after upgrading to a .NET Core (Linux) instance
|
| | - 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.
|
| | - 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.
|
| | - 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.
|
| | - 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.
- 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 PlatformIntegrate Optimizely Data Platform
|
| | - 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.
|