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...Support for pre-live staging area for content updatesSupport for pre-live staging area for content updates
Previous
 
Next
New Post
1/4/2009 9:26 AM
 

 The way that we handle it is that we have two different servers that are running PowerDNN.com .  One of them is live, and one of them is where we make all our changes.  Once we have the development version of our website where we want it, we "clone" the website from our development server onto our live server.  This works really good for us since it allows us to do module installs and major content updates without all the headaches of managing different editor permissions.  Also, we don't have to be worried about nuking the live site.

 

 
New Post
1/4/2009 12:48 PM
 

Timo Breumelhof wrote

Workflow is on the roadmap.

A workaround would be to copy the page, deny acccess to "normal" users.

Then after editing delete the original page and allow access to the edited one.

Not ideal but it works if it's for a few pages.

This works unless the page is linked to internally or externally, since creating a new page changes the tabid and hence breaks any links linking to the "old" page.

 
New Post
1/4/2009 4:07 PM
 

Tony Valenti wrote

Once we have the development version of our website where we want it, we "clone" the website from our development server onto our live server.  This works really good for us since it allows us to do module installs and major content updates without all the headaches of managing different editor permissions.  Also, we don't have to be worried about nuking the live site.

 

 

What form does the "cloning" from dev->live take - are you talking about files only, rather than DB tables? If you clone the database you'll presumably overwrite user data as well as metadata??

 
New Post
1/4/2009 5:58 PM
 

For PowerDNN.com, we do a complete backup and restore of the website and database since we don't ahve to worry about preserving user data.  On some of our other sites, we do an Import, then a backup and restore where we import specific "live" data from the production environment right before we do the backup.  We do this on a table-by-table basis and have written code that helps with doing the imports.

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Support for pre-live staging area for content updatesSupport for pre-live staging area for content updates


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