EPiServer CMS 11.18.0 delisted from Nuget feed

We are investigating a compatibility issue where EPiServer.CMS.Core 11.18.0 can cause problems with other parts of the platform, e.g. Search and Navigation (Find).

For the time being we have de-listed this version from the Episerver nuget feed while we continue to investigate the issue.

If you have already deployed a solution using this version, please reach out to Episerver application support to determine if you can be affected by this and what steps you should take to resolve any issues you might have from it.

If you are in the process of updating your solution to this version, hold off on the upgrade for now.

Our sincerest apologies for any inconveniences this might cause.

Originally published 2020-08-28 11:32 CEST

Update 2020-08-28 15:33 CEST:

We took the decision to not only delist, but to delete the 11.18.0 version from the Nuget feed. This will cause issues restoring packages for anyone who has already updated, but that is intentional, a way to draw attention to the issue with that version.

We are working on a fixed 11.18.1 version that we hope to have QA:ed and released early next week. Anyone updating from a pre-11.18 version to 11.18.1 will be safe from this issue. Anyone who has deployed with 11.18.0 are still adviced to reach out to Application support to determine what steps to take.

Update 2020-09-01 09:16 CEST:

The patched 11.18.1 version has been released.

Update 2020-09-02:

There are reports of issues when updating from 11.18.0 to 11.18.1 since the former has been removed from the feed. If you run into such issues, you can download CMS 11.18.0 (NOT for production use) here.

Update 2020-09-29:

CMS 11.19.0 was released 2020-09-15. This version automatically handles compatibility with Find. If Find 13.2.8 or earlier is used, CMS automatically falls back to the pre-11.18.0 behavior to ensure there are no compatibility issues. If Find 13.2.9 or later is used, CMS can use the new memory optimized Content proxies. You can still force it to use the old Castle proxies by using this appSetting:

<add key="episerver:setoption:EPiServer.Core.ContentOptions.ProxyType,EPiServer" value="Castle" />

In the absence of any setting, the default is to use the new optimized proxies (equal to setting the above AppSetting to "Optimized").