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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...How to upgrade to New VersionHow to upgrade to New Version
Previous
 
Next
New Post
1/29/2008 7:59 AM
 

Hai Guys

I have used DNN3.3.7 in my webiste. I need to upgrade it to new DNN version. How can I do it while my site is in Live? Could you please explain?

 
New Post
1/29/2008 9:55 AM
 

You can't do it live, but depending on your site it may not be down long.  You can use an app_offline.htm file to respond to requests while doing the upgrade.

Jeff

 
New Post
1/30/2008 9:00 PM
 

I'm fairly new at this but here is what got me through my first two upgrades (4.6.2 - 4.7 - 4.8) successfully - http://www.deutschnetnuke.de/AboutDotnetNuke/V3V4TippsTricks/Upgradedurchführen/tabid/186/language/en-US/Default.aspx

If you keep track of files you have made custom changes to (usually .css and the skin .ascx files), you can prep the new file set not only with the new web.config but the changes to the other files.  Double and triple check that everything is good and you can:

1.  Pull the site up in a browser.
2.  Stop web services.
3.  Copy the new file set into the dnn root folder on the web server.
4.  Start web services.
5.  Jump to the browser, refresh and watch dnn upgrade.

If you have customized module templates or anything beyond simple skinning and design, it's safer to make the same changes to the new file rather than copy the old one with the change into the new file set.

I've successfully upgraded twice with only 1-2 minutes of downtime using this method.  Don't forget to practice on a test site and have a db/file backup ready to restore should something go wrong.  After every upgrade, check everything out.  Both times I upgraded, I have had a some manual and unexpected fixes to apply to modules and they needed to be applied to each deployed module one-by-one which added a few minutes ot hunt down the solution plus 20-30 minutes to go from page to page and apply the changes.

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...How to upgrade to New VersionHow to upgrade to New Version


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