URI resolving in a multi-site context for the HtmlContentInBodyWithRequestsProcessor
Since our pages are composed of content fetched from many items in Sitecore, we added the HtmlContentInBodyWithRequestsProcessor in the indexing pipeline (we did this so that we could have indexed in Coveo our complete pages, and not only parts of it).
It worked fine until we added other sites in Sitecore. For thses new sites, Coveo seems to have problems finding the right URIs to fetch the content of the pages for that site, resulting in the fact that none of the pages of this site are indexed.
I have read many questions asked and the answers you provided, and from what I understand, it is quite difficult for Coveo to determine the URI of an item/page at indexing time (as mentionned here https://answers.coveo.com/questions/7019/clickableuri-is-incorrect-resolveitemsiteprocessor-not-working )
So my question is : can the HtmlContentInBodyWithRequestsProcessor be made to work in a multi-site context?
What we are investigating right now is to add a processor just before to find the URI and set it in the arg, so that the HtmlContentInBodyWithRequestsProcessor can work with a valid URI. Is it a good approach?
We are using CES 7.0 (8047) and Coveo for Sitecore 7.5 v3.0 (1188), which I think are the December 2015 versions.