-
Notifications
You must be signed in to change notification settings - Fork 2
Upgrade Procedure
Trevor Fayas edited this page Aug 31, 2022
·
10 revisions
Upgrading a Kentico site is best done with "Base" Kentico applications. The Kentico Installation Manager will not upgrade a site if it's not a WebApp, and having custom code and modules runs the risk of errors during upgrade.
Likewise, after upgrade, it's best to also start with a fresh Kentico 13 installation to avoid issues with post-upgrade processing and such.
- Use the Kentico 12 Installer to install a Kentico Xperience 12 MVC Site with a database (you can use localdb)
- Hotfix that new site to the hotfix that matches the version your site is on.
- Replace the Connection string and CMSHashSalt values in the web.config with your site's settings
- Point your IIS to the fresh kentico site CMS folder
- Run your site (should run)
- Run the Kentico Xperience 13 Installation Manager
- Register your site (pointing to the Base Kentico Solution)
- Upgrade the site to Version 13 (back up site and database)
- Use the Kentico 13 Installer to install a Kentico Xperience 13 Solution (no database needed this time)
- Copy your connection string and CMSHashSalt over to this new Base Kentico Xperience 13 Solution
- Set the SQL COnnection timeout to a very high number (60000) so no sql timeouts during first-run upgrade operations
- Set the Compliation Debug = true so there are no request timeouts during first-run upgrade operations
- Point your IIS to the new base solution
- Run the site (this may take a while)
- Register your Kentico 13 Installation Manager to the new Base 13 Solution that you just ran.
- Run the Hotfix on it and hotfix to either the latest version (if using the HBS KX13 Baseline, may want to hotfix to it's latest hotfix version, then once set up hotfix the entire solution again). Be sure to backup site and database during this.
- Run the admin once more.
At this point, you have a base Kentico Xperience 13 Admin WebApp, and you can start slowly adding in your customizations, making sure they are compatible as you go.
You should use the base MVC Site, or the Baseline, and start building your site.
Introduction
- Tips & Tricks
-
General Processes
- Cleaning up Site Prior to Split
- Cleaning up Site After Split (Workflow/Page Types)
- Go through Template Configuration
- Go through Section Configuration
- Go through Widget Configurations
- Checking Conversions
- Converting Page Types
- Converting Forms
- Final Database operations
- Preserving Navigation Redirects
- Upgrade Procedure