July 2012: 7.x-2.x branch with new features: Language switching, Masquerade, and jumping between staging/production/test sites !!
The original Administration Menu module has become a lot more powerful in recent months. Some of the special features of DQX AdminMenu are no longer as unique as they used to be.
The consequence might be that at some point this development on this module will stop.
Alternative to Administration Menu with added:
- "Directional Hover Intent" based on vertical/horizontal mouse move direction, as we know it from desktop-based menus.
- Find-as-you-type: Type a letter to find menu items more easily, even in submenus that are currently not revealed. Note: Latest versions of admin menu also have a tree search, but it behaves differently.
- Inline submenus for a lot of things. Saves you one level of depth.
- No-access visibility: Submenus being shown even if the user has no access to the parent item.
- Switch language, directly from the menu.
- Jump between staging/production/test sites, directly from the menu.
- Immunity to things like #550254.
Features shared with recent admin_menu (but different feel or implementation):
- Client-side cache for faster page loading. Both modules have this for a long time now.
- Masquerade as a different user, directly from the menu. Recently added independently in both modules.
- Powerful API to add your own items and submenus, make submenus inline, etc. (*)
These features have a cost:
- No manual reordering or adding/removing of menu items via the admin backend.
- No explicit IE6 support. IE7 going to be dumped any time. You are the admin, get a browser!
- The PHP code has little in common with the original Administration Menu module.
- Disable admin_menu, if you have it installed. Remove if you want. Also disable toolbar and admin menu toolbar.
- Requirements: X Autoload and PageAPI. Since 7.x-2.x, also Administration menu itself is a requirement!
- Install/enable dqx_adminmenu.
- Recommended: Masquerade.
Unlike Administration Menu, DQX AdminMenu does not use the menu_links system, but fetches directly from menu_router instead. This has a few consequences, some of which are already mentioned above.
Further explanations have moved here, to clean up this module page: