Coveo for Sitecore 5 is now available!

Coveo Search Page Fails to Load After Upgrade

Coveo for Sitecore (September 2016)

Coveo for Sitecore (October 2016)

Symptoms

With the September 2016 release, you get one of the following errors:

  • When accessing the page through the Preview or Experience Editor, the Coveo Search Page seems to be loading forever, with the following error in the browser console.

    Uncaught Value should not be null or undefined
    
  • In the Experience Editor, after adding a facet, it gets reduced to a line, and saving the page gives you the previous behavior.

Cause

This issue arises when you disabled the Display the tabs section option in the Layout properties, or when the coveo-tab-section is absent from your page.

With the new Coveo Search UI, the responsive facets need a coveo-tab-section to load. In itsĀ absence, the Coveo Search Page is unable to load properly.

Resolution

There are two ways to fix this issue:

When You Intend to Add Tabs

You need to add a coveo-tab-section to your Coveo Search Page.

  1. Access your page, and under Publish, select Experience Editor.
  2. Edit your page properties by clicking on the page, and then selecting the Edit Properties button. It should be the first one.
  3. Under Layout, check the Display the tabs section box.
  4. Click on OK to close the properties window, and save your page. Your issue should be fixed.

When You Do Not Intend to Add Tabs

You need to disable the automatic responsive mode.

  1. Access the file associated with your search page.
    1. When using Web Forms, it should be located under or near <Sitecore instance>\Website\layouts, and should be a .ascx or .aspx file.
    2. When using MVC, it should be located under or near <Sitecore instance>\Website\Views, and should be a .cshtml file.
  2. Inside the class="CoveoSearchInterface" section, add the following line:

     data-enable-automatic-responsive-mode="false"
    
  3. Save your file.

  4. In Sitecore, reload your Coveo Search Page, and confirm that your issue is fixed.