Quick question...
Can the same process to upgrade DNN 3.1.1 to 3.3.5 be used based on your tutorial Upgrading 3.x to 3.2?

This is because i've noticed on DotNetNuke.com they now have an DNN 3.3.5 Install and a DNN 3.3.5 Upgrade folder.

Which do i use? - i'm going to take a gues and use the upgrade folder and watch your tutorial.

And is it best to do this on my local box as a test? Or does DNN treat domain URLs  differently verses localhost URLs.

Just curious what your findings are.

 

 

Hello,

Yes it is the same process.

If you use the upgrade folder it upgrades your DNN installation
If you use the Install folder it also installs the latest DNN modules

I would use the upgrade folder first to test everything is working correctly and then if it is you can update which modules you require afterwards.

I would test this out on localhost first - it is the same process as doing it live

Before doing it live make sure you backup everything.

I've tested the process upgrading from 3.1 right through to 4.3.x and it works with a clean 3.1 installation. - But I tested it on DNN Creative (by downloading the site to my laptop and testing it as a localhost installation) which is v3.2 upgrading to 4.3.5 and it failed due to some of the modules on the site.

(Upgrading to v4.x you need to enable asp.net 2.0)

So you definitely need to test before you go for this upgrade.

(It sometimes helps to cross your fingers and do a voodoo dance as well ;-) )

Good luck

Cheers,

Lee

Ok... i'll give this a try on my local... and keep my fingers crossed.

Thanks so much for the encouragement. Yes i agree on testing and backing up first. There's nothing worse than having the ol' Microsoft mindset of just saying "Ship It" before testing - LOL

Quick Question... When you say


Please excuse my lack of knowledge but How specifically do i do that? The site i'm trying to upgrade has a lot of modules built for 3.x and up. Which were installed initially in version 3.1.1

What is that process for updating the modules as well? Again forgive me for my lack of knowledge on the steps to updating the module specifically. Is it as simple as cross checking the web.config? Or is there a process i need to initiate?

When I upgraded from 3.1.11 to 3.3.5 There were some modules that needed to be upgraded. Specific ones we needed to upgrade was Active Forums. We use quite a few different modules (core, open source, commercial), and Active Foums, was the only one that gave us problems. Though was a simple download from their site, and uploading of the new (fixed) PA again.

I would make a list of modules, and vendors, and check their sites for any reported problems with using DNN 3.3.5 There was a big change in registration, and user profile section from DNN 3.1.11 to 3.5.5.

Good luck!!

 

Hello,

Upgrading the core modules, if you open the Install zip file, go to the install / module folder

In there you will see zip files of the latest versions of the core modules.

All you have to do is upload them and install them as you would with any other module and they will automatically upgrade the old version.

You need to be careful with the new documents module and File Manager as some people have reported problems when upgrading. - But I didn't have this problem, so it all depends on your own setup.

Good luck,