I'm trying to build a mega menu much like the one that Brandon Haynes just released only I want it in module format instead of a skin object. I want to be able to pop-up the module in Live Content in order to build a one button site menu.

I've searched every menu module on snowcovered with no luck, a table in a text/html module would work great but that would show pages that some users should not be able to see, and I just looked at the House of Nuke menu module and the House of Nuke Index module. Both of which might work but neither module will install in DNN 4.9.0 to say nothing of DNN 5.

Any ideas would be greatly appreciated!!

Greg

You might want to ask Brandon to also release his menu as a module. And that menu is still "beta." There are a couple of other people working on new menus. Keep an eye out for them.

Thanks for the reply Joe!

I've already spoke with Brandon - a module isn't going to be possible - at least anytime in the near future. I've seen Mark Allen's new menu (also beta) but it relies on already installed menu systems (solpart, dnnnav, etc.).

I've found a workaround but it is a serious hack - Magic Content text/html module will do role based content. I'm also checking a newer module called NavXP so we'll see. Any other ideas would be great!

Greg

Update: Success on two fronts! I found that my HouseMenu and HouseIndex zip files were corrupt which is why they wouldn't install. Not only did they install in 4.9.0 but they installed and worked fine in 5.0.1. Which is strange as I know there was a problem with the Housemenu 1.4.1 skin object in DNN 5 which Lee found the solution for. But the module version seems to work fine.

Also, the developers of the NavXP module are going to come out with a mega menu skin for their module next week.

that sounds great, keep us updated with your progress, I would be interested to see any menus created on your website.

Thanks,

Hi Greg, I just spotted this thread, and was wondering if you could tell me where you'd got the impression that my mega-menu template required SolPart or DNNMenu? All the templates are completely independent of any other template or menu, so if that's the message that's coming across then I need to fix the text on the website!

Cheers, Mark

Sorry Mark.  I guess my initial impression that SolPart or DNNMenu were required came from your Twitter posts of a month ago or so. But also on your website where it says:

"Drop-in upgrade for SolPart and DNNMenu" OR "Automatic upgrade: Upgrade your site's skin from standard SolPartMenu or DNNMenu....."

In order to upgrade something you have to have it to begin with.  I think I see now that you're trying to convey that your menu is super easy to upgrade to from SolPart and DNNMenu. Which is a great feature but I would add a point talking about stand alone abilities first on the list.

Update on the one button menu:  I ended up taking a chance and buying a really old (Feb. 2006) module from snowcovered called FlexPlex Navigator.  And I got lucky - it works fine in both DNN 4.9.x and DNN 5!!  This old module is pretty powerful for use as a mega menu, child links, or site map module. Ability to display page icon instead of (or in addition to) page title, page description tool tips, image separators, any number of columns, etc. If you set the pref to use page icons it will default to page title if no icon is specified for the page so I could build Photoshop images for Parent pages and child pages show up as hyperlink titles.

Now if I could just get IE to stop being such a pile of junk I'd be set! (grin)