March 25, 2019 Release (5.0.301.4)
This section provides build 5.0.301.4 download links for all supported versions of Sitecore. Download and install the Coveo for Sitecore package that matches your version of Sitecore (see Installing Coveo for Sitecore).
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 Installing 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).
There’s an issue with the Coveo Facet Value Suggestions component when using regular Coveo for Sitecore Hive search pages and Coveo for Sitecore SXA search interfaces simultaneously. If you’re using the Coveo Facet Value Suggestions component, see SXA Coveo Facet Value Suggestions Rendering Item Overwriting Hive Item at Installation.
|Coveo for Sitecore||SXA UI components|
[Supported Sitecore Versions]
[SXA Compatibility Tables]
This section summarizes the new features and fixed support cases introduced in the Coveo for Sitecore March 25, 2019 release (5.0.301.4).
|SC-2532||[Hive] Display an error in Experience Editor if the External Components Section
|SC-2810||[Command Center] Prompt users for confirmation on the index Rebuild All action.|
|SC-2840||[Hive] Allow users to add facet value suggestions (see Adding Facet Value Suggestions to Query Suggestions).|
|SC-3071||[Command Center] Prompt users for confirmation on actions that restart the Sitecore instance.|
|SC-3169||[Hive] Display a warning in the web browser developer tools if a Coveo For Sitecore Analytics component is present in the page to indicate that analytics are only logged in a published page.|
|SC-3189||[Command Center] Allow users to select and unselect all fields in a template (see Understanding the Indexing Manager).|
|SC-3202||[Command Center] Filtered out Coveo component data source fields from the Template fields table.|
|SC-3353||Removed hyphens in Coveo for Sitecore item names to avoid potential invalid character issues.|
|SC-3401||Ensure that the Coveo system fields are created on the Coveo organization upon synchronization.|
|SC-3564||[SXA] Support the SXA grid rendering parameters.|
|SC-3577||[Hive] Allow users to change the Coveo Global Searchbox initialization script (see Using Custom Initialization Scripts).|
|SC-3593||The debug logging in the indexing process now shows added and removed document IDs along with their batch ID.|
|Identifier||Service created or updated|
|SC-3605||Added parameter in
|SC-3618||Added a service to refresh an index from a specific item path in Sitecore.|
|Identifier||Case||Fixed support case|
|SC-3580||00048627||Log Coveo Cloud
|SC-3600||00048962||Properly handle retries when HTTP calls are being throttled by Coveo Cloud.|
|SC-3614||00048550||Fixed a concurrency issue when fetching license details.|
|SC-3598||[Hive] Improved the Coveo Search Interface
This section describes how to upgrade Coveo for Sitecore from February 26, 2019 (22.214.171.124) to March 25, 2019 (5.0.301.4).
For the best Coveo for Sitecore experience, always follow the Best Practices When Upgrading Coveo for Sitecore.
Step 1: Upgrade Coveo for Sitecore
Please, ensure that the Microsoft MVC security update MS14-059 is installed on every Sitecore host in your environment.
Log in to the Sitecore Desktop.
Access the Installation Wizard (Sitecore Start Menu > Development Tools > Installation Wizard).
Upload and install the
Coveo for Sitecore XX 5.0.301.4package. 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.
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.
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