Gravatar for

Question by jschjolberg, Apr 6, 2015 12:05 PM

Handling the Click URI when there are multiple Sitecore sites and multiple indexes

I'm having some trouble with the Click URI on my search indexes. I have two search indexes for two different Sitecore sites. It looks like I can only specify one SiteName in my config file. So for the site that I specify in SiteName, the Click URI is written correctly. For the other site, the Click URI is written using the full path (sitecore/content/etc.). Is it possible to specify multiple SiteNames? Or is there some other way to handle this so my Click URI for my second site is written correctly?

1 Reply
Gravatar for

Answer by Jean-François L'Heureux, Apr 6, 2015 12:19 PM

Coveo for Sitecore recently added improved support for multi-sites configuration in the March 2015 release (build 974). If you are using a previous release, I highly suggest you to upgrade to the latest release.

We wrote an article to explain how the click uri is computed in a multi-site configuration (see Understanding How The ClickableUri Value Is Computed).

We now use the <SiteName> value as a fallback only if we fail to detect the item's site.

I hope this helps.

Gravatar for

Comment by jschjolberg, Apr 6, 2015 12:26 PM

Thanks for your reply. I am using this version:

7.0 x64 Build 6684.0

A couple of questions.

Do you know if this version supports multiple sites?

If I do not specify a SiteName, Coveo should find the site that the item belongs to automatically right?

Gravatar for

Comment by Jean-François L'Heureux, Apr 6, 2015 12:53 PM

You're right, without specifying the <SiteName> Coveo is now able to find the site that handles each item.

7.0 x64 Build 6684.0 is the version number of Coveo Enterprise Search (CES) release of May 2014. I suppose you also have a Coveo for Sitecore version from around May 2014. This version does not support multi-sites well.

You should upgrade to the latest version (April 2015) which better supports multi-sites (see Coveo for Sitecore April 2015 Release Home).

You will be upgrading from a one year old release. There was a lot of evolution in the product and we changed many configuration elements. For that reason, I recommend you to carefully read and apply our upgrade best practices (see Best Practices When Upgrading Coveo for Sitecore).

You will need to upgrade Coveo Enterprise Search and Coveo Search API before upgrading Coveo for Sitecore. All the components should be from the same month to work together.

If you have more questions, don't hesitate to post them here (one question per post is recommended).

Ask a question