The frequent release cycles of mojoPortal ensure that users have access to the latest improvements implemented by the mojoPortal development team. It’s always a good idea to work with the latest version of your CMS, in order to leverage the best support and features. However, upgrades can also present unexpected issues, and some can be real show-stoppers, especially in the case of customized mojoPortal implementations. Here are some tips on how to upgrade your mojoPortal site without losing downtime due to unexpected incompatibilities.
The first thing to do is to make sure you’ve got the same version of database engine on your local machine as you’ve been leveraging on your hosting server – if your hosting provider is running MSSQL 2008, for instance, make sure you’re running the same version on your local testing environment, right down to the release version – you’ll see more on why that’s important shortly.
We’ll go on the assumptions that
- you tested your mojoPortal implementation locally before you launched it live
- you still have that development environment available
- it’s the same version as the live site you currently have
Now – let’s proceed to get a backup copy of your live site database. This step will vary, depending on which database engine you’re using (mojoPortal supports MSSQL, MySQL, SQL CE, and several others); once you’ve got your backup database, restore it to your local database instance, and make sure your local mojoPortal instance is pointing to it.
From here in, we’ll presume that you’re using Visual Studio to access your local instance (if you’re using a different IDE, leave a note in the comments, and I’ll cover that in a future post).
- Press F5, and allow your local instance of mojoPortal to start up; make sure that you’re seeing the content from the live site, to confirm that you’re working with the right database.
- Now, stop your local instance, and download the latest version of mojoPortal that you intend to install.
- Extract the download from the .zip file, and leave that folder open.
- Right-click the solution in your Visual Studio pane, and select “Open Folder in Windows Explorer”
- Close Visual Studio
- If your database settings aren’t in user.config, make a backup copy of your web.config file, so you don’t lose your configuration information
- Select all the contents of the extracted folder, right-click, and select “Copy”
- Navigate to the folder of your existing mojoPortal instance, find an area without a file, right-click, and select “Paste”
- Allow all files to be overwritten
- If you’re not using user.config, re-enter your database connection string into the web.config folder – do not use the old web.config file, as many things tend to change between versions
- Re-open your Visual Studio project, and refresh files.
- Press F5, and allow mojoPortal setup to run through the updates.
At this point, if the automatic updates ran without any errors, you can navigate to the home page of your site.
We’ll take a coffee break here, and pick up in Part 2, where we’ll review areas commonly in need of attention after an upgrade, and how to implement your updates on the live site.