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...Why is DotNetNuke giving itself a black eyeWhy is DotNetNuke giving itself a black eye
Previous
 
Next
New Post
8/17/2008 2:36 PM
 

Andrew,
That is the new DotNetNuke 5.0 skin in all its glory.  :)  It is sooo beautiful, don't you think?

I really hope that Joe is right about there being a lot of stuff happening in the background.  We were looking over release dates yesterday and in over a year, DotNetNuke has gone from version 4.3.x to version 4.8.x.  Apart from lots and lots and lots of bug fixes, I can't think of a major feature that has been added in the past year.  And, when you've played with the 5.0 betas, it is really hard to get excited about a new skin, "Deny" permissions, and "a whole lot of behind the scene changes."

Have any of you compared DotNetNuke to Joomla (community target product) or Alfresco (enterprise targeted product)?  DotNetNuke is clearly much more flexible than either of them, but its loosing mindshare.  A year ago, DotNetNuke was perceived as a vibrant, cutting edge technology.  I'm not sure that's the case anymore.  In the past year, Alfresco has become a serious enterprise player with a large number of large scale, corporate accounts under their belt.  In the past year, Joomla as made major strides toward a full community-based web application.  Even though the DotNetNuke application is right in the middle between community and enterprise, I think that DotNetNuke Corporation is going to seriously need to change something major in order to stay a competitive product.

A business mentor once told me "Grow or die."  DotNetNuke needs to start growing again.  A lot of people have a lot more on the line than the members of the Corp do.

 

 
New Post
8/17/2008 3:33 PM
 

Now, I disagree...I like this look.  Clean and basic with room to expand...thanks for the preview.....

 
New Post
8/17/2008 3:35 PM
 

Billy Van Rensburg wrote

Even with your origanal post you did contribute. You have mentally put yourself in the role to complain and got carried away. Every one knows that there is a few small problems they don't constantly need to be remembered. Every web page that on the web got small problem with browser compatabilities. So see the FireFox compliant as a ability one browser got over another for any CSS compatibilty issues don't complain on this forum complain to the browser developers forum and tell us you complained to them, I promise you will get support from our community. Yes, not all problems is third party but let me tell you this DNN corp is one (if not the only) of the few that tries to keep up with technology and I feel they do a great job at it as well. I bet if you have to pay for all the things you complain about to fix, you will rather live with it then to complain about them. I want you to know i also got a few issues but I don't complain I am looking for solutions and give recomendations. So just remember just because you can complain does not give you the right to do so! I hope you can take critisism as good as you can give it. Take one problem at a time lets help you solve it don't just sit there and compile an archive. I challange you to wait for then next release of DNN and check if some of the stuff you complained is solved. If there is a few solved than you stop complaining if not you can complain as much as you like to and I will pull back my post about your complaints. So are we on !!!!!!!!!!!!!!!

Thanks for your thoughts Billy. I'm not getting carried away, I have just learned in this world that some times there needs to be a squeaky wheel. I know things can take time and sometimes you just have to wait. What I am saying is that there is a cost.

Tony had a great post. He said "Have any of you compared DotNetNuke to Joomla (community target product) or Alfresco (enterprise targeted product)?  DotNetNuke is clearly much more flexible than either of them, but its loosing mindshare.  A year ago, DotNetNuke was perceived as a vibrant, cutting edge technology.  I'm not sure that's the case anymore.  In the past year, Alfresco has become a serious enterprise player with a large number of large scale, corporate accounts under their belt.  In the past year, Joomla as made major strides toward a full community-based web application.  Even though the DotNetNuke application is right in the middle between community and enterprise, I think that DotNetNuke Corporation is going to seriously need to change something major in order to stay a competitive product."

The point is this: Business as usual isn't going to cut it anymore. I'm a big DNN fan. I once was a diehard MS fan. Sadly those days are gone. I don't want to say the same for DNN because at it's core I belive in the product and its potential. I wish MS would turn around too, but that a different story.

 
New Post
8/18/2008 8:33 AM
 

Yep.  I think there needs to be a drastic overhaul of how the corp runs themselves.  DotNetNuke has a much stronger, almost "cultish" following (I'm one of them!   ) than products like Alfresco, but Alfresco runs themselves like a true corporation and is getting some major press because of it.  They were even named Network World's #1 software company to watch.  I'd bet money that there's going to be a much larger difference between Alfreso 4 and Alfreso 3 than there will be between DotNetNuke 5 and DotNetNuke 3, especially with Alfresco's sharepoint features (which DotNetNuke is still majorly lacking).

I hope the corp can pull it together.  We've been wanting workflow so bad that about 18 months ago, we actually built the code and sent them a working proof of concept (it actually combined Workflow with a different model for inter-module communication - it was really sweet!).  But... it didn't meet their business requirements so DotNetNuke is still without workflow.

By the way, DotNetNuke.com just seemed to go down for about 10 minutes.  Has anyone else noticed the website being slow/flaky?

 
New Post
8/18/2008 11:44 AM
 

Tony Valenti wrote
 

Andrew,
That is the new DotNetNuke 5.0 skin in all its glory.  :)  It is sooo beautiful, don't you think?

I really hope that Joe is right about there being a lot of stuff happening in the background.  We were looking over release dates yesterday and in over a year, DotNetNuke has gone from version 4.3.x to version 4.8.x.  Apart from lots and lots and lots of bug fixes, I can't think of a major feature that has been added in the past year.  And, when you've played with the 5.0 betas, it is really hard to get excited about a new skin, "Deny" permissions, and "a whole lot of behind the scene changes."

Have any of you compared DotNetNuke to Joomla (community target product) or Alfresco (enterprise targeted product)?  DotNetNuke is clearly much more flexible than either of them, but its loosing mindshare.  A year ago, DotNetNuke was perceived as a vibrant, cutting edge technology.  I'm not sure that's the case anymore.  In the past year, Alfresco has become a serious enterprise player with a large number of large scale, corporate accounts under their belt.  In the past year, Joomla as made major strides toward a full community-based web application.  Even though the DotNetNuke application is right in the middle between community and enterprise, I think that DotNetNuke Corporation is going to seriously need to change something major in order to stay a competitive product.

A business mentor once told me "Grow or die."  DotNetNuke needs to start growing again.  A lot of people have a lot more on the line than the members of the Corp do.

I'm not going to get too far into this as I'm sure this would turn into a flame war if I did, but I would argue that 4.3.x - 4.8.x has shown a number of large improvements, some of which are even very noticable.  The biggest of all I would say is the inclusion of AJAX support in 4.6.0 and the provider implementation for Authentication systems.  In addition to this performance enhancements to the core in 4.4.1 and other versions have allowed DNN to support higher system loads.  So there have been improvements.

I guess in my opinion behind the scenes updates are not glorified changes, but without them we wouldn't have an infrastructure that can support the visible changes that everyone wants. 


-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Why is DotNetNuke giving itself a black eyeWhy is DotNetNuke giving itself a black eye


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