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...Please stop breaking the DotNetNuke.com sitePlease stop breaking the DotNetNuke.com site
Previous
 
Next
New Post
6/30/2009 10:19 AM
 

Twice this week I've had a question from someone higher in the payscale than myself, wondering why we are using software that seems to be broken.  I have no idea why they chose this week to look at what we're using, budgets maybe, but it's embarassing explaining that the main software web site is testing the newest version and that we're on an older, stable release.

Jeff

 
New Post
6/30/2009 10:25 AM
 

At minimum, I would like to see a "warning" message placed on the homepage and/or the under construction page that notes that testing is going on.

I have ended up going with a custom ASP.NET solution for a client, due to the perceived instability of the platform due to the site.


-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
 
New Post
6/30/2009 3:41 PM
 

Last week I was in the position of justifying the use of DNN for a major project for a client (through a consultant they hired for another purpose).  About an hour after sending a fairly comprehensive e-mail touting the benefits of DNN - I went to the site and it was down pretty well all day.  Embarrassing is one word that comes to mind (there are others I can think of but won't repeat since I'd like this post to remain on-line....  I didn't hear back from them that day so I'm hoping they didn't try to access the site.  I'm sure I would have heard about it if they did..

So I second the motion to please keep the DNN site up and running and not broken.  Besides it can't be good for PE sales when the site is up and down like a yo-yo.

 

 
New Post
6/30/2009 4:13 PM
 

Every site, regardless of software, has traffic patterns that are relevant to the specific business.  Part of this week I have spent tracking down issues that are specific to our own traffic patterns, which include malicious intent.  By way of example, we experienced an outage yesterday due to what amounts to a DOS attack on our SQL server.  This in turn stole CPU from SQL, increased load on our network monitoring tools capturing the event and resulted in starving the DNN site.  The problem has been remedied.

The silver lining in this story is that we eat our own cooking (aka "dogfooding").  Our skin is in the game. We use what we publish, in fact we push it to its limits (and beyond) and subject it to real world issues most customers will never face.  Don't misinterpret this as making an excuse, I will be the first to agree with you in terms of ensuring that these issues are permanently resolved and not customer facing, but there is also a powerful message here whereupon we do not use customized or proprietary magic to serve our interests.  We will resolve even the hardest, most difficult issues so that customers will not have to.

The overwhelming majority of issues being seen lately are a function of dotnetnuke.com's specific profile and traffic patterns.

Thank you for the encouragement... we hear you and support your sentiment.


Scott Willhite, Co-Founder DNN

"It is only with the heart that one can see rightly... what is essential is invisible to the eye. "
~ Antoine de Saint-Exupéry

 
New Post
6/30/2009 6:37 PM
 

Yet another reason why I think the DNN community needs it's own portal.

I have thought a DNN community portal, where the DNN community actually has a say in content and procedures, would be a good idea for some time now.

In addition to many other benefits, new DNN releases could be dogfooded on the community site instead of the Corp. site. Corp site could stay on a stable release, not be overloaded with users since most of the traffic on DNN.com is because of forums, and everyone would have a stable corp site to point clients to. Heck, the corp site might even be able to offer a DNN demo portal that is actually online and works. They have at least gotten the demo to produce a portal and a home page but the auto generated admin/host logins don't work.

A corp site that is offline, demo's that don't work, forums busted, forums filled with threads of community members bitching about this or that =  PE marketing nightmare.

Greg

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Please stop breaking the DotNetNuke.com sitePlease stop breaking the DotNetNuke.com site


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