Upgrading Steps for DotNetNuke from DNN 4.x.x to DNN 6.x.x

image

Specifically we wanted to take a version of DotNetNuke from 4.9.1 to 6.1.3 today and actually found that it worked perfectly.

We did take some steps that helped a lot. This may be of value to some of you.

Before we Began

1. Backed up the entire file system for the website.

2. Backed up the database on SQL server for the site in question.

3. Ensured we had a HOST login account that worked.

4. Ensured the server we were running on (Windows 2008 R2) was patched and running .Net Framework version 3.5 SP1.

5. If your site is busy, work out a way to stop the traffic. One way is to add a portal alias, like test.domain.com in your DNN website. Setup a DNS entry to that test.domain.com points to the IP address of your DNN web server. In IIS, setup a Binding, so that test.domain.com will answer for your site.

Then access the site on test.domain.com and check you can login, etc.

Then remove the binding in IIS for www.domain.com (temporarily while you play upgrade).

This way, the site will not answer normal user access, but will answer you when you go to test.domain.com.

 

Update Path

We suggest the following table for upgrading your DNN Website.

Note: If you are upgrading a version prior to DNN 4.6.2, then you will need to manually update the web.config file. After this version the updates are automatic.

 

Steps On Upgrade

On Codeplex, Click on View All Downloads

image

Find the version for the next upgrade step from the table above. Then find the Version Upgrade download link.

image

Download the .zip file to your server. Then extract the contents directly over the existing website directory structure.

You will be asked to overwrite files, Tick yes to all.

You will be asked to overwrite folders, Tick Apply to all – And continue.

Once you have extracted, hit your website in a browser, and watch the upgrade happen before your eyes.

Repeat the steps of backing up after each successful update, and download the next update package and repeat the process.

 

Tricky Bits

If you are using the XML module, on a DNN version before 5.3.0, then you should obtain the latest update of the module before moving past 5.3.0.

If you have the Ifinity URL Master module. We suggest turning it off to upgrade.

 

After Upgrade

In IIS you will wan to move the website to a new application pool that is running .net 3.5 or 4.0 Integrated. You cannot share application pools with earlier DNN versions that run on .net 2.0.

Jump into the HOST settings, and configure things like, friendly URL’s, DNN Host Menu Options, and performance settings.

If you disabled bindings (from the initial steps 5 above) re-enable them and test access.

 

DotNetNuke Upgrade Service and Support

We offer a DotNetNuke Support Service that can include the upgrading of DNN websites for you. This is especially useful if you are not confident with either .net websites or IIS server administration.

We are happy to help you evaluate the upgrade path and potential problems. The cost of the service is in effect calculated at at an hourly estimate. It should be noted that if everything goes well, and trouble free, there there is at least 1 hours work in this upgrade, usually more as there are often little bugs to sort out.

Please contact us for support here: http://www.interactivewebs.com/Services/DotNetNukeSupport.aspx

Additional References

http://www.datasprings.com/resources/articles-information/dotnetnuke-articles/upgrading-dotnetnuke-4.9-to-dotnetnuke-6.0

Problem Upgrading for DNN 4.9.5 to DotNetNuke 6x

During an update from DNN 4.9.5 to DNN 6x we experienced:

All pages with HTML blank when logged out, but show this error logged in.

image

Error: Services is currently unavailable.DotNetNuke.Services.Exceptions.ModuleLoadException: The type initializer for ‘DotNetNuke.Modules.Html.DataProvider’ threw an exception. —> System.TypeInitializationException: The type initializer for ‘DotNetNuke.Modules.Html.DataProvider’ threw an exception. —> System.InvalidCastException: Unable to cast object of type ‘DotNetNuke.Modules.HTML.SqlDataProvider’ to type ‘DotNetNuke.Modules.Html.DataProvider’. at DotNetNuke.Modules.Html.DataProvider.CreateProvider() — End of inner exception stack trace — at DotNetNuke.Modules.Html.WorkflowStateController.GetWorkflows(Int32 PortalID) at DotNetNuke.Modules.Html.HtmlTextController.GetWorkflow(Int32 ModuleId, Int32 TabId, Int32 PortalId) at DotNetNuke.Modules.Html.HtmlModule.OnInit(EventArgs e) — End of inner exception stack trace —

