Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

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...Module action menus surpressed?Module action menus surpressed?
Previous
 
Next
New Post
6/27/2011 11:46 PM
 
ROB AX

Joined: 9/3/2004
Posts: 2185
Let me revise the pageload stats as I'd forgotten how DNN5 had become and Google has since then also altered page speed scoring.

Results are still rubbish overall at between 26 and 34 compared to 80 with my skin and menus.

Performance aside, why not just let existing components work as they did and use new ones for the new bits. Supporting legacy functionality in any system is vital for retaining one's existing customer base... just ask Microsoft.

You don't have to develop or support the legacy stuff further, and you can even put a cap on its lifespan, but this is way to early to wipe out reasonable things like being able to continue using a custom action menu.

For example, I note that the new default login is in a popup, and that's fine. But the most important thing is that my existing login on my own skins is not being orverridden and still works as it always did.

That's how all of these things should be done in my view.

I'm keen to have any pointers as to how it's even finding my custom action menu and replacing it? I'll keep looking.
 
New Post
6/27/2011 11:49 PM
 
ROB AX

Joined: 9/3/2004
Posts: 2185
p.s. I note that the Host setting to disable the customer module css class is still broken.
 
New Post
6/28/2011 12:09 AM
 
ROB AX

Joined: 9/3/2004
Posts: 2185
p.p.s Some good news.. there's a host setting, next to the broken item mentioned above, to disable the overlays.

That won't make much difference to performance, but it's a big win back in usability, especially across different devices... good stuff :) I was already tiring of scrolling around the overlays trying to find the next steps.

Just on a related point - There's an inherent logic, hierarchy and ease-of-use present in the traditional vertical scrolling page. Everything from people's expectations to their hardware is built around this basic system.

All of this is lost when one has to squeeze the same amount of content into a small vertically-restricted window as with these overlays. The additional scrollbars, tabbing, and expandable sections required may all look very cool, but are ultimately a step backward for the user.

Just something to think about.
 
New Post
6/28/2011 2:38 AM
 
Chris Paterra


Joined: 4/5/2003
Posts: 4377
Rob,

I appreciate all the feedback. There were a lot of things that were changed in 6 (with regards to design and admin interfaces) and I understand the frustration. We are still looking at a few things now to see if they need to be changed prior to a 'retail' public release (for example, I know we are adding in a couple css styles to default.css that were removed in the beta), so all feedback is being reviewed and considered. We really are trying to minimize the impact seen in upgrade installs, as well as move the framework forward too. Most things I have tested look 'and feel' very similar in 6 and as far as modules and providers go, they are all working as they were in 5 (I did check-in a change post beta to resolve a problem with the dnn label control that was UI related).

However, one thing you brought up that has certainly changed behavior is the module actions menu. I am not heavily involved in the development of this specific piece but I can tell you the premise behind it was to provide a consistent admin interface in the application for a number of reasons. There are a few others who could probably speak better to this and I will refrain from saying much more on the topic (because I would just be speculating). 

In reference to some of your other points:
  • There was a check-in to disable popups for third party modules (unless enabled by the developer, thus it would be dnn 6+ compatible only). All admin & host modules will still have this enabled by default (this is post beta). 
      • Recently we noticed (and corrected, but not in the Beta) a bug where module.css was loading in the wrong position (as I said, this is correct in source now but the beta has this flaw). 
  • We did add jQuery UI to pretty much any view an admin or content editor would see (this adds more js files and also required us to add to default.css). This script (which is > 200KB) is being loaded via CDN. There was some debate internally, at first, if we were going to send the whole thing but after much discussion we realized this way was best. 
  • There was some internal performance testing done, if I remember correctly DNN 6 is 20% faster than any version of DNN 5.

Chris Paterra

Get direct answers to your questions in the Community Exchange.
 
New Post
8/14/2011 8:36 AM
 
ROB AX

Joined: 9/3/2004
Posts: 2185
Turns out the action menu is not replaced automatically in the final release version on DNN6... great news!
 
 Page 2 of 2
Previous12 
Previous
 
Next
HomeHomeDevelopment and...Development and...Open Core Testi...Open Core Testi...Module action menus surpressed?Module action menus surpressed?


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