Try our conversational search powered by Generative AI!
AI OnAI Off
New Catalogs doesn't show in catalog node picker
The picker populates using the page provider, the commerce manager should send a Cache invalidation msg to <cmsSite>/Services/EventService.svc and thus invalidating the cache for that part of node structure on the cms site. By default these should already be in you config though.
cms site should contain this among the service bindings in web.config.
<service name="EPiServer.Business.Commerce.EventService" behaviorConfiguration="EPiServer.Business.Commerce.EventServiceBehavior">
<endpoint address="" binding="webHttpBinding" contract="EPiServer.Business.Commerce.IEventService" behaviorConfiguration="EventServiceEndpointBehavior" />
<endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange" />
</service>
and the manager site the following:
<endpoint name="eventSvcEndpoint"
address="http://<your cms site>/Services/EventService.svc"
binding="webHttpBinding"
behaviorConfiguration="EventServiceEndpointBehavior"
contract="EPiServer.Business.Commerce.IEventService" />
Aug 02, 2013 21:06
We have a issue with our new site thats running commerce.
We add a new Catalog node but when trying to pick that node from the CMS (using catalog picker property) The node doesn't show. Opening the catalog browser to the right (same window showing blocks and files) will how ever show the new node.
To make it show up in the picker we need to recycle the app pool so my guess is a cache somewhere. Anyone know where this cache could be and how we go about to clear it if new nodes are added?