Try our conversational search powered by Generative AI!

AI OnAI Off
Products
Packages [expand] [collapse]
Services
Released in version
All versions
4.1.15
4.1.14
4.1.13
4.1.12
4.1.11
4.1.10
4.1.9
4.1.8
4.1.7
4.1.6
4.1.5
4.1.4
4.1.3
4.1.2
4.1.1
4.1.0
4.0.20
4.0.19
4.0.18
4.0.17
4.0.16
4.0.14
4.0.13
4.0.12
4.0.11
4.0.10
4.0.9
4.0.8
4.0.7
4.0.6
4.0.5
4.0.4
4.0.3
4.0.2
3.2.42
3.2.41
3.2.40
3.2.39
3.2.38
3.2.37
3.2.36
3.2.35
3.2.34
3.2.33
3.2.32
3.2.31
3.2.30
3.2.29
3.2.28
3.2.27
3.2.26
3.2.25
3.2.24
3.2.23
3.2.22
3.2.21
3.2.20
3.2.19
3.2.18
3.2.17
3.2.16
3.2.15
3.2.14
3.2.13
3.2.12
3.2.11
3.2.10
3.2.9
3.2.8
3.2.7
3.2.6
3.2.5
3.2.4
3.2.3
3.2.2
3.2.1
3.2.0
3.1.7
3.1.6
3.1.5
3.1.4
3.1.3
3.1.2
3.1.1
3.1.0
3.0.8
3.0.7
3.0.6
3.0.5
3.0.4
3.0.2
3.0.1
3.0.0
2.1.8
2.1.7
2.1.6
2.1.5
2.1.3
2.1.2
2.1.1
2.1.0
2.0.6
2.0.5
2.0.4
2.0.3
2.0.2
2.0.1
2.0.0
1.2.3
1.2.2
1.2.1
1.2.0
1.1.1
1.1.0
1.0.13
1.0.12
1.0.11
1.0.10
1.0.9
1.0.8
1.0.7
1.0.6
1.0.5
1.0.4
1.0.3
1.0.2
1.0.1
1.0.0

Release notes for Optimizely CMS and Customized Commerce updates

This topic lists Optimizely updates, delivered as NuGet packages and services. You decide which updates apply to your project.

Select a product, package, or service in the left menu, and then select one of the following filters from Item type and click Filter.

  • Bug – Display bug fixes.
  • Critical bug – Display only critical bug fixes.
  • Feature –  Display only new features (all features).
  • UI Feature – Display only end-user (user interface) features.

Note: NuGet packages listed here may not be immediately available in the Optimizely NuGet feed.

Latest changes

Item type
Filter on date
Items/Page
Clear filters
Area ID Type Description Released
COM-11549
  [Perform] Introduce new setting for forcing variants to be exported as individual items

Several customers have reported that they want to be able to ignore the products in their catalog and export all variants as separate items instead.

To do this, use the abstractions and structure map interceptor pattern. Partners need to write their own implementation of an interface method whose default implementation is ~500 lines of code with private sub-methods. The source code is provided to the partners for this purpose.

EPiServer.Personalization.Commerce 3.2.17; (Or a related package);
Jul 02, 2020
COM-9021
  Personalization: Add better logging in the export feed process.

There should be info-level logging for successful exports and warning/error-level logging for failed exports.

The scheduled job log should mention how many blobs are in the DB. Something like:
"Created X catalog feeds. There are now Y feeds awaiting export.

If there are more feeds awaiting export than were created by the latest job execution it indicates that earlier exports have not been successful.

EPiServer.Personalization.Commerce 3.0.7; (Or a related package);
Mar 19, 2019
COM-9177
  [Personalization] Serialization of CommerceTrackingData gives unexpected results when using scoped configuration

https://github.com/JamesNK/Newtonsoft.Json/issues/830

We use a custom contract resolver inheriting CamelCasePropertyNamesContractResolver to serialize tracking data to JSON. Even though we use different instances of our contract resolver the CamelCasePropertyNamesContractResolver uses an internal static cache of resolved JsonContracts and shares them between resolver instances.

When a contract for a tracking type is resolved the Site and ClientToken values for the current scope are used in the JSON data and, because of the cache, in all future tracking data of that type. If the site consists of more than one web app the web apps may have cached values from different scopes leading to a, from the outside, seemingly random behavior in regards to what values are included in the JSON.

The Newtonsoft team have chosen not to “fix” it (it’s not really a bug, it’s inconsistent behavior) in later versions because that would be a major breaking change. Therefore, upgrading the Newtonsoft.Json version is not a viable workaround.

EPiServer.Personalization.Commerce 3.0.6; (Or a related package);
Mar 19, 2019
COM-8156
  Catalog feed does not include products in secondary catalog

Steps to reproduce
Precondition: There is a multi-site commerce solution where products are kept in a master catalog (primarey category relation for each product links to the master catalog) and then linked to categories site-specific catalogs.

1. Configure personalization for each of the sites, including configuration of the catalog to export for each site.
2. Run the catalog feed export.

Expected: The products linked to each site specific catalog are included in the export.
Actual: The products are not included in the catalog they are linked to.

EPiServer.Personalization.Commerce 2.1.2; (Or a related package);
Nov 01, 2018
COM-8161
  Catalog feed category outlines can be incorrect in multi-catalog scenario

Steps to reproduce
Precondition: There is a multi-site commerce solution where products are kept in a master catalog (primary category relation for each product links to the master catalog) and then linked to categories site-specific catalogs.

1. Configure personalization for each of the sites, including configuration of the catalog to export for each site.
2. Run the catalog feed export.

Expected: The category outline for each product refers only to categories in the exported catalog. If the product is linked to multiple categories in the same catalog, all these outlines are included.
Actual: All outlines in all catalogs are included.

EPiServer.Personalization.Commerce 2.1.2; (Or a related package);
Nov 01, 2018
COM-7429
  Catalog feed categories should not include catalog name

Since only one catalog can be exported in each catalog feed, and with the new multi-site support there is no indication there will ever be multiple catalogs in one feed, the catalog name in the category hierarchy in the feed only adds noise.

Remove the catalog level from the hierarchy.

NOTE: This must be matched by adjusting the category tracking in the same way.

EPiServer.Personalization.Commerce 2.0.0; (Or a related package);
Jul 22, 2018
COM-5626
  [Recommendations] Product description is not generated in Catalog Feed

Steps to reproduce

  1. Create a catalog in the English and Svenska (Swedish) languages.
  2. Create a product with an active variant.
  3. Update the product description in both languages.
  4. Export the catalog feed.

Expected:
The product description in Svenska can be exported to catalog feed via <p:description location="sv"/> property.

Actual:
Product description in Svenska cannot be exported.

EPiServer.Personalization.Commerce 1.0.0; (Or a related package);
Oct 31, 2017