- Search Interface Does Not Return the Expected Results
- Enabling the Interface Editor in Your Salesforce Organization
- Coveo-Powered Search Page Fails to Load After Upgrade
- Insight Panel Refuses to Display
- Unable to Install the Coveo Lightning Component for Community Cloud
- Error When Adding or Accessing Coveo Components in a Lightning Community
- Cannot See Values When Using an Existing Field in a Facet
- Unknown Page for the Current Site Configuration Error With Coveo Lightning Components
- Coveo Object Unavailable in Lightning Component
- The Feature is Not Activated for Your Organization
- Uncaught-DOMException-Failed-to-read-the-'responseText'-property-from-'XMLHttpRequest' Error Message When Using a Component
- Infinite Loading When Trying to Preview a Document in a Quick View
- Access Token Update Required
Coveo Object Unavailable in Lightning Component
When creating a Lightning component that bundles the Coveo components (see Integrating the Coveo Components in a Custom Lightning Component) and trying to reference the
Coveo object, you get an error message that looks like one of the following messages:
Uncaught Action failed: c:communityCoveo$controller$onInterfaceContentLoaded [$ is not a function]
Cannot read property $ of undefined
Your custom component likely uses API version 40, which means that Lightning Locker is automatically enabled. When Lightning Locker is enabled, the
window object isn’t shared with other components.
Your custom component needs to use an API version prior to 40.0.
In Salesforce, open the Developer Console (see Open the Developer Console).
Open your custom component.
In the right sidebar, select Bundle Version Settings.
In the Bundle Version Settings window, next to API Version, select an API version prior to 40.0.