In Joe's latest blog post it says:.



"In DotNetNuke 6 we have deprecated the use of the module action menu control. 

Any action menu that exists will be suppressed and a standard menu using the new

mega-menu styling will be injected."



Does this mean that custom and third party action menus are going to be wiped out no matter what?

I need to use my custom action menu and can't have it surpressed.



Thanks for any info on this one

Rob

Thanks for the reply Chris.

I'm not sure I fully understand...
As a skinner and non-developer, with loads of skins and containers which have a third party action menu, inserted using a container skin object, which works perfectly with DNN 3, 4 and 5... will all of this break in DNN 6?

I think what you're telling me is that one can build something else altogether, but what I'm trying to figure out is if any existing action menus one might have are specifically going to be targeted and killed, as the blog post suggests.

I'm going to set up another test of the current DNN6 release shortly and see if I can figure this out.
Rob

I've spent some more time with it now... and seriously... creating new interface bits for dnn 6 is all fine and dandy... and by all means, a new skin for dnn 6 should feature and demonstrate all of the changes, but who on earth decided it would be a great idea to intercept everyone's existing skinning and development work and simply replace it wholesale with this mess?

I've gone to great lengths to create a slick, small and useful interface for dnn, incuding all my own menus, action menus and control bar, and this simply overrides it all in a mass of scripted bloat.

I'm looking at nearly 6 times the resource hits (167!!) and a 1.12 Mb load, just to view a page as page editor. Sheer lunacy.. obviously no one building this ever edits sites remotely, or god forbid, on a mobile device.

A blank page in the core skin viewed anonymously now gets a pathetic 37 score on Google PageSpeed.. that's down from just under 70 for DNN5 and somewhat higher for DNN4. My own system scored 86 with all the bells and whistles on, and that now drops to 45... there's a gold medal for bloat in here somewhere.

Anyhow... none of this sort of 'progress' used to bug me because the great DNN framework allowed one to easily replace bits of it.. as a framework should. All I'm concerned about here is whether or not the final version is going to automatically and forcefully override action menus and anything else like this, or if legacy tokens will continue to work, which they don't in this beta, even though I see they are present. If anyone knows more, please let me know.

I'll keep investigating, but on first glance I'd suggest DNN should be using new tokens for the new functionality rather than repurposing old ones. That would avoid all dramas and allow skinners to migrate systems much more tidily over time to new functonality.

Regards
Rob