--- title: June 11, 2024 release (5.0.1368.1) slug: o4te0333 canonical_url: https://docs.coveo.com/en/o4te0333/ collection: coveo-for-sitecore-v5 source_format: adoc --- # June 11, 2024 release (5.0.1368.1) :page-create-version-block-in-assets/version-tags/sitecore-version.adoc: done > **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.10116.0 version of the JavaScript Search Framework (see [April 2024 release (v2.10116.0)](https://docs.coveo.com/en/n14g0322#april-2024-release-v2101160)). When using a CDN with the Coveo Hive framework, this release includes the latest 2.10116 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 June 11, 2024 release (5.0.1368.1). > **Note** > > Coveo has ended support for Sitecore 9.0 releases. > 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, 2023. ### New features and enhancements [cols="15,85",options="header"] |=== | Issue number | Description | WEB-5554 | Updated user interface labels to reflect Coveo Platform terminology. | WEB-6817 | Added support for Coveo JavaScript Search Framework version 2.10116. | WEB-6894 | Added support for Sitecore 10.4 initial release. |=== ### Bug fixes [cols="15,85",options="header"] |=== | Issue number | Description | WEB-6620 | Changed settings on some special fields (that is, `source` and `permanentid` now have `IsFacet`, `language` now has `IsMultiValue`). | WEB-6622 | Improved the efficiency of the security provider creation process. | WEB-6647 | Fixed **Resources & Support** links in the **Control Panel**. | WEB-6685 | Fixed vulnerabilities. | WEB-6836 | Fixed the content structure of the **Coveo Page View Analytics** request payload. | WEB-6922 | Removed no longer required usage reporting. | WEB-6937 | Fixed the analytics endpoint being used when you bypass the Coveo for Sitecore proxy. | WEB-6954 | Simplified the way the Usage Analytics endpoint is composed, depending on the context. |=== ### Maintenance cases [cols="15,15,70",options="header"] |=== | Issue number | Case | Description | WEB-6562 | 00104719 | Ensured all responses for search queries go through the `coveoProcessParsedRestResponse` pipeline. | WEB-6574 | 00105544 | Fixed issue with wrong language arguments in media item clickable URIs. | WEB-6864 | 00111719 | Stopped logging `'p_Tracker' must not be null'` errors when the Sitecore Tracker is unavailable (for example, when using Sitecore XM). | WEB-6881 | 00111817, 00112119 | Added handling of Sitecore URL rewrites in the recomputation of clickable URIs at query time. |=== ## 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 October 23, 2023 (5.0.1277.4) to June 11, 2024 (5.0.1368.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/2606/) 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.1368.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](https://docs.coveo.com/en/assets/images/c4sc-v5/new-install-a-package-image.png) ### Step 2: Manually update Coveo configuration files Coveo for Sitecore packages contain some `.config.example` files. When you activated Coveo for Sitecore, the `.config.example` configuration files copied to your Sitecore instance were renamed (the `.example` was removed) making them enabled `.config` files. The name change also prevents the resulting `.config` files from being overwritten by `.config.example` files during a Coveo for Sitecore upgrade. In a nutshell, Coveo uses `.config.example` files for upgrade configuration changes that must be merged manually. Otherwise, Coveo uses standard `.config` files that get overwritten during [step 1](#step-1-upgrade-coveo-for-sitecore) of the upgrade process. > **Tip** > > Use a tool like WinMerge to compare the new `+Coveo.**.config.example+` files with your existing `+Coveo.**.config+` files. > **Important** > > The October 23, 2023, release of Coveo for Sitecore introduced changes that can cause a `500 - Internal Server Error` when trying to access pages such as `/coveo/rest` in this release. > See [Internal Server Error when accessing package pages](https://docs.coveo.com/en/oaa90229/) for the resolution. Here are the modifications to the `.config.example` files between the previous and current Coveo for Sitecore releases: #### Coveo.SearchProvider.config The following element has been added as a child of the `` element: ```xml ``` Apply this change to your configuration. ### Step 3: 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. --- [〈{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/n5jd0437#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/o9ud0570#step-2-manually-update-coveo-configuration-files) {nbsp} {nbsp} {nbsp}