Packages [expand] [collapse]
Released in version
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-19658
  Unnecessary stream allocation in FileCache

FileCache can create an unnecessary stream, even if the file was cached.

EPiServer.CMS.Core 11.20.8;
Sep 07, 2021
CMS-19174
  Race Condition in ContentModelILCompiler.GetOrGenerate()

Bug in the form of a race condition in

EPiServer.DataAbstraction.RuntimeModel.Internal.ContentModelILCompiler.GetOrGenerate().

The bug causes 500 Internal Server Errors for visitors on high volume sites during site startup.

 

EPiServer.CMS.Core 11.20.7;
Jun 15, 2021
CMS-15877
  Missing index for stored procedure netContentChildrenReferences

Introduce an index that will help this highly utilized stored procedure that backs one of the provider calls to .GetChildren(). Adding this index will bring each of the branches down Logical IOs by 98+% on tblContent.

EPiServer.CMS.Core 11.20.7;
Jun 15, 2021
CMS-19460
  Softlink publishing should support same reference ID from different providers

Steps to reproduce:

  1. Create a Alloy site.
  2. Configure a custom content provider (for example, an XML content provider).
  3. Create a content item on the default content provider with ID XXX and publish it.
  4. Create a content item on the custom content provider with the same ID XXX and publish it.
  5. Create a content item that includes an XML html string property.
  6. Add content link (XXX) and custom content link into XML html string property.
  7. Publish the content item from step 6.

Expected result:

Publish should be done without an exceptions.

Actual result:

Publish throws exception (item already exist).

EPiServer.CMS.Core 11.20.7;
Jun 15, 2021
CMS-19409
  Import of contents added system:references properties as warning message

Import content to a site with keep identity.
You see lot of warnings like:
"10.5.2 Export/import warning: [Importing content 106_107] Property 'EPi:SystemReference' does not exist on destination content type".

EPiServer.CMS.Core 11.20.7;
Jun 15, 2021
CMS-18473
  Login redirects are cacheable

When an AccessDeniedException is thrown and a handler handles the necessary redirect, we don't explicitly set cache headers that forces no caching of the response.

Today we only set 'private' which should stop proxies from caching the response, but we can be even more explicit and set both 'no-store' and 'no-cache'.

EPiServer.CMS.Core 11.20.6;
Apr 06, 2021
CMS-18476
  Content URL cache does not invalidate cache remotely

DefaultContentUrlCache is using IObjectInstanceCache and not ISynchronizedObjectInstanceCache. Therefore, URLs are not removed from all instances in a load-balanced setup.

Reported from Content url caching not invalidating on synchronized sites (episerver.com)

How to reproduce:

  • Set up a load-balance environment with remote events.
  • Upload an asset.
  • Render link to asset in a view.
  • Access the view from both nodes and click the link.
  • Change the URL to the asset from one of the nodes.
  • Refresh the view on the other node and click the link.
EPiServer.CMS.Core 11.20.6;
Apr 06, 2021
CMS-18005
  Should not allow to create "regularExpression" validation if pattern is invalid

Steps to reproduce:
Define a content type via Definitions Api.
Note: A "regularExpression" validation is added to a string property but its pattern is invalid. For example, "pattern": "[0-9]++"

{
	"name": "PageRegExValidationInvalidCase3",
	"baseType": "Page",
	"editSettings": {
		"available": true,
		"order": 0
	},
	"properties": [
        {
			"name": "String1",
			"dataType": "PropertyString",
			"validation": [
				{
					"name": "RegularExpression",
					"severity": "error",
                    "pattern": "[0-9]++",
					"errorMessage": "String 1: pattern is invalid"

				}
			]
		},
        {
			"name": "StringList1",
			"dataType": "PropertyStringList",
			"validation": [
				{
					"name": "itemRegularExpression",
					"severity": "error",
                    "pattern": "[0-9]++",
					"errorMessage": "String List 1: pattern is invalid"

				}
			]
		}
	]
}

Expected result: 
Content management is created with invalid pattern return 400- Bad Request.

Actual result:
Content type is created with invalid pattern. 

Content management is created with invalid pattern return 500.

EPiServer.CMS.Core 11.20.5;
Feb 23, 2021
CMS-17771
  Fallback language is sometimes selected instead of language version when using simple address

Steps to reproduce:

  1. Enable multiple languages like this:
  2. Set root to enable all the languages and set the fallback language to "en" for every language except en.
  3. On page Alloy Plan, set simple address to "alloy".
  4. Create different language versions of Alloy plan and set simple address to "alloy" for all the different language versions.
  5. Go to the different language versions by using their simple address. So for German go to site.com/de/alloy or Swedish site.com/sv/alloy.

Expected result:

The different language versions of the page should be displayed.

Actual result:

Sometimes, the English version is displayed even if there is a language version available.

 

EPiServer.CMS.Core 11.20.5;
Feb 23, 2021
CMS-15508
  Selection property created from UI has no selections

Steps to reproduce:

  1. In admin view, create a new page type.
  2. Add a new property of the type 'Drop-down list'.
  3. Edit the newly created property and add some selections under the tab 'Custom settings'.
  4. Navigate to edit view and create a page of this page type.

Expected result:

The newly created property should have the selections you just added.

Actual result:

The property has no available selections.

EPiServer.CMS.Core 11.20.4;
Feb 10, 2021
1 2 3 4 5 6 Next