Would appear lots of times after disabling and uninstalling a module, the menu items remain under Navigation. Would be useful to have some 'housecleaning' where such menu items are reassigned from module 'system' to module 'menu' to allow for deletion. May be a better way of accomplishing this but have not come across it.

Comments

donquixote’s picture

donquixote CreditAttribution: donquixote commented

I have a local version which shows "dead items" for any menu. That is, items where the router path has become invalid, or the user has no access.
Your feature request is a bit different.

Question: Do you actively use the navigation menu?

donquixote’s picture

donquixote CreditAttribution: donquixote commented

And in theory, the core menu.inc should take care of this itself, or not?

polskikrol’s picture

polskikrol CreditAttribution: polskikrol commented

Would think the core menu.inc should take care of this, however, dont think any updates will be done to core modules in Drupal6 anymore (I can be mistaken).

Maybe its the same issue as described in #1 since I try to delete the menu item (which has been orphaned as the module no longer exists which created it) by modifying 1234/edit to 1234/delete but receive a permission denied even though I am logged in as user 1.

Use the Navigation Menu with DHTML for all admin tasks and admins use it to post new content. Recently have been organizing items into groupings such as 'Security' placing Secure Pages, etc modules in there. Noticed a few menu items which should no longer be available and clicking on them gives a does not exist error page. (On a side note, does this module support creating 'folders' for groups of items without requiring a path? Thus, adding a new Menu Item as a parent for other child items would not be clickable.)

apaderno’s picture

apaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
CreditAttribution: apaderno as a volunteer commented
Issue summary: View changes
Status: Active » Closed (outdated)

I am closing this feature request, as it's for a not supported project version. If you want to see this feature implemented for a supported project version, please re-open this issue.