Solution

In our case, the upgrade left 2 things behind that DNN 6 did not like.

  1. in the app_code directory, we deleted the ‘HTML’ folder (since it does not seem that it was in use anymore and was potentially conflicting with new html module code)
  2. in web.config, I removed the following line in the <Codesubdirectories> section
    <add directoryName="HTML" />

Save and you are done.

Setting Mushroom Lite Template for DNN 6x Default Skin

DotNetNuke 6x has a great looking default skin called DarkKnight, and the skin design has previously caused some layout issues with the Mushroom Light Module Templates.

To correct this, we have created two new templates that are designed specifically to work with the DarkKnight skin in DotNetNuke.

Called:

  • DarkKnight-Small
  • DarkKnight-Large

They produce the following results…

image

With the Large template being the content on the left, and the bottom right showing the content of the small template.

This makes the module perfect for use with DotNetNuke 6x our of the box.

 

How to Set the Templates

The templates are selected through the normal RSS Template Tab in the module.

1. Select Load Template Button

image

2. Select the appropriate template and press the select button.

image

That will load the new templates and be ready to use on your site.

Activity Email Updated to DotNetNuke 6x

image

Today we are please to announce that the Activity Emailer Module for DotNetNuke, will support and run on DNN 6x.

This single package will now run on all DNN versions from 04.05.05 and later, including DNN 5x (all versions) and DNN 6x.

 

To Understand the Module

To understand the best use for this module, it is necessary to understand the type of situation it was designed for…

Any business that has a membership database, for example a gym, club or association, church etc. Who currently have an in office database of membership details, and want to run a website that allows members to update their details online, will need a way to have the databases linked from the website back to the membership database in the office.

In many cases we develop custom modules that feed and sync data to a “backend database” to meet specific needs. However sometimes clients simply cannot afford the expense of a customized application that links membership databases.

This module is the cost effective solution. This module sends a simple email to a configured email address with a list of the changes that members who have logged into their website have made. This email can then manually be entered into the “backend database” by staff in the office.

Example

  • A local gym with 500 members has a database to manage membership and billing information in the office.

  • The office database is proprietary software and although a connection module is possible, the cost of development is prohibitive.

  • Membership details are exported from the office to the web.

  • Members of the gym are encouraged via promotions etc. to keep their details up to date on the login area of the gyms DNN website.

DotNetNuke 6 Gets Image Module

We have updated our popular Mushroom Image module that feeds image sources into a template engine that allows some fantastic effects on pages.

The module is now ready for use on DotNetNuke 6x versions, and can be seen here:

http://www.interactivewebs.com/mushroom-image/Demo/LightBoxEffect.aspx

pulling feeds directly from Flickr in this instance. Use the Demo menu to see other examples.

DotNetNuke 6 Gets Blog Module

We have updated our popular Mushroom Lite module that is used to integrate WordPress blogs module into DotNetNuke.

The module is now ready for use on DotNetNuke 6x versions, and can be seen here:

http://www.interactivewebs.com/mushroom-lite/Demo/MushroomLiteDemo.aspx

pulling feeds directly from our blog here: http://www.interactivewebs.com/blog/

DNN Word Editor Ready for DotNetNuke 06.00.00

image

Today we released a version of Word Editor that is ready and tested on DotNetNuke 06.00.00 release.

The popular Word Editor module allows users to edit the content of HTML on a DotNetNuke website using Microsoft Word 2007 or later.

If you have not seen the module, check out the website here:

http://www.interactivewebs.com/dnnwordeditor/AboutDNNWordEditor.aspx

Or the online demo here: http://demo.interactivewebs.com.au/dnnwordeditor_demo/dnnwordeditor_demo.htm