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...Problems with the DNN ProjectProblems with the DNN Project
Previous
 
Next
New Post
2/22/2007 2:00 PM
 
I’ve used DNN for several years now and find it to be the most useful “portal management” software on the market. I know everyone puts in a lot of hard work to get it to the point it is. As good as it is, there are several major problems with the project. I know I’m probably going to get flamed for criticising DNN, but I think somebody has to do it.
Every time I’ve seen a thread like this there are the usual die-hards jumping in with comments about how its “free” and done by volunteers, etc... I do not want to go down that road and argue semantics. Please start a new thread if you want to discuss these kinds of issues. J I’m taking the time to put this down so that something will be done about the problems and I hope that others will chime in support of these issues. Anyhow the major issues:
1.       DNN’s site, and Gemini are often down or slow. It seems like every time I go to the site lately it is either not working or really slow. It’s pretty hard to report bugs when Gemini is down. Other “open source” projects don’t all have this problem, so why DNN?
2.       Bugs are ignored for long periods of time. I’ve reported bugs including the actual fixes in the source code only to have them sit there (sometimes for over a year) without any acknowledgment. Sometimes they are flagged as duplicate because someone else has reported the same issue months down the road. So why is the earlier issue flagged as duplicate? Why are core bugs not even acknowledged?
3.       Major bugs are not caught because there is no public beta. By listening to some of the team members it seems that DNN has a stringent release protocol. However MAJOR bugs are not being caught before release. I think part of the problem is that that you only get to beta test if you are a paid member. 4.1.1 had major issues with compression that would have been caught by anyone using third party controls or even the repository module. Why weren’t these issues caught? Perhaps they were caught but couldn’t be fixed by the time of the release. If so, they should have been put in a readme...
4.       Forums are next to useless to search.  I was really concerned when the decision to switch from asp.net forums to the forums module was made. I wondered about the loss of the old knowledgebase and how functional the new forums would be.  I can see I was right. Search is downright horrible. Unless you notice that the start date is set for today and change it, you will get no results. If you expand the date range, most often it will time out and you’ll get nothing. And don’t try to narrow it down by checking off a particular sub-forum because that doesn’t even work.
5.       Stale projects. This is probably the biggest issue. I realise that there was quite a shake up recently with certain people being asked to resign to try to correct this, but I’m not sure even now that things have been corrected. For example, the Active Directory core module has had several major bugs for well over a year that have not be corrected or even acknowledged.  In fact if you look at the forums, some members have actually taken it upon themselves to correct the issues every time a new release is made and offer third party patches. There doesn’t seem to by any response from TAM in ages, so I don’t think it will be fixed soon. Just about everyone who uses DNN for an intranet portal in a windows environment needs this feature, but it is ignored. Other projects like the repository have promised releases for over a year...but nothing ever shows up. And the gallery has been in beta forever...
6.       No Changelog. This seems to be changing somewhat, with some postings in the blogs etc, but still there is no changelog file in the distribution. This is an absolute necessity. As mentioned above it seems like there are major bugs in every release so it’s a real crap-shoot trying to decide if you should upgrade or not to fix bugs you currently have.
7.       Roadmap is blank. The roadmap is useless and should be removed from the site. It hasn’t had accurate information in it since 3.0 first came out. Mostly it’s blank anyway...
I’m sure there is a lot more I could on about, but I think that’s plenty. I realise that managing a project of this size and complexity is difficult, but other open source projects (some as large) don’t seem to have these kinds of issues. I hope something is being done to address some of these issues as they’ve plagued DNN for the last couple of years. DNN is an absolute Godsend and hope some of this is worked out soon.
 
New Post
2/22/2007 4:12 PM
 
