Upgrade checklist?

Post here for help with installing or upgrading mojoPortal pre-compiled release packages. When posting in this forum, please provide all relevant details. You may also want to review the installation or upgrading documentation.

If you have questions about using the source code or working with mojoPortal in Visual Studio, please post in the Developer forum.

Post here for help with installation of mojoPortal pre-compiled release packages

When posting in this forum, please try to provide as many relevant details as possible. Particularly the following:

  • What operating system were you running when the bug appeared?
  • What database platform is your site using?
  • What version of mojoPortal are you running?
  • What version of .NET do you use?
  • What steps are necessary to reproduce the issue? Compare expected results vs actual results.

You may also want to review the installation or upgrading documentation.

If you have questions about using the source code or working with mojoPortal in Visual Studio, please post in the Developer forum.

This thread is closed to new posts. You must sign in to post in the forums.
12/1/2013 11:57:40 AM
Gravatar
Total Posts 77

Upgrade checklist?

I want to upgrade to 2.4.0.0. so I have been studying the upgrading instructions.

It's probably me, but I find the upgrade instructions a bit hard to follow so I analyzed the text and made a checklist of the steps to take and the sequence in which the steps should be taken. (see below)

I like to do things right the first time so before I upgrade, please let me know if the contents and sequence of my checklist are correct.

Thanks

Ken

=======================

1:Backup the database

2: Backup the files

3: Backup the web.config

4: Check current version ( Admin>System Information)

5: Select upgrade version ( Which .Net version?,  Which database version?)

6: Review release documents (Configuration changes?  Skin changes?)

7: Upload the files in sequence

7.1: Setup folder(check scripts)
7.2: Client script folder
7.3: Data folder
7.4: The rest of the files
7.5: web.config (again)

8: Overwrite your old files

9: Edit web.config (connection strings, SMTP settings, machine key)

10: Open /Setup/Default.aspx

 

12/2/2013 10:39:08 AM
Gravatar
Total Posts 18444

Re: Upgrade checklist?

looks good to me

step 2 should include step 3, so 3 is redundant

step 8 is covered in steps 7, so 8 is redundant

don't really need to edit the smtp settings in Web.config, those are not used, technically some value needs to be there to prevent an error but the values there don't need to be correct because we actually use the smtp settings that should be in user.config and don't need to be touched during upgrades.

12/2/2013 11:14:14 AM
Gravatar
Total Posts 77

Re: Upgrade checklist?

Thanks Joe,

I'll let you know how it goes.
 

Ken

12/3/2013 11:43:01 AM
Gravatar
Total Posts 503
feet planted firmly on the ground

Re: Upgrade checklist?

Just to note that we always edit the httpruntime settings in web.config as well, to permit larger file uploads than the default. Also note that connection strings can be in user.config and so not need updating after the replacement of web.config.

I like to keep an "upgradenotes.config" file in the root folder of every website with the specific upgrade instructions for that site. There can be additional steps like putting back customised copies of resource files for emails etc.

12/3/2013 1:17:56 PM
Gravatar
Total Posts 77

Re: Upgrade checklist?

Crispin,

It would help a lot if you could post an example of your "upgradenotes.config" file.

 Thanks

Ken

12/4/2013 12:38:45 PM
Gravatar
Total Posts 503
feet planted firmly on the ground

Re: Upgrade checklist?

It is similar things to your list Ken, but here's a specific example of what I mentioned about the httpruntime setting in web.config to allow larger uploads:

<httpRuntime requestValidationMode="2.0" maxRequestLength="2097151" maxUrlLength="560" maxQueryStringLength="2048" executionTimeout="3600" />

We have some simple scripts for updating a site from the newly downloaded version (backing up then copying in the new files), and have been considering making them a bit more sophisticated in Python to do the web.config changes etc. However there's always a degree of manual work and checking required when upgrading a site, so we don't mind a few manual operations to complete the upgrade process either.

12/4/2013 2:20:39 PM
Gravatar
Total Posts 77

Re: Upgrade checklist?

Crispin,

The technique that "finally" worked for me was to use a tool called "Beyond Compare" to show the old and new web.configs side by side on a 24" 1920*1200 monitor with the new web.config also open on another 24" monitor in Visual Studio 2012.

Beyond Compare enables a side by side comparison but it uses colors to show the differences between the two files whereas Visual Studio uses colors to show the structure of the file.

Thanks for the explanation & tips.

Ken

You must sign in to post in the forums. This thread is closed to new posts.