March 26, 2021 Release (5.0.943.3)
March 26, 2021 Release (5.0.943.3)
This section provides build 5.0.943.3 download links for all supported versions of Sitecore. Download and install the Coveo for Sitecore package that matches your version of Sitecore (see Install Coveo for Sitecore in a Sitecore On-Premise Environment ).
If you’re using SXA and want to be able to insert Coveo components in your SXA pages, download and install both the Coveo for Sitecore package and the SXA UI Components package (see Install Coveo for Sitecore SXA Components).
If you want to upgrade your version of Coveo for Sitecore 5 to this release, follow the upgrade procedure (see Upgrade Steps).
For the simultaneous deployment of Sitecore 9.1 and Coveo for Sitecore on Azure, download the
Sitecore 9.1 (WDP) package and the
coveoforsitecore-module.json file (see Install Coveo for Sitecore Alongside Sitecore in Azure PaaS).
This section summarizes the new features and fixed support cases introduced in the Coveo for Sitecore March 26, 2021 release (5.0.943.3).
|SC-4107||Removed warnings in the logs when the Coveo indexes were already initialized and when the first entry of the
|SC-4764||Added support for Sitecore 10.0.1.|
|WEB-4811||Added support for Sitecore 10.1 and SXA 10.1.|
|Identifier||Case||Fixed Support Case|
|WEB-4795||00065927||Fixed issue with improper Coveo media library item field type preventing generation of valid WDP packages.|
|WEB-4907||00066467, 00065997, 00066604||Deprecated the
|SC-4777||Fixed email anonymous identity being logged in the
|SC-4778||Fixed issue where duplicate
|WEB-4796||Fixed issue with errors thrown upon accessing the Content Editor when Coveo for Sitecore is not activated.|
|WEB-4828||Fixed issue with the Command Center endlessly loading upon login when there is an error getting the list of organizations.|
This section describes how to upgrade Coveo for Sitecore from February 12, 2020 (5.0.900.5) to March 26, 2021 (5.0.943.3). If you're upgrading over multiple versions, Coveo has a procedure to streamline the process.
|For the best Coveo for Sitecore experience, always follow the Leading Practices When Upgrading Coveo for Sitecore.|
Step 1: Upgrade Coveo for Sitecore
|Make sure the Microsoft MVC security update 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.943.3 package built for the specific version of Sitecore you’re running (e.g., Sitecore 9.0). You can find it in Downloads.
- When prompted to overwrite files, click Yes to all.
When prompted to overwrite items, select Overwrite, then click Apply to all.NoteYou 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.
Step 2: Manually Update the Coveo Configuration Files
The Coveo configuration files are located in the
App_Config\Include\Coveo folder. When upgrading, you must compare the changes to the
.example files from your current Coveo for Sitecore version with the ones in the build you’re upgrading to. Then, you can merge these changes into your current configuration files. This method lets you keep your customization intact, while still benefiting from the latest enhancements brought in the product. You can use a merge tool such as WinMerge to accomplish this.
In further detail, here are the modifications that you must perform to the configuration files resulting from the feature changes between the previous and current Coveo for Sitecore releases:
<processor> element (and its leading comment) has been added as the last child of the
<renderContentEditor> element. Until now, this processor definition was located in the
Coveo.SearchProvider.Licensing.config file, from which it has been removed.
<!-- The CoveoRenderContentEditor processor hides sections in the Content Editor based on available features. --> <processor patch:before="*[@type='Sitecore.Shell.Applications.ContentEditor.Pipelines.RenderContentEditor.RenderSkinedContentEditor, Sitecore.Client']" type="Coveo.SearchProvider.Licensing.Processors.CoveoRenderContentEditor, Coveo.SearchProvider.Licensing" />
Apply these changes in your configuration.
<settings> element has been added as a child of the
<sitecore> element, to streamline the process of patching elements in the
<settings> section of the
You can apply this change in your
Step 3: Enable the CleanHtml Processor
CleanHtmlWithSimpleSelectors processor added in the February 12, 2021 release of Coveo for Sitecore had to be deprecated in this release. It will no longer be maintained and supported. The instructions below will allow you to revert to the CleanHtml processor.
An alternative to processors in Sitecore for removing HTML content is using Coveo indexing pipeline extensions (IPE). After re-enabling the CleanHtml processor, we recommend you refer to the Remove HTML Sections From Indexed Sitecore Items article for instructions and a code sample on how to achieve this.
To re-enable the CleanHtml processor
Open the Command Center Indexing Options accessible at
Index rendered HTMLoption is selected
Only index Sitecore item data.
Click Apply and Restart.
In the Command Center left menu, select Indexing Options to return to the indexing options screen.
Index rendered HTMLoption.
Click Apply and Restart.
Step 4: (Optional) Leverage the New Dynamic Facet and Dynamic Hierarchical Facet Data Source Options
CustomSortDelimitingCharacter options. The
CustomSort option has been added in both the Coveo Dynamic Facet and the Coveo Dynamic Hierarchical Facet data source. The
CustomSortDelimitingCharacter option has been added in the Coveo Dynamic Hierarchical Facet data source. For more details on these options and how to leverage them, see Coveo Dynamic Facet - Data Source Options and Coveo Dynamic Hierarchical Facet - Data Source Options.
Step 5: 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