dstgroup wrote
1.       DNN’s site, and Gemini are often down or slow. It seems like every time I go to the site lately it is either not working or really slow. It’s pretty hard to report bugs when Gemini is down. Other “open source” projects don’t all have this problem, so why DNN?
2.       Bugs are ignored for long periods of time. I’ve reported bugs including the actual fixes in the source code only to have them sit there (sometimes for over a year) without any acknowledgment. Sometimes they are flagged as duplicate because someone else has reported the same issue months down the road. So why is the earlier issue flagged as duplicate? Why are core bugs not even acknowledged?
3.       Major bugs are not caught because there is no public beta. By listening to some of the team members it seems that DNN has a stringent release protocol. However MAJOR bugs are not being caught before release. I think part of the problem is that that you only get to beta test if you are a paid member. 4.1.1 had major issues with compression that would have been caught by anyone using third party controls or even the repository module. Why weren’t these issues caught? Perhaps they were caught but couldn’t be fixed by the time of the release. If so, they should have been put in a readme...
4.       Forums are next to useless to search.  I was really concerned when the decision to switch from asp.net forums to the forums module was made. I wondered about the loss of the old knowledgebase and how functional the new forums would be.  I can see I was right. Search is downright horrible. Unless you notice that the start date is set for today and change it, you will get no results. If you expand the date range, most often it will time out and you’ll get nothing. And don’t try to narrow it down by checking off a particular sub-forum because that doesn’t even work.
5.       Stale projects. This is probably the biggest issue. I realise that there was quite a shake up recently with certain people being asked to resign to try to correct this, but I’m not sure even now that things have been corrected. For example, the Active Directory core module has had several major bugs for well over a year that have not be corrected or even acknowledged.  In fact if you look at the forums, some members have actually taken it upon themselves to correct the issues every time a new release is made and offer third party patches. There doesn’t seem to by any response from TAM in ages, so I don’t think it will be fixed soon. Just about everyone who uses DNN for an intranet portal in a windows environment needs this feature, but it is ignored. Other projects like the repository have promised releases for over a year...but nothing ever shows up. And the gallery has been in beta forever...
6.       No Changelog. This seems to be changing somewhat, with some postings in the blogs etc, but still there is no changelog file in the distribution. This is an absolute necessity. As mentioned above it seems like there are major bugs in every release so it’s a real crap-shoot trying to decide if you should upgrade or not to fix bugs you currently have.
7.       Roadmap is blank. The roadmap is useless and should be removed from the site. It hasn’t had accurate information in it since 3.0 first came out. Mostly it’s blank anyway...
I’m sure there is a lot more I could on about, but I think that’s plenty. I realise that managing a project of this size and complexity is difficult, but other open source projects (some as large) don’t seem to have these kinds of issues. I hope something is being done to address some of these issues as they’ve plagued DNN for the last couple of years. DNN is an absolute Godsend and hope some of this is worked out soon.

I'm going to respond to a few of the comments that I feel I'm capable of responding to.

1. DotNetNuke.com hasn't been slow for me in months, not since the 4.4.* release with all the performance inhancements.

4. There is new forums code coming. I agree with you that the searching and usefulness of the current forums can be very limiting, but I think Crispy has taken a HUGE undertaking with the upcoming release to completely rework the forums and fix these issues.

6. I try to post changelogs in my blogs, but your best bet for finding the change log is to look at the changelog available in Gemini.

 


Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions
 
New Post
2/23/2007 2:30 PM
 
Hi Chris,
I'd like to address some of the things you said.
1. I agree that the site is faster with the new code. However it seems like every 3rd or 4th time I visit there is maintenance being done or something that causes the whole site to be slow...like it was yesterday just prior to my posting the thread. I don’t know what is going on behind the scenes, but it’s really irritating.
4. I’m really hyped by the new forums and hope it will fix the search features now lacking in the site. I used to monitor and read the DNN ASP.NET forums every day. Now I only come to the forums when I absolutely have to track down bugs etc... I don’t even try to search, and just browse hoping the info is near the top somewhere. Usually I find the same questions asked over and over...
6. Yes, you were the “This seems to be changing somewhat, with some postings in the blogs etc” I mentioned. J And believe me, it is REALLY appreciated. Now if only that information made its way into each release...
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Problems with the DNN ProjectProblems with the DNN Project


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