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...Upgrade option - make copy and then do it?Upgrade option - make copy and then do it?
Previous
 
Next
New Post
5/16/2011 9:59 PM
 
Got a site running DNN 4.04 and want to move it to the latest.

Can I copy the site to a sub folder, do all of the updates between 4.04 and the latest - and then fix all the modules, the script, the styles etc. When it's perfect I plan to re-point the index page to the sub-folder (and the new site).

This crazy?

Got another idea?

thanks
 
New Post
5/17/2011 1:12 AM
 
I would set it up in another environment first, a test domain, a local website, something that functions more like your production site, than a subfolder.

You should check out the Upgrade steps in the Wiki (under the resources tab here)

Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions
 
New Post
5/17/2011 9:36 PM
 
Hmm, not sure I follow why a subfolder is a bad idea. Can you explain that a little more?

Other info - I'm on a mac. So, a local site in Windows 7 thru VMWare will be heavier than I really want :)

thanks, len
 
New Post
5/22/2011 10:29 PM
 
An upgrade happens in 2 steps:

1. You copy the new files over the old ones. That could happen in a subfolder.

2. DNN discovers a new version and makes changes to the database.



So, besides another folder, you would also need a copy of your database.



If you want to test an upgrade, you would want a setup that resembles your live site as closely as possible.Although I have locally a number od DNN instances running under (localhost), I always test upgrades under the URL of my hostin portal, after having redirected the IP to the loopback IP (127.0.0.1) in the %windir%\system32\drivers/etc/hosts file on a local copy of the life website.



Since you cannot do that on your mac, copying all files to a sub folder might work as a way to backup your file system. But you will also need to backup your database (and make sure you can restore before you start the test, sometimes DB owners do not have restore permission).



When you are sure of your backup/restore procedures, make the upgrade without the testing. If anything goes wrong, putting back the file system and restoring the database should get you out of trouble.


____________________________________
The one-eyed in the land of the blind.
 
New Post
5/24/2011 5:46 AM
 
We use next steps usually:
1. Clone site folder to another folder and configure it in web server
2. Clone db to another one db
3. Change connection string in web.config (for clone) to newly created database
4. Process with upgrade on cloned website

Please notice that steps 1-3 can be automated with Papayas SiteBackup module and step 4 with Papayas DnnAutoUpgrade.

Papayas DnnAutoUpgrade - automatic DotNetNuke upgrade without any problems!
www.papayasdnn.com
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Upgrade option - make copy and then do it?Upgrade option - make copy and then do it?


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