Interferers with Administration Menu--cannot click on admin links on top of a mega menu

I have enabled megamenu for the admin menu, but I see no effect whatsoever (I flashed caches and all). What might I be doing wrong?

...I am guessing that there should be 2nd level menus as 'slots' with 3rd level menus placed under them. Right?

Could anyone that had success with it provide a screenshot of what I should see please?

Thanks for taking the time to post the screenie Andrew, but is this the default install of Admin menu? I am asking because I was expecting to see some of the 1st, 2nd and 3rd levels of that module that I am used to. Or perhaps you've added some custom items ('lvl1', 'lvl2' and the 't3 - x' children) for testing purposes.

Also, is this a customized css alteration of the default Admin menu theme I see there?

This screen shot shows the Primary Links menu Interface with the levels and the resulting menu

http://drupal.org/files/issues/grimfan-megamenu-scnshot.jpg

BTW, I don't think that this module is meant to replace the Admin Menu with a Mega Menu.

It is primarily meant to replace the Primary and Secondary Links Menus.

Thank you John for taking the time to provide a second screenshot. Things are clear to me now. I realize that this shows a custom menu rendered as a Mega menu (I had already thought so).

My confusion here has to do with:

a) the mention of Admin menu in #0.
b) the issue's title, since I misinterpreted 'Compatibility' (was spelled wrong btw) with 'Support'.
c) the mention of an 'Administration menu' in the module's settings page (please see attached screenshot)

Should have noticed that this is a 'bug report'. Here's a 'feature request' then: #869030: Support for the admin_menu module - a.k.a. convert admin_menu to a mega menu ;)

I was going to install the admin menu to my demo install and then look at mega menu. Interestly, I don't get the Administration Menu Item. I get a Features item.

Interesting indeed!

Do you see this in d6.17? Are you using latest devs of modules? What menus do you see in your menus list (.../admin/build/menu)?

Drupal core 6.17

Administration Menu 6.x-1.5 (I am not using the latest alpha). I installed 6.x-3.0-alpha4 and so now I also get Administration Menu listed in my Menu List and in the Mega Menu interface.

Menu List
Administration menu
Features (Menu items for any enabled features)
Navigation
Primary links
Seconadary links

Some modules with "menu" support like, Administration Menu (some versions) and Features appear in the megamenu configuration menu, see screenshot.

These menus however are not supported by Mega Menu (to my knowledge) therefore are confusing to users. The only options that should be presented are supported menus (currently Primary Links and Secondary Links).

I agree with you Andrew on excluding admin menus (or any menu known to have issues), but only once we have a 'stable' release.

I think for dev versions this exclusion needs to be omitted. The community needs to be able to test with ease and report back any regressions. Perhaps a 2.x dev branch could hold the extra soon-to-be-supported menus, but it is silly to talk of that since we didn't yet reach 'stable'-ish stage in 1.x (not even a 'unsupported' 1.x alpha). So, I guess a 'Only for testing - not supported yet!' help text under each menu entry in the list of menus would suffice for now.

@FilmKnurd: Andrew, please take a look again at the description of that issue. It is a feature request, suggesting that this module should convert Admin menu to a Mega menu, whereas this one is a bug report dealing with any issues that might come up when both modules are installed.

Anyways, if any of the two should be marked as duplicate it should be the other one for two reasons:

- this one has a patch available (...well kinda patch, at post #2) that deals with the issue being reported
- the other is newer (this one was started first)

I agree with you. Perhaps some of the posts here actually belong to the other issue and that does confuse things.

Once this is fixed (by adding the css rule), then I guess there will be no issue and all admin_menu feature-request-related posts will go to the other one. Well... not until any new bug-related issue might come up and this is re-opened ;)

...missed an 'i' there ;)

Corrected spelling.

yea! I put it in the wrong place ;) thanx

The version of Megamenu I checked out the other day (I couldn't get at anything recent without pulling Head from CVS*) does not have this Fix in it. Marking as Needs Work.

* P.S., Please clean up CVS or create a stable release ;)

@FilmKnurd: The zany Feature Request that takes up most of this issue is actually a hijacking. The problem here is a bug report. If you reread the original post it describes the problem I am seeing.

Attached is a screenshot of the out-of-the-box behavior you get when using MegaMenu and Admin Menu. This is what happens as you mouse down along the admin menu. A split second after the cursor floats above the megamenu, the admin menu closes and you are simply on the megamenu.

#2 was addressing this problem.

You say you committed a Fix, but I could not find the fix in CVS. Therefore I have to assume a problem ;)

Unless you can point me to the right tag?

This is definitely a z-index issue with the included skins. It's also present in the 7.x-1.x version as well. I presume, as it's css related that by using a custom skin rather than one of the included ones it will resolve itself, but it seems to me the example skins that come with the module should be updated to fix this issue so that people creating new skins won't run into this problem and then be confused what is causing it.

the megamenu.css sets the z-index of .megamenu-menu .megamenu-parent to 5000 and the z-index of .megamenu-menu .megamenu-bin to 10000. The admin menu has a default z-index of 999. You can force the admin menu to appear over your mega menu by overriding it in your theme's css:

#admin-menu, #admin-menu ul {
    z-index: 10000 !important;
}