Probably a bit of a niche subject but if you've ever wanted a nested hierarchical facet in Episerver Find this is for you! It builds on the existing HierarchicalFacet2Find code and adds support for nested fields.
Imagine that you have two different nodes in your Episerver Commerce catalog and you want these to be routed to different specifiable URLs within the site. This post looks at how this can be achieved by overriding only two HierarchicalCatalogPartialRouter methods.
When a Url or ContentReference is used in a PropertyList the editor sees this as a ContentReference ID or unfriendly permanent URL. With a little Dojo magic we can use a custom formatter to show the editor a friendly URL!
Customizing the editor UI for a content type is achieved via the UIDescriptor class and this easily covers most scenarios. However, what about if you want available or default views to be restricted based upon a user's roles?
Configuring TinyMCE in Episerver has never been easier, but I recently ran into an edge case when trying to customize it in the context of a PropertyList. This post explores why you can't use the initialization module approach in the scenario and gives a solution.