Packages [expand] [collapse]
Released in version
12.1.0
12.0.4
12.0.3
11.20.10
11.20.9
11.20.8
11.20.7
11.20.6
11.20.5
11.20.4
11.20.3
11.20.2
11.20.1
11.20.0
11.19.0
11.18.1
11.17.0
11.16.0
11.15.1
11.15.0
11.14.2
11.14.1
11.14.0
11.13.2
11.13.1
11.13.0
11.12.0
11.11.3
11.11.2
11.11.1
11.11.0
11.10.6
11.10.5
11.10.4
11.10.3
11.10.2
11.10.1
11.10.0
11.9.4
11.9.3
11.9.2
11.9.1
11.9.0
11.8.1
11.8.0
11.7.1
11.7.0
11.6.0
11.5.4
11.5.3
11.5.2
11.5.1
11.5.0
11.4.0
11.3.4
11.3.3
11.3.2
11.3.1
11.3.0
11.2.1
11.2.0
11.1.0
10.10.5
10.10.4
10.10.3
10.10.2
10.10.1
10.10.0
10.9.2
10.9.1
10.9.0
10.8.0
10.7.0
10.6.0
10.5.0
10.4.3
10.4.2
10.4.1
10.4.0
10.3.2
10.3.1
10.3.0
10.2.0
10.1.0
10.0.1
9.12.5
9.12.4
9.12.3
9.12.2
9.12.1
9.12.0
9.11.0
9.10.2
9.10.1
9.10.0
9.9.1
9.9.0
9.8.3
9.8.2
9.8.1
9.8.0
9.7.3
9.7.2
9.7.1
9.7.0
9.6.1
9.6.0
9.5.1
9.5.0
9.4.0
9.3.3
9.3.2
9.3.1
9.3.0
9.2.1
9.2.0
9.1.0
9.0.3
9.0.2
9.0.1
9.0.0
8.11.0
8.10.1
8.10.0
8.9.0
8.8.2
8.8.1
8.8.0
8.7.0
8.6.0
8.5.0
8.4.0
8.3.0
8.2.0
8.1.0
8.0.0
7.19.2
7.19.1
7.19.0
7.18.0
7.17.0
7.16.1
7.16.0
7.15.0
7.14.2
7.14.1
7.14.0
7.13.3
7.13.2
7.13.1
7.13.0
7.11.0
7.10.0
7.9.1
7.9.0
7.8.2
7.8.1
7.8.0
7.7.1
7.7.0
7.6.5
7.6.4
7.6.3
7.6.2
7.6.1
7.6.0
7.5.1003.0
7.5.1002.0
7.5.1000.0
7.5.440.0
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.1
6.1.379.0

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.

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
CMS-14681
  Migration step: GroupName on property was not updated

Migration step: GroupName on property was not updated. It was created under the NewGroupName tab, and the old property was moved to the Content tab.

EPiServer.CMS.Core 11.20.10;
Nov 23, 2021
CMS-20624
  Optimizing Commerce content creation

For each Commerce content that was created, it was determined whether the type should use a proxy. This was optimized – since a .NET type will not change during the lifetime of the application – so the first evaluation was cached for later evaluations.

EPiServer.CMS.Core 11.20.10;
Nov 23, 2021
CMS-20845
  Thread starvation caused by MARS set to true on connection string

When connection string was configured with MultipleActiveResultSets (MARS) set to true the application generated SQL timeout exceptions when running on Linux due to thread starvation.

EPiServer.CMS.Core 12.1.0;
Nov 16, 2021
CMS-17408
  ContentType.DisplayName with only spaces did not fallback to Name

If you saved DisplayName with only spaces, it did not show correctly in UI Admin. It should have a fallback to ContentType.Name.

EPiServer.CMS.Core 12.1.0;
Nov 16, 2021
CMS-18334
  Fallback language not used and AlternateLinks handler wrote out an expired version

When accessing the URL of language content that was expired, the AlternateLinks handler wrote out the expired version that then became a 404 error, instead of using the fallback language.

EPiServer.CMS.Core 12.1.0;
Nov 16, 2021
CMS-18001
  Scheduled job Remove Unrelated Content Assets should not stop at error

When the job failed to delete a content asset folder, the job was stopped and marked as failed instead of logging the issue and continuing with other candidates.

EPiServer.CMS.Core 12.1.0;
Nov 16, 2021
CMS-20452
  Migration step: GroupName on property was not updated

Migration step: GroupName on property was not updated. It was created under the NewGroupName tab, and the old property was moved to the Content tab.

EPiServer.CMS.Core 12.1.0;
Nov 16, 2021
CMS-18355
  LinkValidator threw exception

Steps to reproduce: 

  1. Install Alloy.
  2. Update EPiServer.CMS package to 11.15.1.
  3. Compile and build.
  4. On start page, add a Button block in a content area.
  5. Enter required text.
  6. In link, click external and paste the JavaScript:
    javascript:void(location.href='mailto:' + String.fromCharCode(106,111,104,97,110,46,97,110,116,105,108,97,64,111,112,116,105,109,105,122,101,108,121,46,99,111,109))
  7. Save and publish block and page.
  8. Go to admin.
  9. Run Link Validator job.

An exception caused the job to fail and stop executing, instead of marking it as an invalid link and ignoring it going forward, to complete with a summary of scanned links and failed links.

EPiServer.CMS.Core 12.1.0;
Nov 16, 2021
CMS-20408
  Multi-site content language not resolved correctly with localhost and port

In a multi-site scenario, locally (with localhost and separate port numbers), content language was not determined correctly because the code in EPiServer.Globalization.Internal.HostLanguageResolver was only comparing the host name, and not the port number.

EPiServer.CMS.Core 12.1.0;
Nov 16, 2021
CMS-20621
  The logging compatibility API was made obsolete.

The logging compatibility API was made obsolete. It was added to simplify the transition fro log4net but is no longer needed.

EPiServer.CMS.Core 12.1.0;
Nov 16, 2021
1 2 3 4 5 6 Next