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 create a stage enviroment for upgradeHow to create a stage enviroment for upgrade
Previous
 
Next
New Post
11/6/2012 4:53 PM
 

We are looking at upgrading website to newest version of DNN.  The current website is running DNN 5.6 and work will continue on the live website.  Since the site has lots of pages and editors we can stop creating new things on the current site when the framework is being setup on the stage site.
We are creating new skins for the newer version of DNN on the stage because we are going to have a different layout but a lot of the lower level content items will need to be moved over to the stage once and then again right before going live since work will continue on the live site for a month or two before the new site can be finished.  What is the best solution in doing this or plan of attack?  I have been racking my brain on trying to figure out what makes the most sense with out to much loss of production on the main site.

 
New Post
11/6/2012 9:48 PM
 

I would create a copy of the live System on a local or virtual Maschine. Running the Upgrades, implementing the new design and running tests.

For this you need a copy of all files and a database backup of the live System to Transfer this to the test System. You have to add the URL for the test System to the alternate URL mapping into the DNN site management.

After success upgrade and testing you can also backup the database and files to restore this on the production environment.

Hope this helps you!

 
New Post
11/7/2012 10:49 AM
 
Thanks for the responses.  I guess the issue I am having is how do I work on the new copy and merge it back into the live site?  I have setup many test sites with the process you describe but that is more for functionality testing and we did not care so much about the actual data.  Since we have so many document level edits going on not sure how to match the two up again since this process I could see it taking a month or two to get all the content and structure setup for the new site.  Do you understand the disconnect I am worried about.
 
New Post
11/8/2012 7:33 AM
 

All of the content in the database in uniquely and integrally linked together ... as such it is a complex prospect to remerge the contents of two separate databases.

The community edition of dnn does not include any features that allow data from different copies of a site to be merged.  You could possibly look at merging the data yourself - but you would need to do so very carefully.

The thing to understand however is that say for example you have two copies of dnn - and you add a page to each - with different content - you now have a serious mismatch - because the site links elements together by tabid - and each version of the site would have different page content assigned to potentially the same tabid.

The same goes for moduleid's and module content - on page 1 you add a text module -  on page 2 you add two text modules  =  the text modules have unique id's that are uniquely related to that copy of the site.  so if you then ad a page to copy two of dnn and put two text modules on the page - then again you would be in all sots of trouble trying to merge the two copies 

Westa

 
New Post
11/13/2012 11:30 AM
 

 Westa, I agrees with what you have said above and that is what I am worried how I am going to get this done.  It has us in such a funny place where I thought once we have information in a database upgrades would not be so hard but that is not the case. I guess in this case major upgrades since we are looking at structure changes. 

Does a higher version of DNN have true Stage Environment? I thought Enterprise was just for content modules.  I did more thinking and wondering if I just upgrade the current site and create a new portal to start fresh with new skins and structure? Once that is done then I could create a script to upgrade the documents from the old site to the new one by just updated portalID in the correct places?  I will have to look at this in more detail and still wondering what anyone else has done before.

Chris

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...How to create a stage enviroment for upgradeHow to create a stage enviroment for upgrade


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