In this post we dive deeper into the `RelationRepository`, `CatalogContentStructureProvider`, `IInventoryService` and `IPriceService`. 4 items you need to be aware of before putting everything together.
As explained in the introduction of this series implementing a custom Catalog is not only overriding / replacing the `CatalogContentProvider`. In this chapter we are dive deeper into the the realted classes which do need some attention.
When you have written a content provider before you are aware that you have to have to point it to a location where to ‘start’ from. For a `CatalogContentProvider` we have to add some code to support this way of working as well. In this chapter we dive deeper into whats needed for this.
Controlling Episerver Find by determining which catalogs and how many items to be indexed.
A client of ours asked us a while back to implement Azure B2C authentication for their Episerver implementation. The client is running 15+ websites, each on their own TLD for global presence. They are running their website all over the world, from The Netherlands, Germany, Brazil to China. Note, the websites are not running on a separate subdomain, which is implemented out-of-the-box (and allowed) using Azure B2C. In this blog I will describe the hurdles we had to take to get Azure B2C working on multiple TLD websites.