Packages [expand] [collapse]
Released in version
14.0.4
14.0.2
13.4.8
13.4.7
13.4.6
13.4.5
13.4.4
13.4.3
13.4.2
13.4.1
13.4.0
13.3.0
13.2.11
13.2.10
13.2.9
13.2.8
13.2.7
13.2.6
13.2.5
13.2.4
13.2.3
13.2.2
13.2.1
13.2.0
13.1.1
13.0.5
13.0.4
13.0.3
13.0.1
12.7.1
12.7.0
12.6.2
12.6.1
12.6.0
12.5.3
12.5.2
12.5.1
12.5.0
12.4.3
12.4.2
12.4.1
12.4.0
12.3.3
12.3.2
12.3.1
12.3.0
12.2.9
12.2.8
12.2.7
12.2.5
12.2.4
12.2.3
12.2.2
12.2.1
12.2.0
12.1.0
12.0.1
12.0.0.4448
11.1.7.4454
11.1.6.4396
11.1.5.4342
11.1.4.4296
11.1.3.4160
11.1.2.4113
11.1.1.4013
11.1.0.3965
11.0.0.3701
10.1.0.3493
10.0.0.3291
9.6.0.3185
9.5.0.2999
9.4.0.2900
9.3.0.2674
9.2.0.2446
9.1.0.2335
9.0.0.2183
8.10.1.2073
8.10.0.1509
8.9.0.1462
8.8.0.1354
8.7.0.1103
8.6.0.1055
8.5.0.931
8.4.0.886
8.2.4.684
8.2.3.666
8.2.2.663
8.2.1.643
7.5.454.128
7.5.453.109
7.5.452.100
7.5.451.96
7.5.450.89
7.5.448.68
7.5.446.66
7.5.446.2
7.5.446.1
7.5.440.2
7.5.409.0
7.5.402.0
7.5.394.2
7.0.586.24
7.0.586.16
7.0.586.8
7.0.586.4
7.0.586.0
1.0.0.343
1.0.0.314
1.0.0.286
1.0.0.278

Release notes for Optimizely updates

This topic lists Optimizely updates, delivered as NuGet packages and services. You decide which updates apply to your project; see Installing Optimizely updates (CMS 11 and Commerce 13).

To upgrade to Content Cloud (CMS 12), see Upgrading to Content Cloud.

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
FIND-9204
  Find hit tracking accepts hit.id without type

Fixed an issue that caused a 500 error on an _msearch call while attempting to view search statistics for a specific query. Track ID was supposed to contain [content_type]/[id].

EPiServer.Find 13.4.8;
Mar 15, 2022
FIND-9872
  Adding best bets sends one config request for every existing best bet

Fixed an issue where adding best bets sent one config request for every existing best bet.
If you have many bests bets it can make adding/editing best bets in the Find UI result in a timeout.

EPiServer.Find 13.4.8;
Mar 15, 2022
FIND-9858
  Exceptions should not be kept in memory by the ContentIndexer

Fixed an issue where the content indexer had a collection of exceptions (called _indexingExceptions), which could cause a memory leak.

EPiServer.Find 13.4.8;
Mar 15, 2022
FIND-5583
  3 EpiServer find and ServiceApi Conflict

Fixed an issue where adding ServiceApi to the project caused the unified search to stop working. (If you removed the ServiceApi nugget, it would work again because of a lack of user and roles in the first request.)

EPiServer.Find 13.4.8;
Mar 08, 2022
FIND-9483
  Avoid duplicate hits and inconsistent scoring

Fixed an issue where sometimes visitors got duplicate hits when paginating, which happened only for non-ordered constant score queries because different shards were answering the same query.

EPiServer.Find 13.4.8;
Mar 08, 2022
FIND-9574
  [Netcore] A NullReferenceException exception occurred when adding MapControllerRoute

[Netcore] A NullReferenceException exception occurred when adding MapControllerRoute, when the search result should have been returned.

EPiServer.Find 14.0.4;
Nov 23, 2021
FIND-9316
  Logging of serialization errors was incorrect

Logging of errors was enhanced to be more informative.

EPiServer.Find 13.4.7; EPiServer.Find 14.0.4;
Nov 16, 2021
FIND-6456
  SearchTypeName is not updated when culture updated

When a culture was set in web.config, the indexing job should have updated the SearchTypeName. For example, setting the culture to Swedish (sv-SE), SearchTypeName should have updated to Sida but was listed incorrectly as Page.

EPiServer.Find 13.4.7; EPiServer.Find 14.0.4;
Nov 16, 2021
FIND-9487
  Invisible mode disabled using a Find V1/V2 index

Problem

Find clients on version 13.4.0 - 13.4.4 configured to use an index hosted on a Find v1 or v2 cluster incorrectly disables Invisible Mode.  This disables the indexing queue which is responsible for
1. Processing updates in parallel to the save/publish thread
2. Push updates in batches

Impact

The impact is slow save/publishing in the edit UI as updates to Find are sent in the same thread and not in batches.
It would also affect import jobs that trigger content updates.
You will likely see more bulk requests to Find than you usual.

Only Find indexes on Find V1 and V2 clusters are affected. They have a service url that starts with 
https://us-, https://ap- , https://se-https://eu- , htttps://az- or https://es- 

It will not affect the Find indexing job as it doesn't use the queue.

Workaround 

If you're not able to upgrade right away explicitly setting Invisible to True in an init module works as well

ContentIndexer.Instance.Invisible = true;
EPiServer.Find 13.4.5;
Sep 21, 2021
FIND-9462
  Optimization - TrackQueryCommand.Execute caused unnecessary LOH Heap Allocations

TrackQueryCommand.Execute caused unnecessary LOH Heap Allocations

EPiServer.Find 13.4.5;
Sep 21, 2021
1 2 3 4 5 6 Next