-
Known Issues
- An Index Should Be Configured for Database web Error Is Preventing the REST Service from Loading
- Cannot insert the value NULL into column ID, table YourSitecoreSite\_Core.dbo.Properties column does not allow nulls. INSERT fails.
- Coveo for Sitecore Not Properly Replicating the Sitecore Permission Model
- ERROR Error in FileWatcher Internal Buffer Overflow While Installing Coveo for Sitecore
- ERROR Exception while handling event Sitecore.ContentSearch.Events.IndexingFinishedEvent, Index my\_Index was not found
- Error in the Experience Profile After Installing Coveo for Sitecore
- Failed to Reactivate the Organization Message in Command Center
- Field Is No Longer Indexed in the Sitecore Items
- Handler CoveoSearchEndpoint has a bad module ManagedPipelineHandler in its module list
- Items in Different Languages Are Not Automatically Indexed or Updated When Language Fallback Is Enabled
- Metadata Duplicated Keys are Producing Warnings in the Log Browser
- Missing Valid xDB License
- Multi-Value Field - Migrating from On-Premises to Cloud Version
- Opening the Experience Explorer Sets the Static Context to 'Master'
- Prebinding Is Not Applied to Elements Within a Searchbox Container
- Publishing Multi-Language Sitecore Items Leads to a Large Amount of Files Being Indexed
- Sitecore 8.0+ Error When Saving a Coveo Search Page Using the Sitecore Rule Engine
- Sitecore 8.2 With WFFM Refuses to Start After Installing Coveo for Sitecore
- Sitecore.ContentSearch.SitecoreItemCrawler.IsAncestorOf(Item item) error
- Slow Initial Rebuild Time Caused By The ExcludeCoveoDataSourceItems Processor
- Solr - Error When Initializing Coveo When Side-by-Side with Solr Is Enabled
- Solving the Conflict Between Keys from Dynamic Placeholder Modules and Coveo Dynamic Placeholders
- The Experience Editor for Non-Default Language Page Fails to Load When Using Coveo for Sitecore Hive
- The RouteData must contain an item named 'controller' error with SXA
- Two Instances of the Same Search Page Component Have Been Added on a Page but Only One is Initialized
- Unexpected Token < When Editing Page With SXA Components in Experience Editor
- Send Analytics to Sitecore Component Not Working in Sitecore 9
- Exception When Trying to Switch Organization
- Issues When the Core Database Is Disabled on Content Delivery Servers
- Content Database 'master' Not Found on a Content Delivery Server
- Coveo Analytics Events Are Not Logged in Sitecore 9.1 Analytics
- Ajax Error 500 When Using Special Characters in a Query
Prebinding Is Not Applied to Elements Within a Searchbox Container
Coveo for Sitecore (September 2018)
Symptoms
You have a component inside a searchbox container but a prebinding operation is not applied on this component. When inspecting or viewing the source of the rendered page in your browser, the component <div> tag is missing an attribute and/or an attribute value is incorrect.
In the rendered page, you inspect a component on which the fieldTranslator method should have been applied. You notice that the component <div> tag does not contain data-applied-prebind="true", nor does it show a value in the Coveo for Sitecore format for the data-field attribute.
Cause
The executed method initializes the component context directly on the searchbox component rather than on the searchbox container.
Resolution
You can add the following JavaScript code at the bottom of the Coveo Searchbox.cshtml file to ensure prebinding operations are applied on all searchbox container components.
<script>
// Workaround to initialize prebinding attributes on all the elements used in the Searchbox container.
document.addEventListener("DOMContentLoaded", function() {
var searchBoxContainer = document.getElementById("@(Model.Id)_container");
CoveoForSitecore.Prebinding.applyPrebindingOnElement(searchBoxContainer);
CoveoForSitecore.Prebinding.applyPrebindingOnChildren(searchBoxContainer);
});
</script>
Better yet, if you know the Searchbox ID, you can replace @(Model.Id)_container with the Searchbox ID in the document.getElementById("@(Model.Id)_container") code line and place the script anywhere on the page.