Menu migration not reproducible via the GUI?

The megamenu menu system is only for top level links. Technically for "megamenu" you should only have a top level link and a link directly below it. That minipanel link will call a minipanel based on the megamenu (insert) menu.

I think a tutorial is in order for this as can get confusing at first if workflow is not defined. I will write one up this weekend. Will you be able to test out the tutorial on Monday. I will do the use case you have defined so can follow.

This also could be a theme hook not firing for that specific menu block. wetkit_menu.module does some pretty nifty stuff to ensure the markup is correct whether it is a sidebar, megamenu, or regular menu.

I will write a tutorial on the doc site this weekend but out of curiosity were these the steps you used roughly?

Menu Steps

1) Add a new menu entry in "megamenu" lets call it test "Test"
2) Added another menu entry in "megamenu" below test but as a path specifying and associated this menu item with an existing minipanel based menu block.

Mini Panel Steps

1) The minipanel itself should be based on a menu block with relevant settings specified such as depth, etc.
2) Additionally there is a panels style plugin that you can apply to achieve further refinement of the menu markup.

Hey just popping in. Been a little late on this but am booking some time tomorrow for it. :)

Any progress on this? I have temporarily found a workaround to use a "Placeholder" menu item that allows the "leaf node" menu item to be a link.

However, this causes the Placeholder to appear in the breadcrumbs. So I am creating a custom module to hide "placeholder" menu items. Quite a hack, but it's all I can think of to do without making changes to the wetkit_breadcrumbs module.

Also, a tutorial would be nice as requested above :) Thanks

I haven't forgot this issue sorry kicked the can on this so much.

I have some documentation written by a colleague in PDF but spans 20 pages and goes into what a mega menu is etc. (That part is for our business side)

So have been working on the markdown file to convert it. I can get this done during the following week.

If you would like the PDF we can I can send that off to an email :)

I would like a copy of that PDF or the markdown file...sent you a PM using the drupal contact form but you haven't replied so I'm guessing you didn't get it. I also looked you up on GEDS but you arent there. I work for the government as well. But can you just contact me at chris.delalisATpco-bcp.gc.ca

Thanks!
Chris

Just send this your way.

Has the documentation provided highlighted the issue?

I skimmed the documentation but have yet to go through it in detail. There may be something in there that we missed when setting it up. I will let you know.

In the mean time, could you confirm whether or not you are still doing coding work on the Menus? Or are you fairly certain that it is us not using it correctly?

Also, do you have similar documentation for configuring the "sidebar" properly? For some reason the sidebar is always expanded instead of expanding and collapsing properly based on what node/view you are on.

@sylus any chance you could send the PDF or markdown file my way?

carl.leducATcsa-asc.gc.ca

Currently working experiencing the same issue where items I add that weren't part of the original megamenu the parent item is not linked. Must be some odd thing I missed when trying to re-create the same setup with my own links.

Cheers!

Carl

Hi Sylus, going through the documentation, I noticed that our version of the wetkit distribution is missing a field when setting up a new menu link.

Namely in your documentation on page 6. It says "9. Set Menu minipanel to -None- as this is the Top Mega menu item"

However, we do not have a field called "Menu Minipanel" see screenshot:

Where does this field come from? Do I have to enable it in some module?

I figured that out. Apparently on the menu properties (the menu itself, not the menu item) you have to select the checkbox to enable "Allow to be used with WetKit Menu"

I found another "bug" with the menus that I would like you to address if possible:

I followed the menu documentation you sent me, and it set up the menu's properly. Now we wish to have menu items nested under the first depth level. (i.e. 2nd level depth menu items)

However, when clicking "Save configuration" after adding this menu item to 2nd depth level of the Menu (mini panel), it no longer appears in the menu, neither does it even appear in the page source code! This leads me to believe that wetkit does not support menu items at depth level > 1.

Can you confirm??
See attached screenshot:

So for WCMS Teams you are displaying a mini panel based menu block. Can you provide a screenshot of the menu block settings you have?

Sure, do you mean a screenshot of the minipanel content, settings, context, or layout?

Here is the content:
*note - I added french and english to the same minipanel because your documentation said I could. I just had to switch the admin UI to french mode to add french content.

here is the menu block: Mega Menu (insert) which was already present when I installed the wetkit template - I tried to emulate the Mega Menu (Statistics Canada) you set up in your documentation/
* Note - I also created a subtheme called wetkit_omega_lgc so I could add some custom css files for tweaking the css, but that shouldn't have any effect on the menus...

Alot of these issues should be solved based on the work here: #2199997: Improve the whole menu workflow.

The whole process for creating menus is going to be much simpler and it should address all of your issues and allow for proper render of different menus at different depths.

Give me another day to package it all up and will make sure it solves this issue ^_^

great news. could you please also post on this thread as well once that is released?

thanks.

The enhancement from #2199997 made it into distro v1.4.
Judging from the recent patches on v1.4 of the distro I'm going to skip v1.4 and upgrade against the dev build and qa that version.

Looks like this issue #2146897 should be closed as the enhancement from #2199997 is now included with the current builds of the distro.

Sounds reasonable to me lets close this issue and should any issues still persist after consulting the documentation at drupalwxt.org please file a new issue showing steps taken and intended output.

Finally this is resolved :)