Packages [expand] [collapse]
Released in version
12.1.2
12.1.1
12.1.0
12.0.1
11.2.1
11.2.0
11.1.2
11.1.1
11.1.0
11.0.2
11.0.1
11.0.0
10.2.0
10.1.2
10.1.1
10.1.0
10.0.1
10.0.0
9.8.0
9.7.2
9.7.1
9.7.0
9.6.2
9.6.1
9.6.0
9.5.3
9.5.2
9.5.1
9.5.0
9.4.3
9.4.2
9.4.1
9.4.0
9.3.1
9.3.0
9.1.2
9.1.1
9.1.0.2335
9.0.0.2183

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
Area ID Type Description Released
COM-16792
  Update package dependency range to Episerver.Find 15

Updated package dependency range to Episerver.Find 15.

EPiServer.Find.Commerce 12.1.2;
Mar 07, 2023
COM-16794
  EPiServer.Commerce.FindSearchProvider 12.1.1 not supported by Find 15

Fixed EPiServer.Commerce.FindSearchProvider to support Find 15.

EPiServer.Find.Commerce 12.1.2;
Mar 07, 2023
COM-15723
  [Find.Commerce] CatalogContentEventListener should use ConcurrentDictionary

CatalogContentEventListener.IndexContentIfNeeded can get into an infinite loop when executing multiple threads. You should use ConcurrentDictionary instead of using standard dictionaries. 

EPiServer.Find.Commerce 12.1.1;
Jul 26, 2022
COM-15726
  [Find.Commerce] The result is not listed in Catalog tree if user search more than 1 word

Fixed an issue where a second search would not produce a result. If you cleared the content index and then started Search & Navigation Content Indexing Job manually, the first search in the Search box of the catalog tree performs correctly, but the next one did not.

EPiServer.Find.Commerce 12.1.1;
Jul 26, 2022
COM-14878
  Update Newtonsoft.Json dependency version to 13

Updated the Newtonsoft.Json dependency version from 12 to 13.

(Episerver.Find already supported Newtonsoft.Json 13)

EPiServer.Find.Commerce 11.2.1;
Mar 22, 2022
COM-9720
  FindCommerce should allow temporarily disabled event indexing

Fixed issue with ability to set FindCommerce event indexing to allow for temporarily disabling of event indexing. 

CatalogContentClientConventions.AllowIndexingCatalogContent should be possible to set dynamically. Furthermore, IsListeningToPriceEvents, IsListeningToInventoryEvents and IsListeningToLowLevelApiEvents should be introduced, and also possible to set dynamically to allow fine grain control of the indexing.

 

EPiServer.Find.Commerce 11.2.0;
Nov 19, 2020
COM-11513
  CatalogEventIndexer.IndexContentInAllLanguages is slow

Fix to improve performance of catalog intensive operations such as import, when loading language versions.

 

EPiServer.Find.Commerce 11.2.0;
Nov 19, 2020
COM-10057
  FindSearchProvider doesn't get ServiceUrl and defaultIndex from app settings after a new deployment

Steps to reproduce

1) Deploy a Commerce site using FindSearchProvider to Azure.
2) Make sure everything works as expected, i.e: you can search the catalog in Catalog Entry Search of Commerce Manager, the FindSearchProvider gets values from app settings of web app.
3) Update serviceUrl and defaultIndex in Mediachase.Search.config to invalid values, i.e:
serviceUrl="https://es-eu-dev-api01.episerver.net/BG2y7vnuQICkEqmEOVHAK7SVcuNX4xH4" defaultIndex="dinhnguyen_20190830".
4) Re-deploy the Commerce site.
5) Make sure app settings still have serviceUrl and defaultIndex values. And these values are valid.
6) Navigate to Commerce Manager -> Catalog Management -> Catalog Entry Search.

Expected
No errors, be able to search catalog.

Actual
"401 Unauthorized" error displays. Because the FindSearchProvider doesn't get values from app settings, it still gets value from Mediachase.Search.config file. If you restart the web app, then rebuild the Index in the Administration UI, it works as expected.

EPiServer.Find.Commerce 11.1.2;
Feb 11, 2020
COM-8396
  Index of content should be deleted when move it to another Catalog

Precondition: Install FindCommerce to QuickSilver.

  1. Create a Catalog name Catalog1 with avaiable Language: English
  2. In Catalog1, create a Category name CategoryA. Publish it
  3. Create a category name Sub1 that is child of CategoryA. Publish it
  4. Create a Catalog name Catalog2 with available Language: Svenska
  5. In Catalog2, create a category name CategoryB. Publish it
  6. Move Sub1 from CategoryA to CategoryB
  7. Go to Find/#configure/boosting. Then search by: Sub1

Expected: Sub1 of CategoryA isn't returned. Because it was moved to CatetoryB at step6
Observed: Sub1 of CategoryA is returned. If open it, error will occurs
Note: This issue also happens in FindCommerce 11.0.1

EPiServer.Find.Commerce 11.1.0;
Apr 16, 2019
COM-8542
  Wrong ChildNodeRelations when node and its subnode are published in English and Svenska

Precondition:

  • Install FindCommerce on QuickSilver
  • Catalog Fashion is avaiable at language: English and svenska

1. Go to CatalogUI, In catalog Fashion: create Category NodeA. Publish it at English and Svenska
2. Create a sub node of NodeA named SubNodeA. Publish SubNodeA at English and Svenska
3. Go to Go to Find > Overview > Explore, search for "NodeA"
4. Expand the detail NodeA at Svenska. Search for "ChildNodeRelations"
Expected: SubNodeA should be shown in "ChildNodeRelations"
Observed: SubNodeA isn't shown in "ChildNodeRelations" (bug)

Note: This issue also happens at FindCommerce11.0.1

EPiServer.Find.Commerce 11.1.0;
Apr 16, 2019
1 2 3 4 5 Next