Login       Friday, September 03, 2010    
Search
Articles
Queen Played By Old School Hardware
Get Ready For The End Of Windows OS As We Know It
Weezer Pork & Beans Video Is Awesome!!
Silverlight 2.0 Beta - The Long Wait Is Finally Over
Things Geeks Do When Bored
Bill Gates Nostalgia - Lest We Forget
Wooden Binary Adding Machine Using Marbles
GoDaddy Lets Their SSL Certificate Expire
Multitouch Display using Wiimote
Rapid Replication - Fabricating Things The Open Source Way
How Much Does The Universe Weigh?
Windbelt - Affordable Power From the Wind
I'm Liquidating My Old .NET Books
New Printer Translates Japanese to English
Cyberdelic ASCII Googles
If I Was A DotNetNuke Core Teamer What Would I Fix?
Our Next President
Bypass the Sony Rootkit
The Worlds Smallest Power Source
Drag-n-Drop Video
How to Open Your Visual Studio Projects from a Network.
Alienware Area-51 m9150
Iframe in AJAX
WPF/e is Named SilverLight
Every American Should (not!) Have A Chip Implant
Pyramid Mystery Discovered?
Tooth Cellphone Implants
Wireless Electricity is REAL! - finally
The Coolest USB Attachment
Tutorial how to install WPF/e on your Origami
Assembly Steps of the International Space Station
KodHedZ WPF/e Databinding Video Player Module
WPF/e Video Player DNN Module Tutorial
WPF/e within DotNetNuke and DataBinding
Getting a full url from dnn for your portal directory
Apple and Cisco go to bed over iPhone
Collapsible Control Panel
NASA has released the C# Source Code For Viewing Planets
World First Quantum Computer
Hackers Attack Key Net Traffic Computers
The Ultimate Anti-EULA
Naked SQL Server Chicks
The Need for Creating Tag Standards
Geeky Thing Of The Day - Pay Per Click Content
My New Super Uber Geek Blog
If I Was A DotNetNuke Core Teamer What Would I Fix?
Bookmark This Page  View This Page Fullscreen  Print This Page  View the comments for this page  Add a comment for this page    View the RSS Feed Submit to del.icio.us Digg it Submit to Stumble Submit to Reddit Submit to Fark    Vote this page Up  Vote this page Down

I would love to say that DotNetNuke is a easy to use, intuitive solution to your web woes, but I would be misleading you.  As a consultant, a .Net developer for five years, and an active member of the DotNetNuke Core Team for 4 years, I have a shortlist of the most annoying things about DotNetNuke:

1. Make the + - Icons for module visibility a default OFF.  I am not sure who thought it is a good idea to make all the modules on a page show the +- icon by default but it is so really annoying. I actually got some personal flak about it on a website i have never even heard of before.  They thought it was annoying too.  DNN Core Team, please fix this and make it default to NO Visibility.

2. Make the Print Icon default to OFF.  Whoever thought this is a good idea to have as a default ON is really missing the point.  Designers spend countless hours on each website changing the default ON settings of this to OFF.  What a waste, if we wanted to see the stupid print icon, we would set it to show for that module.

3. Add a warning message to the Section Header of Admin > Site Settings > Marketing Options to dissuade new users from doing these things until the website is completed:

In DNN 4.5.5 they have a nicely labeled "Marketing Settings" pane in the Admin > Site Settings menu.  This is really nice to have, except that the repercussions from new users will be tremendous.  Imagine using the Submit to Google/Microsoft/Yahoo button once or twice a day for a week, only to have your website show up in the Supplementary Index of the search engines for the next year.  Be judicious, never submit your website to these search engines more than once a month (at most) or they will punish you and put you at the end of the search results.

The answer is to add a message to the section header saying "Do NOT use these tolls until your website is ready for submission to websites.  IF you are still under construction or don't have a lot of content, you should consider waiting to click on these options."

4.When you copy a module or make a copy of a tab, the module settings are not preserved!

This is by far one of the most annoying things about DotNetNuke.  Why on DNN;s sweet ass can't they copy over the module settings?  Who wants to save a couple seconds by copying a page with it's modules, only to spend 20 minutes making all the configuration changes to the modules on that page.  Come on DotNetNuke Corp, this is an easy one...

That is my rant of the day, but it had to come out... I have been putting up wioth these same lame issues for version after version for years... what is wrong with this picture?  Usability is a joke, it seems to be tailored for the developer/techies than the user/website owner.

I know they can get it right, but the question is how long it will take...





Your Name (public):
Email Address (private):
Comment:
 Latest Video

Get the Flash Player to see this video.

  
Search By Tag
Join This TagPlace
Your Email Address
 
Subscribe
    KodHedZ Software Team DiscHeads Disc Golf Super Uber Geek Disc Golf World News multistore Enterprise Architect Sports and so Much More More .net Modules Champion Plastic Disc Golf Outlet evopoint Affiliate Marketing Help Begin to Garden Backpack the World Tennis strokes and how to hit a fuzzy ball. In Profit List Building Jacob Bushnell Wood Recovery Inc.
Privacy Statement   Copyright 2007 by KodHedZ Software Development, Inc