Upgrade to Coveo for Sitecore Hive Framework: FAQ
This article covers some questions related to upgrading from the Legacy UI Framework to the Coveo for Sitecore Hive Framework.
What Am I Gaining If I Decide to Upgrade?
Here is a list of some advantages:
All-new modular components
Separated and specific purpose for each component
Easier to configure
Easier to move around
Allows many layout possibilities out-of-the-box
Easier integration with existing sites
In-file result templating
New features of the new framework won’t be ported to the legacy framework. Only critical bug fixes will be applied to the old framework.
What If I Want to Upgrade?
The Legacy components aren’t compatible with the new framework, so you need to start your search interface over.
It takes some work to create a search interface that looks like your older search interface, but you will end up with reusable and easier to maintain components.
Can I Port My Existing Components?
It depends on your specific component.
Here are some things that were removed.
Coveo for Sitecore no longer bundles jQuery with the new UI.
You can still use jQuery, but the package doesn’t provide an initialization call like this anymore:
This variable has been removed.
This allows having many search Interfaces that have no chances of interfering with each other.
For more information on the new components, see Coveo Hive Renderings Reference Documentation.
To support HTML caching, all code related to a custom context has been transferred to the CoveoForSitecoreContext component and is now all handled client-side instead.
CoveoForSitecore.Context.fields.toCoveo("@yourfield"). The Coveo Search Resources must be included in the page.