June 11, 2024 release (5.0.1368.1)

This is for:

Developer System Administrator
In this article
Important

Per the Coveo Version Support Lifecycle policy, this Coveo for Sitecore 5 release has reached end of support. See available Coveo for Sitecore releases.

Even if this release is no longer supported, you must still perform some of its upgrade steps to upgrade to a more recent version of Coveo for Sitecore.

This release includes the 2.10116.0 version of the JavaScript Search Framework (see April 2024 release (v2.10116.0)).

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).

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 for these versions was December 31, 2023.

New features and enhancements

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

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

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, this Coveo for Sitecore 5 release has reached end of support. See available Coveo for Sitecore releases.

Even if this release is no longer supported, you must still perform some of its upgrade steps to upgrade to a more recent version 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 to streamline the process.

Important

See Leading practices when upgrading Coveo for Sitecore and Upgrade Sitecore with Coveo for Sitecore to ensure successful upgrades.

Step 1: Upgrade Coveo for Sitecore

Important

Make sure the Microsoft MVC security update MS14-059 is installed on every Sitecore host in your environment.

  1. Log into the Sitecore Desktop.

  2. Access the Installation Wizard (Sitecore Start Menu > Development Tools > Installation Wizard).

  3. 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).

  4. When prompted to overwrite files, click Yes to all.

  5. 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.

  6. Once the installation is completed, make sure that you restart both the Sitecore client and server.

    Restart Server and Client dialog

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 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 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 <fieldNames> element:

<fieldType fieldName="permanentid" isFacet="true" settingType="Coveo.Framework.Configuration.FieldConfiguration, Coveo.Framework" />

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.

〈  Previous version upgrade steps

Next version upgrade steps  〉