Config pages are effectively hardcoded to some subcategory of 'admin/config'

Created on 30 September 2009, over 15 years ago

Updated 25 March 2025, 20 days ago

We're currently hard-coding the menu path of a module's configuration page to a specific, often subjective, parent category page.

The problem is best described by webchick in #34:

Currently, your only option is to hook_menu_alter() the path from admin/config/development/XXX to admin/config/butterfly/XXX. But when you do that, suddenly all of your help text/drupal_set_message() links are broken, the tests (which are all pointing to the default path) no longer pass, etc.

Original post:

I'm sorry. I predicted this fact already, but no one wanted to listen.

I'm trying to port http://drupal.org/project/compact_forms to D7 as part of my personal D7 porting effort.

But.

There is no suitable category.

A suitable category would may be "User interface".

But that does not exist.

My little module has, as of now, 609 users.

It doesn't make sense for a module like that to define a new "category".

The "expected" result is to have 4,000+ Drupal modules to define their own "categories".

Core is not able to pre-define the categories.

We already know that. And we really should have learned from admin/build/modules.

I mentioned exactly that before.

The thinking is 2D.

The reality is 3D.

📌 Task

Status

Postponed: needs info

Version

11.0 🔥

Component

menu system

Created by

🇩🇪Germany sun Karlsruhe

Live updates comments and jobs are added and updated live.

API change
Changes an existing API or subsystem. Not backportable to earlier major versions, unless absolutely required to fix a critical bug.

API clean-up
Refactors an existing API or subsystem for consistency, performance, modularization, flexibility, third-party integration, etc. May imply an API change. Frequently used during the Code Slush phase of the release cycle.

MenuSystemRevamp

Needs issue summary update
Issue summaries save everyone time if they are kept up-to-date. See Update issue summary task instructions.

stale-issue-cleanup
To track issues in the developing policy for closing stale issues, [Policy, no patch] closing older issues

Incomplete comments

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Comment 20 days ago →
🇺🇸United States smustgrave
Thank you for creating this issue to improve Drupal.

We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.

Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

Thanks!

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024