--- title: February 15, 2023 release (5.0.1202.1) slug: m9ta0384 canonical_url: https://docs.coveo.com/en/m9ta0384/ collection: coveo-for-sitecore-v5 source_format: adoc --- # February 15, 2023 release (5.0.1202.1) > **Important** > > Per the Coveo [Version Support Lifecycle policy](https://docs.coveo.com/en/1485/), this Coveo for Sitecore 5 release has reached end of support. > See [available Coveo for Sitecore releases](https://docs.coveo.com/en/2274/). > > Even if this release is no longer supported, you must still perform some of its [upgrade steps](#upgrade-steps) to [upgrade to a more recent version](https://docs.coveo.com/en/2155#multi-release-upgrade) of Coveo for Sitecore. > Even if this release is no longer supported, you must still perform some of its upgrade steps to [upgrade to a more recent version](https://docs.coveo.com/en/2155#multi-release-upgrade) of Coveo for Sitecore. This release includes the 2.10099.2 version of the JavaScript Search Framework (see [JavaScript Search Framework Release Notes](https://docs.coveo.com/en/n14g0321/)). When using a CDN with the Coveo Hive framework, this release includes the latest 2.10099 version of the JavaScript Search Framework (see [Choosing between local and CDN Coveo JavaScript resource files](https://docs.coveo.com/en/2629/)). ## Release notes This section summarizes the new features and fixed support cases introduced in the Coveo for Sitecore February 15, 2023 release (5.0.1202.1). > **Important** > > Coveo Hive search interfaces now perform front-end calls through the [reverse proxy](https://docs.coveo.com/en/3401/) to generate search tokens, even when you disable the proxy. > [Caching reverse proxy endpoint responses](https://docs.coveo.com/en/n74a0288/) may cause issues. > **Note** > > Coveo has ended support for Sitecore 8 versions. > Sitecore's [extended support end date](https://support.sitecore.com/kb?id=kb_article_view&sysparm_article=KB0641167#SupportPhasesForSpecificProducts) for these versions was December 31, 2022. ### New features and enhancements [cols="15,85",options="header"] |=== | Issue number | Description | WEB-6076 | Added support for Sitecore 10.3 initial release. |=== ### Bug fixes [cols="15,85",options="header"] |=== | Issue number | Description | WEB-5892 | Removed Experience Editor and log warnings when a custom dictionary overrides an out-of-the-box dictionary entry. | WEB-5896 | Fixed issue with `HideDependentCheckbox` which caused `Could not find constructor in ReflectionUtil.CreateObject` warnings. | WEB-5916 | Changed the facet data source `Facet name` option to `Facet ID`. | WEB-6030 | Fixed issue where a Sitecore source would always display as Rebuilding when the Sitecore instance shuts down or restarts. |=== ### Maintenance cases [cols="15,15,70",options="header"] |=== | Issue number | Case | Description | WEB-5876 | 00089140 | Updated all references of `System.Web.WebPages.Razor` to 3.0.0.0 and `System.Web.Mvc` to 5.0.0.0. | WEB-5900 | 00089647 | Optimized use of the cached version of the Coveo license when users are created or updated in Sitecore. | WEB-6024 | 00090944 | Fixed **Command Center** field inclusion issue in Sitecore 10.1 and higher instances. | WEB-6081 | 00093476 | Fixed issue with searches for `@` causing search pages to load forever. |=== ## Upgrade steps > **Important** > > Per the Coveo [Version Support Lifecycle policy](https://docs.coveo.com/en/1485/), this Coveo for Sitecore 5 release has reached end of support. > See [available Coveo for Sitecore releases](https://docs.coveo.com/en/2274/). > > Even if this release is no longer supported, you must still perform some of its [upgrade steps](#upgrade-steps) to [upgrade to a more recent version](https://docs.coveo.com/en/2155#multi-release-upgrade) of Coveo for Sitecore. > Even if this release is no longer supported, you must still perform some of its upgrade steps to [upgrade to a more recent version](https://docs.coveo.com/en/2155#multi-release-upgrade) of Coveo for Sitecore. This section describes how to upgrade Coveo for Sitecore from August 15, 2022 (5.0.1153.1) to February 15, 2023 (5.0.1202.1). If you're upgrading over multiple versions, Coveo has a [procedure](https://docs.coveo.com/en/2155#multi-release-upgrade) to streamline the process. > **Important** > > See [Leading practices when upgrading Coveo for Sitecore](https://docs.coveo.com/en/2155/) and [Upgrade Sitecore with Coveo for Sitecore](https://docs.coveo.com/en/2155/) to ensure successful upgrades. ### Step 1: Upgrade Coveo for Sitecore > **Important** > > Make sure the Microsoft MVC security update [MS14-059](https://docs.microsoft.com/en-us/security-updates/SecurityBulletins/2014/ms14-059) is installed on every Sitecore host in your environment. . Log into the Sitecore Desktop. . Access the Installation Wizard (**Sitecore Start Menu** > **Development Tools** > **Installation Wizard**). . Upload and install the Coveo for Sitecore 5.0.1202.1 package built for the specific version of Sitecore you're running (for example, Sitecore 10.2). . When prompted to overwrite files, click **Yes to all**. . When prompted to overwrite items, select **Overwrite**, then click **Apply to all**. > **Note** > > You might be prompted twice with this question. > Select the **Overwrite** option and click **Apply to all** both times. . Once the installation is completed, make sure that you restart both the Sitecore client and server. ![Restart Server and Client dialog | Coveo for Sitecore 5](https://docs.coveo.com/en/assets/images/c4sc-v5/new-install-a-package-image.png) ### Step 2: Publish your site In the Sitecore **Content Editor**, perform a publish site action. This ensures any changes related to Coveo components in the upgrade are published to the `web` database. ### ⚠️Step 3: Adjust uses of Coveo for Sitecore codebase methods Note the following changes that were made in the Coveo for Sitecore codebase: * `Coveo.CloudPlatformClientBase.CloudPlatformClient.IsSecurityProviderCreationAllowed` This method was removed from the codebase. * `Coveo.AbstractLayer.Security.PermissionsProviderFactory.CreateProvider` The signature of this method was changed. It now only accepts one argument of type `SecurityConfiguration`. If you're using these methods in your code, make the necessary adjustments. --- [〈{nbsp}{nbsp}Previous version upgrade steps,role="float-start btn home-outline-btn d-inline-flex px-150 mt-100"](https://docs.coveo.com/en/m3gf4364#step-2-manually-update-coveo-configuration-files) [Next version upgrade steps{nbsp}{nbsp}〉,role="float-end btn home-outline-btn d-inline-flex px-150 mt-100"](https://docs.coveo.com/en/n3ne0564#step-2-manually-update-coveo-configuration-files) {nbsp} {nbsp} {nbsp}