Supporting wildcard routes in EPiServer 7 CMS
Unfortunately EPiServer does not support wildcard routes out of the box. Luckily it is not too hard to implement it using the ISegment interface.
Simply.io
Route constraint for Content Type in EPiServer CMS 7
When registering new ASP.NET MVC routes with EPiServer CMS you want the URL segment to be dynamic. To do that you add the {node} segment in the route URL. The node segment represents the full path to your page, e.g. “/Lorem-Products/Ipsum-Dolor/”.
How to get Content Type from PageData or ContentData in EPiServer CMS 7
There are times when you need to get the ID of a Content Type (Page Type) in EPiServer CMS. If you are used to developing with PageTypeBuilder you know that you can use the PageTypeResolver.Instance.GetPageTypeID method to get the Page Type ID. In EPiServer CMS 7 this of course does not exist. …
“Key has already been added” exception with PageTypeBuilder
This is one of those exceptions you get and you know you have had them before but never remember the solution, and googling them doesn’t give you any answers. Time to fix that! Background I was in the process of creating lots of new page-types for a new EPiServer website and suddenly it …
Faking Dynamic Properties with PageTypeBuilder in EPiServer
When building websites in EPiServer you sometimes want a value of a property to be inherited from the parent page. Previously we used Dynamic Properties to have properties inherited, but when using PageTypeBuilder we are spolied with being able to code all our page type properties programactially …