Gravatar for micallahan@logmein.com

Question by mcallahan, May 12, 2015 11:02 AM

The coveoPostItemProcessingPipeline is not being hit

The coveoPostItemProcessingPipeline is not being hit. I have added the following processor to it (HtmlContentInBodyWithRequestsProcessor), but this pipeline is just not getting called at all.
I have sitecore logging set up in the default layout used by pages, as well as the Coveo device layout (browser agent=Coveo Sitecore Search Provider), and neither one of these layouts get called.
The content type of the item in the index is sitecoreitem, when i think it should be html.

I am currently trying out Coveo with the Free License…. is this something that is not available with the Free License?

<coveoPostItemProcessingPipeline>
  <processor type="Coveo.SearchProvider.Processors.AddCoveoVersionTag, Coveo.SearchProviderBase" />
  <processor type="Coveo.SearchProvider.Processors.HtmlContentInBodyWithRequestsProcessor, Coveo.SearchProviderBase" />
</coveoPostItemProcessingPipeline>
Gravatar for jflheureux@coveo.com

Comment by Jean-François L'Heureux, May 12, 2015 11:26 AM

Which release of Coveo for Sitecore do you use? You can find out the number in the package file name.

February and March 2015 releases had a bug where the HTML content was discarded just before being sent to the RabbitMQ queue. It was fixed in the April 2015 release.

Gravatar for micallahan@logmein.com

Comment by mcallahan, May 12, 2015 11:53 AM

Coveo for Sitecore 80 3.0 (1026)

Gravatar for jflheureux@coveo.com

Comment by Jean-François L'Heureux, May 12, 2015 12:00 PM

1026 is the May 2015 release. It is not affected by this problem.

Gravatar for micallahan@logmein.com

Comment by mcallahan, May 13, 2015 12:53 PM

Has anyone else had this issue with Coveo for Sitecore 80 3.0 (1026)?

3 Replies
Gravatar for micallahan@logmein.com

Answer by mcallahan, May 20, 2015 11:34 AM

I found the problem, not related to Coveo… the hostName in my node was wrong. So it couldn't access the page to crawl it, and it stored it as a SitecoreItem instead of the Html content type.

Gravatar for vseguin@coveo.com

Answer by Vincent Séguin, May 12, 2015 11:04 AM

Hi,

This pipeline is always supposed to be getting called, at indexing time. You need to trigger a rebuild or refresh from Sitecore to see it being triggered.

Gravatar for micallahan@logmein.com

Comment by mcallahan, May 12, 2015 11:10 AM

But shouldn't the Coveo.SearchProvider.Processors.HtmlContentInBodyWithRequestsProcessor processor access the pages using the device layout for coveo(browser agent=Coveo Sitecore Search Provider)? I rebuild the indexes and neither the coveo layout or the default layout get hit.

Gravatar for vseguin@coveo.com

Comment by Vincent Séguin, May 12, 2015 11:14 AM

Hmmm… do you see the item actually being indexed, either in the CES console or in the Sitecore logs?

Gravatar for jflheureux@coveo.com

Comment by Jean-François L'Heureux, May 12, 2015 11:29 AM

Only items that have a layout defined will be requested. And they will be requested on the published website (web database content).

Gravatar for micallahan@logmein.com

Comment by mcallahan, May 12, 2015 11:41 AM

All items are being indexed, i can see them in the CES console. Not just items with layouts.

Gravatar for jflheureux@coveo.com

Comment by Jean-François L'Heureux, May 12, 2015 12:03 PM

Can you check the ShowConfig.aspx page to confirm that your processor is correctly defined in the final Sitecore configuration? You may have another configuration file that is overriding this pipeline node.

Gravatar for micallahan@logmein.com

Comment by mcallahan, May 12, 2015 12:50 PM

Yep, I checked the ShowConfig, it is set up correctly.

<coveoPostItemProcessingPipeline patch:source="Coveo.SearchProvider.config">
  <processor type="Coveo.SearchProvider.Processors.AddCoveoVersionTag, Coveo.SearchProviderBase"/>
  <processor type="Coveo.SearchProvider.Processors.HtmlContentInBodyWithRequestsProcessor, Coveo.SearchProviderBase"/>
</coveoPostItemProcessingPipeline>
Gravatar for lbergeron@coveo.com

Answer by Luc Bergeron, May 12, 2015 11:08 AM

Hi,

Do you have any inbound filter that could prevent the item from being indexed?

Gravatar for micallahan@logmein.com

Comment by mcallahan, May 12, 2015 11:13 AM

I am, but the items are still getting indexed because they are in this path (sitecore/content/sites/Demo)

Items are getting indexed, but it isnt crawling the rendered html of the page.

<indexing.filterIndex.inbound>
  <processor type="Coveo.SearchProvider.InboundFilters.IndexLatestVersionInboundFilter, Coveo.SearchProviderBase" />
  <processor type="Coveo.SearchProvider.InboundFilters.ItemPathInboundFilter, Coveo.SearchProviderBase">
    <ContentStartPaths>/sitecore/content/sites/Demo</ContentStartPaths>
  </processor>
</indexing.filterIndex.inbound>
Ask a question