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

HomeHomeDevelopment and...Development and...Open Core Testi...Open Core Testi...DNN 7.0 CTP2 - Edit ModeDNN 7.0 CTP2 - Edit Mode
Previous
 
Next
New Post
9/24/2012 8:03 PM
 

I would like to see if other people are seeing the same thing that I am with the change to require users to "click to edit".

I just timed a few common activities that I perform on a daily basis when maintaining DNN sites between a 6.2.3 site and a 7.0 site.  The 7.0 site although faster to load pages, took me almost 3 times a long to actually perform the edits.

I think this is due to a few things.

  1. Once I start editing, I often have many more edits to do, often on other pages
  2. When logging in as a host/admin I shouldn't have to click "Edit" just to add a user on the User Accounts page for example.
    1. Similarly to this even a "sticky" mode where once I turn on edit mode would be better
  3. Removing the "Skin", and "Tab Name" from the quick access items in the control panel makes for a lot more time editing things that I used to be able to do without waiting for the full load of a dialog
  4. Similar to #3 "Copy Permissions to Childen" was key when setting up pages/structures when building out a site.  Lots of time is added now that this is gone

I would appreciate others opinions here.  For one off edits I think the new setup is great, but there is a lot of pain added for new site builds, and regular day-to-day edits.


-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
9/24/2012 8:14 PM
 
1 and 2 are already covered by the blog post from Will: this feature is not yet finished. (I encountered a number of associated issues while testing with multiple browsers.)

As far as I noticed, the focus of the new control panel is providing a totally different user experience, not necessarily driven by false believe in "efiiciency". What do you gain, if you only need one click - to distort the current design without an undo option ?- Instead of getting the time to think over your ideas while looking for the proper command, and choose the right action, when you'll find it, just a few moments later?

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
9/24/2012 8:40 PM
 

#1 and #2) I'll defer until the changes Will spoke about come into effect.  I think that will resolve it.

#3)  I tend to agree, although, honestly, I seldom used those quick edit features even though I knew they were there.  Definitely see the benefit though.  There is a trade off between "clean" and "convenient".  I think we are moving more towards "clean", which is good but does necessitate some loss of previous convenience.

#4) Same as above, I see the benefit, but I so rarely used it, I'm OK with it being on the actual Page Settings control only.  Might just be me though.

 
New Post
9/25/2012 11:36 AM
 

I guess I'm really curious as to Will's changes as there is not a mention about "staying" in edit mode when going page to page, I hope that statement is incorrect and that edit mode becomes sticky as the concerns with #1 and #2 will waste a LOT of time for the users, and honestly will place more load on the server when doing more edits than leaving it the old way.  I'll wait patiently for another update.

As for items #3 and #4 I can see the reasoning that they are not as "clean" the way there were implemented, but the efficiency when building out a site with 200+ pages is immense.  The biggest one for me is the removal of "Copy Permissions to Children", as now I don't see any way to do this, and that is HUGE, especially since the mass page creation process does not allow you to change permissions.


-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
9/25/2012 12:00 PM
 
This is an excellent thread. Thanks for all the feedback. Allow me to address the concerns that Mitchel raised.

1) This is a valid point, but the intended behavior is to require an explicit switch to edit mode for each page.

2) This is essentially a bug due to the way most admin modules handle IsEditable. We are working on a way to force edit mode when using host or admin modules.

3 & 4) A few others have brought this up as well. I will be talking with Ryan (UI/UX) this morning to see what we can do to find a good combination for both needs.

Will Morgenweck
VP, Product Management
DotNetNuke Corp.
 
Previous
 
Next
HomeHomeDevelopment and...Development and...Open Core Testi...Open Core Testi...DNN 7.0 CTP2 - Edit ModeDNN 7.0 CTP2 - Edit Mode


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