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...DotNetNuke - Not Good Enough blog postingDotNetNuke - Not Good Enough blog posting
Previous
 
Next
New Post
3/15/2009 2:40 PM
 

http://deanjrobinson.com/article/dotnetnuke-not-good-enough/

Read about someone venting about DotNetNuke, he does have a nr of valid points. I use the DNN framework but inside have my own adittional development framework for modules, a 3rd party sematicly correct templatable menu system and various replacements for dnn core modules. So I do understand his arguments but instead of complain about is I just find better solutions for the things that im not completely satisfied with. 3rd party or custom build.

There are several good 3rd party modules that are much better than there core equivalences but also the garbage html output fo the forums and the incomplete rendering of tables has made me switch to 3rd party as well, You cant sell that to your clients. Especially clients that are going to pay for the PE version.

As a portal framework its perfect and handles almost anything I use it for or I can adapt too. But the all in one solution can not satisfy evryone especially compared to dedicated forum or blog module or soluton developers.

just my 2cts

 

 

 
New Post
3/15/2009 4:42 PM
 

armand datema wrote
 

As a portal framework its perfect and handles almost anything I use it for or I can adapt too. But the all in one solution can not satisfy evryone especially compared to dedicated forum or blog module or soluton developers.

I think you just nailed the reason I use DNN.  Because I can adapt it to what I need.  The other .NET CMS/Portal/Blog/Forum/Frameworks out there are less adaptable, though many do the few jobs they do extremely well.  And I have to admit, while I don't modify the core, I do delete many of the core modules.

I can't use the menu system.  Any of them.  They are non-functional and the only one that works fully and correctly is Telerik's control set.

I can't use the forum.  It hasn't ever worked.  Period.  It does have extremely long-lasting bugs, but it never validated, always screws up and basically sucks for configurability.  Active Forums is really the only one that works correctly, and that's not perfect.

I can't use the blog module.  Even the latest version, which borrows heavily from Ventrian's News look and feel, doesn't meet anywhere near my needs.  Or likey anyone's.  Ventrian's News is a better blog than the core blog.

I can't use the announcements, documents, repository, media or gallery modules.  They are all useless and there are better ones available.

I can't use the Newsfeeds, Feedback, Survey or FAQ modules.  All of them fall extremely short.

I can't use search.  Mostly because it can't search.  Fortunately Google has the perfect solution.

I can't use the Events module.  It has had major issues for way too long.  Fortunately Goole has a calendar that incorporates quite easily as well.

Reports suck.  So do the XML module and the User Defined Tables.

The Links module is usable.  But it's too cumbersome to work with.  And the stupid LinkClick links it creates break every other week and trash any resemblance or SEO functionality.  As well as break the search mechanism.  Actually, it's also the same fault with the FCKEditor provider.

The Text/HTML module is okay.  In fact, it's probably the best functioning and most useful module.  Except for the FCKEditor issues.  Telerik's editor is far better and easier for end users to understand.

You know, I'm no longer sure why I really use DotNetNuke.  Except that I know it.  The Devil you kow kinda thing.  I can beat it into submission, though I often don't think I should have to.  Though I do seem to be making module developers rich, stimulating the economy...

Jeff

 
New Post
3/16/2009 7:05 AM
 

Hi,

Links Module is actually kinda broken too... Due to the SEO issues. I rather hardcoded the links using html module.
My DNN site is actually = Ventrian Site where all of my modules are from Ventrian beside the html module.
For the Gallery Module...no offence...I rather hard coded it using html module or using ventrian.

"You know, I'm no longer sure why I really use DotNetNuke."

I have the same feeling too and actually started to look for alternative as I'm wondering:

Why would I pay so much for 3rd party modules (More than USD300
to date)...while I'm using a open source platform?


Maybe afterall DotNetNuke do not need a PE version but it is the DNN MODULES NEEDED PE version.

If I have the money to pay JUST For a CORE (PE ver.), why don't I pay a little bit more for whole worry free platform+modules? (kentico)

George.

 


Thanks,
George

Where to eat? Visit GoEatOut for Food Promotion in Kuala Lumpur.
 
New Post
3/16/2009 8:48 AM
 

I gotta say that I don't have an issue with paying for open source.  I have never equated open source with "free" as many in the Linux world have.  When I started in the field, everything was basically open source, you bought a program and the source was delivered as well.  The source frequently had a development loop that was closed, similar to DNN, and if you wanted a different development you forked the code.  Very few people made money from code, they made money by adapting code more than anything else.

Now everyone and their brother is a coder.  They all know they can do it better, faster, stronger.  The reality is they can't, but you can't explain that.  They believe time is free.  I'll still pay for code to be written by someone else, even though I could write it myself.  My big issue with modules in DNN has always been that if I don''t have the code then I'm locked into a developer that might get hit with a beer truck.  I have rarely modified the core or any module code.  But I can.

As for alternatives, I've looked for a better option.  Commercial closed source or open source.  So far I haven't found one that meets my needs, which happen to include ASP.NET as a requirement.  But I don't stop looking.

Jeff

 
New Post
3/16/2009 11:03 AM
 

 "I can't use the announcements, documents, repository, media or gallery modules.  They are all useless and there are better ones available"

ouch. now I'm depressed.

it certainly wasn't my goal to build a useless module ;)  since I'm still in the process of re-building the Repository from the ground up, I'd like to know specifically why you think it's useless and what features would you really like to see in the next version.  I've reached out to the community for help and so far no one's stepped up to volunteer their time or expertise to assist .. seems everyone just wants stuff for free without actually contributing.  It's fine, we all have our reasons for participating in an open source project. It just means that it takes me much longer to get fixes and new versions out to the community.

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...DotNetNuke - Not Good Enough blog postingDotNetNuke - Not Good Enough blog posting


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