setting autoupgrade to false prevents users to get displayed the upgrade wizard, it is useful, if you don't have the option to disable access for a busy site while upgrading it. I usually prefer to clone the site (and database) for major upgrades, apply the upgrade to the clone, test the site to be fully functional and switch domain address to the clone. However, if you don't have this option, disabling autoupgrade and using app_offline.htm while uploading files would be the best solution.

---

Cheers from Germany,
Sebastian Leupold

   

Speed up your DNN Websites with TurboDNN

Thanks very much, Michael Tobisch and Sebastien Leupold, for confirming that the upgrade instructions in the wiki contain items that aren't as hard requirements as they look.  I fully agree that a test site is the only way to test upgrades in DNN.  I greatly appreciate the warning about the host login prompt with v.6 - if the current upgrade works, my next round will be 5.6.8 to 6.2.8.  I hope I don't have to bother you again but one never knows.

---

hedera
**********
Nature bats last.

The upgrade from 5.6.3 to 5.6.8 to 6.2.8 went reasonably smoothly except for two things, one of which we'll live with:

The Gallery module, upgraded to latest (but dead) 4.4.0, simply doesn't display properly.  I've tried to make it "admin only" but I don't see the warning flag on it.  We've agreed we'll live without it for now.

When I ran the wizard to upgrade the production site to 6.2.8, I wasn't prompted for a login.  I was prompted when I upgraded the test site.  The wizard says it ran without error and the site looks good and says it's running 6.2.8.  Should I worry about this?  I had been using a manual "site maintenance" site with autoupgrade="false".

---

hedera
**********
Nature bats last.