Converting Page Types

Once your page builder content has been all converted, it's time to go through all your classes and set them up for KX13.

All items in KX12 MVC and KX13 are Content-Only Page Types. When upgrading from KX12 to KX13 MVC, the system looks to see if there is a Url Pattern on the class to determine if it should have the URL feature enabled when upgrading, and also looks at the ClassIsMenuItemType value to see if Page Builder should be enabled.

This conversion will allow you to select which page types should have these features set.

Two Steps

First step will let you go through all the page types to convert. You should look at the page types and determine if they should have a Url or Page Builder enabled (Page builder requires URL feature to be enabled).

Once that's converted, the system checks for any page types without Url Feature enabled that have children below them that have Url Feature enabled. In KX12 (both Portal and MVC with Dynamic Routing), the Url was the NodeAliasPath. However, in KX13, the Url is the combined Node Aliases of all ancestor pages that have URL Feature Enabled. So your URLS for a page can change if one of the ancestor page types no longer has Url enabled. This second screen allows you to set these to Url Feature Enabled just so the url generation still works properly.

Determining Which To Enable

As you look through the classes, if the class should be reachable on the web, the Url Feature should be enabled. If it's only a content item that is used on other pages, then it does not need Url enabled. For Page Builder, if the page should be reachable and there is a possibility of using widgets, then you should enable this.

Note that you can enable Page Builder feature at a later time on any page type with the Url Feature enabled, but you cannot enable Url Feature post-upgrade on a page type that does not have this.