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...To Upgrade Or Not To UpgradeTo Upgrade Or Not To Upgrade
Previous
 
Next
New Post
1/26/2011 1:46 AM
 
There it is again, that flashy red button that reads: "Critical Updates Available" when I login as host. It's the word "Critical": it suggests that we are vulnerable to attacks from evil ... euh... attackers. I want to protect my production site against that, don't I?

I once made that mistake. I then learned that some professionals happily run their sites on 04.09.05 in spite of all the critical updates since. Of course, I had to venture into DNN 5, to keep up-to-date with the ML features. But if it were me, I'd have stuck with DNN 05.04.04 for production. "I would have...": then came the scare about the vulnerability in the core of ASP and were suggested that an update to 05.05.00 would provide temporary protection. We all know now it didn't but there's no rolling back without losing information.

So I moved up. Because of Issues, I moved the production site up to 05.05.01 and then to 05.06.00 - and now, if tests run well to 05.06.01. For what I foresee, in another month or so, I might be moving it up to 05.06.02 if that solves the bug in the static text translation page. I envy those sites that live in rest and peace with 04.09.05.

I think I misunderstand the word "Critical", but then, so will many users do. "Critical" makes alarm bells go off.

Good thing: I don't login with the host account that often, and now I will do so even less.

____________________________________
The one-eyed in the land of the blind.
 
New Post
1/26/2011 4:19 AM
 
It is only "Critical" if you upgrade!

Understand your point. DotNetNuke is unfortunately not always stable in the latest version and it feels sad that all updates are critical when a month later is equally critical to be left in.

I've been through websites that completely lost vital parts of the functionality when upgrading and it is difficult to predict it before. Like pages that do not move right, etc.. Imagine a company with 2-3 hundred pages that begin to live her own life! No no ... the customer is not happy. Or that Google Analytics stopped working in a fairly new version. Luckily I had already tired to upgrade.

Think that it is important to DotNetNuke to makes stable and professional versions. So we can stop at a longer time. And in between can new versions be released, that focus on new features to re-collect up to a really stable version that can be a long while. Thinking a bit about how Ubuntu (www.ubuntu.com) works with its long-term versions.
 
New Post
1/26/2011 4:33 AM
 
I have a client that is still quite happy running an old version of dnn before the dawn of time.  His site does what he wants and he sees no reason to move any further forward.

However, having said if one day he does decide to move forward he has now left it so long that I would dread to think of the nightmares moving the site forward would cause.

I guess it becomes each to their own.

Westa
 
New Post
1/27/2011 6:14 AM
 
We happily run our client's sites on 4.9.5, which is still a very stable and secure version with few issues. I contributed a number of items to the DNN issue tracker for DNN 5, but so far, there are still to significant bugs for us to move our clients to latest version (although DNN developers are working hard on it). Due to the DNN upgrade mechanism, I don't expect upgrading 4.9.5 to latest version will be more difficult than upgrading over time to each minor version.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
1/27/2011 9:40 AM
 
Tobias Wiklund wrote:
It is only "Critical" if you upgrade! .

Some semantics from time to time doesn't hurt. Would "Stabilization Upgrade" not be more appropriate for this kind of delivery?

Correct me if I'm wrong: Is the qualification "Critical" not connected to security vulnerability loopholes being closed? In daily use, the word has a whole array of meanings,  The meaning that I constructed around the word in IT language is mostly derived from Microsoft's use in its critical updates.


____________________________________
The one-eyed in the land of the blind.
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...To Upgrade Or Not To UpgradeTo Upgrade Or Not To 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