Administration menu is about to be enhanced with per-module "per-admin-entity" sub-menu-trees over in #420816: On-demand loading of dynamic paths and local tasks #1

...effectively bringing back admin_menu's functionality from D5, where you had direct + immediate access to individual content type administration pages (even fields), menus, etc. Most probably going to be enhanced by an on-demand loading mechanism in a second step.

With that functionality, admin_menu would be able to build the required information like this module is doing. However, slight difference: It would work for everything. :)

Comments

markus_petrux’s picture

markus_petrux commented
Status: Active » Postponed (maintainer needs more info)

I'm aware of the task in the Admin menu queue, and I'm fine adding the feature provided by this module to Admin menu, though I'm not sure what can I do from here right now.

In fact, the links this module provides are already present in the Admin menu, but too deep in the tree. The idea behind this module is to provide a quicker way to switch pages related to the current content type being administered. This is actually provided via a select box next to the menu tabs. Maybe ti could be provided as an extension to the admin menu, as a plugable widget that provides that select box. The problem I see here is that the admin menu could be wider enough to cause the admin menu bar to wrap.

sun’s picture

sun
Primary language German
Location Karlsruhe
commented

coolio - I actually meant to merge the UI as is, but make it integrate with the new hook_admin_menu_map(), which basically delivers all admin entities for a certain context. (I'm working on that patch right now)

The context would actually just be $_GET['q'] or resp. the tab_parent or tab_root of $_GET['q'], which can get quite granular:

- on admin/structure/types/manage/%node_type + sub-pages we'd get a list of other content types to jump to.

- on admin/structure/types/manage/%node_type/fields/% + sub-pages we'd get a list of other fields of the content type to jump to.

Or not, definitely needs UX investigation :)

On deeper paths, we could even expose multiple jump menus to jump to the same sub-page for another admin item... although that could lead to 404s, because not all sub-pages may be available for all admin items ;)

EDIT: But then again, hook_admin_menu_map() already provides us the info whether a (dynamic) sub-page exists for other admin items! :)