Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...DotnetNuke 2.2.1 to newest version and server migrationDotnetNuke 2.2.1 to newest version and server migration
Previous
 
Next
New Post
1/23/2008 4:44 PM
 

I know I am running a real old version.. I was just hired and need to deal with this..

I need to move my old DNN version 2.2.1 website from an older server to a new one. Would it be easier to upgrade to the latest version of DNN before or after I move the website..  I really need help on moving a old DNN 2.2.1 website from server to server. Any help would be great... Even documentation would be great..  Please help me retire this dinosaur.

 
New Post
1/24/2008 7:59 AM
 

>Please help me retire this dinosaur.

actually its not the old dinosaur that one thinks it is - ( it is the fastest of the dnn frameworks) there are still a lot of dnn2 sites out there and there are still a large number of modules available

However to update from dnn2 to dnn3 I would strongly suggest that you do it on the inhouse computer rather then online. When I updated my clients I found that I had to go from dnn2.2.1 to 310 ,335 to 337 this gave me an update with no errors - again however it does not update your users tables  suggest you use non encription on the passwords in the dnn3 web.config.this allows you to manually enter the users into the database or there is a desktop program that will I believe move dnn2 users to dnn3.

If you try to update from dnn2 start to dnn3 then the install can have problems in the sql scripts or at worse not notify you of errors in the scripts and you end up getting errors at inconvierent times after the update. if you have custom dnn2 modules and who has not then you must update them to dnn3 -your skin files will need some minor changes also

ie Inherits="DotNetNuke.UI.Skins.Skin" instead of Inherits="DotNetNuke.Skin" the container files will also need changing

Custom modules can be changed quite simply if you have the code -

if you do this offline then once any errors are corrected you can upload the lot to the new server without any down time.

 

 
New Post
1/24/2008 11:31 AM
 

The person above has many good recommendations.  My KEY recommendation is that you test, test, and re-test the upgrade before you actually do it.

if you can I would take the current site, load it locally do the upgrades and testing, then deploy the upgraded site to the new server. That way the current site is fully functional up until the time you load the new one.

For the actual migration I have a backup and restore guide available on my blog site, linked in my signature.  These guides are geared toward DNN 3.x and 4.x but you can get buy on 2.x as well I believe.


-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...DotnetNuke 2.2.1 to newest version and server migrationDotnetNuke 2.2.1 to newest version and server migration


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out