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 ...Interest in an upgrade utility?Interest in an upgrade utility?
Previous
 
Next
New Post
8/11/2011 11:22 AM
 

I am interested to know if the community generally feels there is value in DNN delivering a formal upgrade utility. My interest from this comes from the following thread:

http://www.dotnetnuke.com/Resources/F...

(My plea for an upgrade utility is lost in that thread so I wanted to elevate it here to see if I am a lone voice).

It has been a real pain to upgrade to DNN 6.0 yet the prevailing wisdom from the DNN side seems to be "it's really easy - just copy the files" - followed by a bunch of "oh, but don't forget this. And this. And that...".

As the associated thread has indicated, it is FAR from easy, apart maybe from in "the lab" (as opposed to real world). My own upgrade took a good deal of effort and concluded in a 1 1/4 hour support discussion with a support professional (I have a Professional subscription) which uncovered all sorts of fun things, none of which were unusual or specific to my environment (the "wackiest" would be the use of Ifinity URL Master but even that is pretty common).

I am of the very strong opinion that DNN should deliver a formal upgrade utility with each release that:

  • Verifies the appropriate version is installed for an upgrade
  • Verifies the integrity of the existing installation
  • Checks for installation of custom modules and, at least, provides a warning (for example, IFinity has a version that supports DNN 6.0 - all I needed was a friendly reminder to check and the penny would have dropped). Even better would be some sort of knowledge of upgrade implications for common modules.
  • Downloads the appropriate files (version and Community/Professional)
  • Offers to stop the web service while the upgrade takes place
  • Upgrades in a transactional fashion (any problems mean the upgrade is completely rolled back)
  • Checks the integrity of the upgraded site

I suspect there is much more an upgrade utility can do. But each step above that is not automated is an opportunity for error, human or otherwise. I know!

Frankly, it was surprising and disappointing to me that a product that has been around in various forms for a decade or so doesn't have a mature upgrade utility. It is still more surprising that, despite experiences like my own (I am SURE I am not alone) and multiple issues folks have with upgrades as indicated by forums, the implication remains "it's easy".

So - lone voice?

Mark

 
New Post
8/11/2011 3:22 PM
 
Mark, FYI we've had tackling the install/upgrade on our roadmap for some time - it's been pushed out as there were more important things to work on (e.g. DotNetNuke 6), but I believe it's something we'll be looking at in the next few releases.

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
8/11/2011 3:29 PM
 
cathal connolly wrote:
Mark, FYI we've had tackling the install/upgrade on our roadmap for some time - it's been pushed out as there were more important things to work on (e.g. DotNetNuke 6), but I believe it's something we'll be looking at in the next few releases.

Thank you, Cathal. That's great to know (the fact that it's on the roadmap - not so much that it's getting punted :)). I understand that these are tough choices but it could be argued that the lack of an effective upgrade mechanism is a blocker to folks experiencing the joy of all those more important features :)

BTW, it would be cool if folks could understand that delivering the "it's easy" message to a very frustrated customer is, er, frustrating. And the fact that an upgrade story is on the roadmap, I think, speaks to that. If it truly, truly was as easy as just copying files (as has been suggested by three folks on that other thread) then a) there would be no call for an upgrade utility and b) it presumably wouldn't be on the roadmap.

Thanks again and I hope the feedback is useful.

Mark

 
New Post
8/12/2011 7:14 AM
 
Hello,
the problem is that it really is as easy as overwriting existing files - as long as the user is correctly set up. In support the majority of issues we see with installs/upgrades are
  • permissions related - either the user did not grant modify permissions from the root down, or has not used the right user (particularly if the user does not have modify permissions on the web.config file)
  • database related -the user is attempting to use sql 2000 or a case-sensitive collation to install dotnetnuke
  • 3rd party module related - a 3rd party module makes direct database access rather than using the API so on an upgrade breaks

Now, there are of course core related issues, particularly when theres a lot of change i.e. 4.0, 5.0 and 6.0 have all had teething problems (though 6.0 has been a LOT more stable than previous large releases), which is why certain people will wait of a 01 to upgrade e.g. 6.0.1 .

However, the reason the upgrade item is on the roadmap is because upgrades fail - it doesnt matter that the majority are not "our" (i.e. the core's) fault - users see a failed upgrade and it's our fault anyway, so it's only sensible to try to make it more robust. Our ultimate aim is to support inline upgrades i.e. where you log in and the portal says an uprade is available, you click a button and it downloads, back's up your current site and then upgrades (and if it fails you click a button and it rolls back to the previous version).


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Interest in an upgrade utility?Interest in an upgrade utility?


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