Re-architect megamenu module in Drupal 7.x-2.x branch

Given these issues…

• #886652: Can I add an extra degree of depth/nesting to the megamenu?
• Add embedded blocks within mega menus

I spent a couple hours evaluating the existing module, and it appears that this module would need to be completely re-architected to support those features in a sane manner.

Between now and Drupalcon, I'm going to work on writing a d7 mega menu module from scratch based on numerous code snippets I have on existing sites. I'm willing to collaborate rather then just create a new project, but I don't know the interest on your end.

Here's sketch of how the configuration of a mega menu would work.

1. Block configuration:
   1. menu name
   2. menu depth (defaults to 2)
   3. admin title
   4. machine name
2. Each menu item in the primary level menu link needs its own configuration as well:
   1. # of columns to split child menu links into
   2. layout (pluggable layouts with multi-column as the default)
   3. menu slice positioning within layout
   4. embedded block positioning within layout

There's also the possibility that it would need to leverage the API of the menu_block module. Which means menu_block would become a dependency.

Obviously, this is big departure from the existing code base. If you'd like to collaborate, great! You can also hold off on deciding until after I have some code for you to review.

subscribe

Just talked to Andrew via email. I'll start working on the new code in a 7.x-2.x branch.

So, who wants to give me CVS access? :-)

Just exactly what I wanted for 7.2x
Tell me if you need some extra hand

John you have access now! Thanks for collaborating.

Also, I've given filmknurd rights to administer maintainers.

subscribing

Hello,

I am very interested in the development for the 7.x-2.x branch of this module.
Unfortunately I cannot code, but if you need an early tester - count me in.

Kirsten

Hi, still testing 7.x.1 version and be happy to test 7.x.2 branch.

I am specifically looking at drop down menus for D7 using multiple sites using the excellent Domain Access Module – and creating workarounds using Taxonomy Menu to generate menu items against different site names. This populates the menus.
So far I have a crude working solution in the dynamic naming of the menu item tree based on site domain. The following example is an overview that would be in module:

$_domain = domain_get_domain();
$menudomain = 'menu-' . str_replace('.', '-', ($_domain['subdomain']));

Then, get menu tree based on $menudomain variable.

(You have to name your menus as:. www-yoursite1-com , www-yoursite2-com to match etc.)

Crude, but works :)

A simple checkbox in the configuration form could be set up to include Domain Access functionality which would be the only module tested to work on D7 with independent menus on a per domain basis.

Hope this might be useful in future.

Tim

Did this go anywhere? I can't see any indication that JohnAlbin did work on this at all... Is there maybe a separate sandbox where this might have gone on?

I didn't mean to sound demanding, I just wanted to be sure I wasn't missing anything. Thank you :)

subsub!

Hi !
I was using this amazing module MEGAMENU with drupal 6 as my primary menu and was trying to use it with drupal 7 . I used same code and it does not seem to be working. how should it be called from acquia marina page.tpl.php to use it as primary menu in drupal 7?

This is the code i am using with d6 and i am using acquia marina theme.

   $megamenu = module_invoke('megamenu', 'block', 'view', 0);
   print $megamenu['content'];

Regards

Just create a block on your page.tpl.php, example:

<?php if ($page['main_menu']) print render($page['main_menu']); ?>

Assign megamenu on your "main_menu" block

That being said that if you use my ported D7 version. Not 7.2-dev

I am really interested in this 7.x-2.x version but the Git branch looks untouched since Feb 25
Is this always planned ? Is there something I can do to help ?

In the meantime I'm looking to this module for my megamenu needs http://drupal.org/project/menu_minipanels

Haven't used it yet, but about to give it a go.

Panels is a great module but also a huge one, required by menu_minipanels.
If you do not use it for your whole website, I think it is a bit too expensive to load it just for your menu.

My 2 cents

I'm using panels everywhere so I'm already neck deep in panels :)

Could anyone tell me where to find the 7.x-2.x branch ?

thanks

The 7.x-2.x branch is currently empty. You can see it on git.

ok thanks

I'm not able to get both megamenu and menu minipanels working together - it's one or the other.... any suggestions appreciated

As I am the new maintainer. I will take a bit of a new approach. I will try to get the 1.x to a stable release and 2.x will be a complete rewrite hopefully with a frontend colleague, we will develop something nice.