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

HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...How to Upgrade DotNetNukeHow to Upgrade DotNetNuke
Previous
 
Next
New Post
10/11/2011 7:41 PM
 
Holy Crap! What a list! Umm, can I pay someone to do this? I would so break something. How much would I be charged for this? Do you know anyone who would do this?

Yikes! I had an old client come back from the dead, with his DotNetNuke site that I built in 2006 in Version 04.03.04.

It's hosted at GoDaddy.

He asked me to make some changes, it acted wonky and then I saw a big red button in the Host Settings page that read "Critical Updates Available."

This is the site: http://www.matthews-hanna.com

I took a screenshot of the host settings, but having trouble uploading it here. The image manager in this editor won't let me upload from my computer. Ugh.

HELP! (Maiden in distress ;)
 
New Post
3/19/2012 9:02 AM
 
Question about upgrade path:

Assume you have 2 identical DNN sites set up separately. The first site, Site1, is upgraded using upgrade path described in the DNN Wiki and working. Now, since the filesystem of Site1 should up upgraded now, would it work to just replace all files at the second site, Site2, with the files from Site1, and then just execute an upgrade to upgrade the database?

 We have tried this on a few of our testsites, and so far the result hasn't been all that great at all, besides all SQL scripts executing without any errors (at least none that DNN detects). If it is not possible to do like this, why not?

 

 
New Post
3/20/2012 6:37 AM
 
unless you are running a web farm, you should upgrade each site individually.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
3/20/2012 7:51 AM
 
Sebastian Leupold wrote:
unless you are running a web farm, you should upgrade each site individually.

 Could you please elaborate a bit on why this is the case? Ie what actions are not performed if you point and updated website to a not upgraded database? 

 
New Post
3/20/2012 9:11 AM
 
upgrade does also modify some of the files (like web.config) in sync ith database settings, which will not be in sync, if you copy over files from the upgraded site.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...How to Upgrade DotNetNukeHow to Upgrade DotNetNuke


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