Loading...
Area: Optimizely Commerce
Applies to versions: 10 and higher
Other versions:

Disabling product update events

Recommended reading 

This topic describes how to disable the event listener. This is useful if you do not want Commerce catalog content to be indexed by Search & Navigation (formerly Find), in solutions where you use the Search & Navigation search provider EPiServer.Find.Commerce.

How it works

EPiServer.Find.Commerce has an event listener that listens for events trigged by the Optimizely Commerce Framework API. The event listener gets typed content for the catalog/node/entry that was added/changed/deleted, and updates the index. You can disable the event listener by setting the appsettings value of episerver:FindIndexCatalogContent to false.

Enable the event listener for front-end and edit servers, to listen for remote events coming from the Commerce Admin user interface [Commerce Manager in version 13 and lower]. By itself, this does not index typed content, because it does not have the types defined in any assembly. Instead, it sends events when something changes, and the front-end server or edit server (with the listener enabled) then indexes typed content of the correct type.

Service API

The Service API indexes the typed content if the configuration file episerver:FindIndexCatalogContent setting is set to true.

Related topics

Do you find this information helpful? Please log in to provide feedback.

Last updated: Sep 28, 2021

Recommended reading