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

HomeHomeUsing DNN Platf...Using DNN Platf...Using Modules a...Using Modules a...DNN 6 - uninstallingDNN 6 - uninstalling
Previous
 
Next
New Post
8/21/2011 4:20 PM
 
Unfortunately, I am uninstalling DNN 6.  Somehow it got put as an auto-install on Godaddy.com  - this from guys who would not put up a single version upgrade for months due to them saying how it was never tested.

Reasons I won't be going DNN6?  The first one is that after investing heavily in DNN5 modules, I have come to realize how 99% of my modules are not even compatible with DNN 6.  So after wasting much time trying to get them to work thinking it was my fault, I am more than a little frustrated this version is so incompatible, where previous 4.x and 5.x versions did not have this many major difficulties.

I am rather also frustrated with the haphazard way the menus and installations of modules, I mean extensions have been renamed and then changed entirely from previous versions.  Wasted many more hours trying to figure out how to install modules, only to now come to the conclusion I won't risk installing DNN 6 until each of the modules I purchased have a DNN 6 upgrade.  I can only wonder what the Vendors must be thinking to have to do this for free?  I guess the answer is obvious that none of my purchased snowcovered.com modules I bought in the last few months xxxx.xx in value are now worthless.

The ability to add multiple pages at once was nice.  The base functionality of having to skin individual pages is the worst user-experience possible for this end-user consultant.  Do I really want to use dark-knight?  No., So why do all the new pages not use the skin I spent $xxx.xx on to work with DNN 6 and continue to default BACK to dark_knight?  And not one person in the beta realized this?  Does everyone have a red, white black and grey website now? ;0

Hopefully these complaints won't fall on deaf ears. 
Hopefully someone will focus on user-experience instead of pushing a major release like this with all these major inconveniences, I mean upgrades...
Hopefully you will hire a user-experience team instead of just using designers to build out the CMS according to what the dev team decides to put.  The haphazard menu functionality and taxonomy for installing skins/containers is rather interesting to be in Settings ? Upload skin/container and not update the entire site...  I can only imagine the head-ache someone is running into with a 100-1000 page website and wanting to use a skin alternative to dark_knight...

I will just keep DNN 5 install handy and do the installs manually for now on, maybe for years until DNN dev team regains my trust that I won't waste 40+ hours trying to figure and retrain myself on how to use a completely different application. 

I did not enjoy this installation experience at all.  Fortunately I didn't upgrade an existing website in production.

Sorry for the complaints.  I just want the dev team to realize that user-experience is more important than stacking functionality into a product and costing their users time and money because they won't hire a user-experience architect to really get the feedback to make this a superior product.  When a product wastes time and money it is not an upgrade.
 
New Post
8/21/2011 9:16 PM
 
Firstly with regard to DNN and skins - what are you talking about - I have any number of sites that have nothing to do with the darkknight skin - there is no reason whatsoever to have to manually skin each page.

You set the default skin for your site on the admin settings page - and that is automatically used on every page in your site that does not have a skin manually selected.

This has been the same functionality since dnn 1.00 - nothing has changed in that area - the only difference is that the old skin module has been deprecated (it was always an ugly mess any way ) and the function of the Admin skin has evolved to be an Edit skin.

With regard to the dnn api and backward compatibility - just about every one of the 100 plus modules we use on different sites have all ported flawlessly to dnn600. 

The only ones that had issues - were the ones that didnt comply with the dnn api - and instead try to do things like manually access core database tables - in which case it IS up to the module vendors to fix such issues - they broke the rules which say -  USE the api.

Westa



 
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Using Modules a...Using Modules a...DNN 6 - uninstallingDNN 6 - uninstalling


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