June 18, 2019 release (5.0.407.4)
June 18, 2019 release (5.0.407.4)
Per the Coveo Version Support Lifecycle policy, this Coveo for Sitecore 5 release has been retired. See available Coveo for Sitecore releases. Even if this release is retired, 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.6063.7 version of the JavaScript Search Framework (see May 2019 Release (v2.6063)).
When using a CDN with the Coveo Hive framework, this release includes the latest 2.6063 version of the JavaScript Search Framework (see Understanding How the Coveo JavaScript Files are Loaded (CDN)).
Release Notes
This section summarizes the new features and fixed support cases introduced in the Coveo for Sitecore June 18, 2019 release (5.0.407.4).
Identifier | Enhancement |
---|---|
SC-3660 |
[Hive] Added the Additional Dictionaries field on the Coveo Search Resources component data source (see Edit the Content of a Result Template: The translateLabel Function). |
SC-3781 | Provided a WDP package for fresh installs of Coveo for Sitecore with Sitecore 9.1 on Azure PaaS (see Install Alongside Sitecore in Azure PaaS). |
SC-3877 |
[Hive] Ensured Additional Data Attributes option is available in all renderings that wrap Coveo JavaScript Search Framework components. |
SC-3898 | Support Coveo JavaScript Search Framework version 2.6063. |
Identifier | Case | Fixed support case |
---|---|---|
SC-3881 | 00053716 | Improved the handling of invalid Sitecore users when using a custom membership provider. |
Identifier | Bug fix |
---|---|
SC-3943 | [Hive] Fixed issue causing the Coveo for Sitecore Analytics data source to display incorrect list of fields in Sitecore 9. |
SC-3893 | Fixed the Coveo Diagnostic Page compilation issue in Sitecore 7.5 and 8.0 instances. |
SC-3896 | Fixed issue with Coveo for Sitecore Legacy UI items still being installed in the core database. |
SC-3900 | Fixed button links in the Developer & Support Resources panel. |
SC-3917 | Coveo Diagnostic Page in Sitecore 7.5 and 8.0 instances now references jQuery 3.4.0. |
Upgrade Steps
Per the Coveo Version Support Lifecycle policy, this Coveo for Sitecore 5 release has been retired. See available Coveo for Sitecore releases. Even if this release is retired, 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 May 17, 2019 (5.0.387.10) to June 18, 2019 (5.0.407.4). 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 Best 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 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.407.4
package. -
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: Delete Coveo for Sitecore Legacy UI Items
-
Open the Sitecore Desktop.
-
Switch to the
core
database. -
Open the Content Editor.
-
In the content tree, navigate to the
/sitecore/content/Applications/WebEdit/Custom Experience Buttons
folder. -
Delete the four items below. Do not delete the
Edit Coveo Data Source
item.-
Edit Coveo Facet Properties
-
Edit Coveo Search Properties
-
Edit Coveo Sort Properties
-
Edit Coveo Tab Properties
-
-
Return to the Sitecore Desktop and set your active database back to
master
.
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 to the web
database.