[drupal-devel] [bug] Menu system requires a local task to have more than 1 child in order to create secondary local tasks

Dries drupal-devel at drupal.org
Wed Feb 9 06:18:43 UTC 2005

 Project:      Drupal
 Version:      cvs
 Component:    menu system
 Category:     bug reports
 Priority:     normal
 Assigned to:  Anonymous
 Reported by:  andremolnar
 Updated by:   Dries
 Status:       patch

Well, the problem is that the tracker module can't determine whether to
add the subtask.  It should only be added when another module adds a
second subtask.  I'll explore this some more.


Previous comments:

February 8, 2005 - 23:49 : andremolnar

Attachment: http://drupal.org/files/issues/menu_inc_1a.patch (826 bytes)

This is a minor bug.  The menu system requires a local task to have more
than 1 child in order to create secondary local tasks.  In other words
if a local task only had 1 child, menu system would not create a
secondary local task menu item.
This patch fixes that with the addition of 1 character in the code.


February 9, 2005 - 00:52 : Dries

I'm pretty sure this patch would break some pages.  Some modules have a
tab and a subtab that show the same page.  The tracker page, for
example, relies on the fact that the subtab does not get shown when
there is only one subtab.  However, when there are two or more subtabs,
they are being visualized.  I guess this needs some more thought.


February 9, 2005 - 01:18 : andremolnar

hmmm... Well, I certainly don't think that this should be the expected
behaviour of the menu system.   A child menu item is a child menu item,
and I would expect that it show up if I create that child in hook_menu. 
When patching user.module it took me over half an hour to track down
this bug (a single missing character was easy to over look).
Nor do I personally think that the menu system should accomodate
exceptions of the sort described in tracker.module.  It should be the
module's job to decide when to create a local task in hook_menu using
logic local to the module.
IMHO if applying this 'breaks' modules - so be it.  It would force a
necissary code/logic improvement in those modules.

View: http://drupal.org/node/17022
Edit: http://drupal.org/project/comments/add/17022

More information about the drupal-devel mailing list