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

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Suspending site during upgradeSuspending site during upgrade
Previous
 
Next
New Post
7/8/2006 5:13 PM
 

Good point, although it's a standard best practice it's still really important to emphasize backing up before performing the procedure.  In addition, another important best practice is testing on another copy of your installation first as well --- especially if you have a complicated and/or mission-critical installation.



Shane Miller
Call Centers 24x7
 
New Post
7/8/2006 5:26 PM
 
Agreed. Backups are essential - regardless of the upgrade method you choose. Also, it takes me all of 5 minutes to upgrade so deleting web.config and taking the site down for that short period of time works fine for me, but depending on your requirements you may want to take the re-route option.
 
New Post
7/8/2006 6:31 PM
 

Those are all valid and good ideas but require access to IIS or the ability to create 2 DB's etc. On a standard hosting account you are often limited to a single SQL DB and no IIS access. Another problem is that you may have several domain names point to your installation and so the rename DNS etc. could take some time to do.

I am surprised that the ability to lock a site down is not available from the Host account. Lock down for maintenance. Also, when kicking off the .../Install/Install.aspx command you should be required to enter the host username and password - or at least you should be able to configure the web.config file such that this is a requirement. While the site was locked down the host account should be able to enter the site and check to see how the upgrade went before unlocking the site(s).


ver 4.3.1 (to 8 July 2006) ver 4.3.2 (to 20 July 2006) ver 4.3.3 (to 5 Aug 2006) ver 4.3.4 (to 20 Sep 2006) ver 4.3.5 (to 25 Dec 2006) ver 4.4.0 (to date)
 
New Post
7/8/2006 9:50 PM
 
I, too, would love to see some sort of lockdown capability.  I'd like to see the ability to temporarily deny access (optionally, with a configurable message) to selected roles, and for selected portals. 


Shane Miller
Call Centers 24x7
 
New Post
7/9/2006 8:11 AM
 
I like the delete web.config idea -- also combine that with setting up your IIS error pages to produce a nice error message. That should solve the problem of people trying to hit specific pages.

However, one of my last shared host upgrades failed, and it took me about 4 hours to delete and upload my entire site using residential cable modem. That's a lot of downtime if you have nowhere to redirect to.

Seems Microsoft should have thought of a better way to do this. This is more specific to .NET apps than anything -- letting a user go on your website in his own session space while you update. DNN has a pretty good upgrade system actually, but I'd welcome improvements.

Jason Honingford - Web & Software Developer
www.PortVista.com
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Suspending site during upgradeSuspending site during 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