Hot answers tagged

5

Engin was likely autocorrected to engine because the Coveo Index has detected that it's a simple mistyping of engine. This works with the DidYouMean feature, that allows you to enter a query that is one letter away from a common (enough) word in your index, and automatically corrects it: https://coveo.github.io/search-ui/components/didyoumean.html As for ...


3

If you are using a recent version of Coveo for Sitecore you may be able to change some config values by using the Coveo Command-Center. For other config values such as the SearchAPI URL, you will need to update the config file directly. Most of the configurations you want to change will be under App_Config/Include/Coveo/Coveo.CloudPlatformClient.Custom....


3

The encryption key used to encrypt the sensitive configuration nodes of Coveo. The encryption keys are stored in the core database with the latest versions. So that can be shared by the farm starting version 4.0.780. The file system based encryption key is legacy mode and can be turned on with a setting. The legacy file system based encryption key can be ...


1

To answer your questions directly, no, you should not install CES or the Search API on your CD servers. As for your second question, yes, it should query your CM Search API. It is even recommended that you install CES and the Search API on a different server so that working with Sitecore won't affect Coveo Enterprise Search performance (or the other way ...


1

For Coveo Cloud Platform for Hive: Local Search information: Log into the Coveo Cloud Manager from your sitecore instance's Control panel. From there you will log in from the configuration tab. This will update a few items that you can add into source control, which exist in the App_Config/Include/Coveo/Coveo.SearchProvider.Custom.config file. These will ...


1

You need to review the coveo search config files and make copies of QA index definitions and name them with "DEV_" prefix so you know. Once you define for all databases (master, web, core) you should see these new index definitions in the index manager in sitecore control panel. Select only these indexes (prefix "DEV_") and index them.


1

So I did not find an outright "fix", however, I do have a workaround that enables this to work. In addition to the above httpProtocol section I posted in the description in the specific web.config file, I also created my own HttpHandler just for OPTIONS requests that come in. public class CoveoOptionsHandler : IHttpHandler { public bool IsReusable { ...


Only top voted, non community-wiki answers of a minimum length are eligible