Migrate from Kooboo CMS 2.0 to 3.0
Applications in V2 has been renamed into Sites. Each sites can manage its own layout, content display template, script, theme, page, label and file management. In V3, there are some new features like robot.txt, URL redirects publishing queue and system disgnosis.
Besides the development improvement, in V3, the content repository has been saparated from the sites. We will explain the difference below.
Content repository is now independent from Sites. One content repository can belongs to multiple websites. When creating a new website, you are allowed to use an existing content database by inputing the name of that database or create a new one. The content inheritance concept has been replaced by content broadcasting. You can enable the content broadcasting feature under database settings. When enabled, you will be able to define content broadcasting sending and receiving rules to send content to or receive content from other websites.
The Text schema from V2 has been renamed to: Content type. We do not have binary schema any more. If needed, we have a new media library to store multi media files or you can store binary files in a text content.
In V3, all the content management pages are template based which means that you are able to modify the content list page, conent edit page or the category selection windows yourself. You can enable this "Custom Template" feature in the Database setting and change them in the content type editing screen.
Unfortunately, there is not a migration tool, you have to do this database migration manually.
Layout and content display template
The following names has been changed from V2 to V3.
Layout template = Layout
Content template = View
Text resource = Label
The template syntax has been changed into MVC styles and arranged under two main classes: Url.FrontUrl() and Html.FrontHtml(). Label syntax has been simplified to like: "textstring".label().
In the V3, we keep the ASP.NET webform syntax and add the new Razor view engine. Some helpers have been provided to make the template coding much easier. You can always find help in the right sidebar of layout or view template editing screen, includes data rule designer and code helpers to most of important APIs like Html meta, layout position tag, etc.
To migrate, rewrite layout template to layout, content template to view and text resource to lable. You can change kooboo API to newer API and keep major part of your existing templates
It has very simliar concept like in the V2, you can configure the page by inserting widgets into predefined position and assign their parameters. You can now insert more than just content template or module into a position, you can directly query content from data folder or insert reuseable static html blocks.
A visual sitemap view of pages has been added, the sitemap is an easy access to all the page available operations.
Extensions must be rebuilted under new Visual Studio extension development template. Many of the APIs have been changed, it has to be rebuilt before it can be used in the Kooboo new version.