Since the primary links have the "expanded" option, it might seem to "not work" for the end user as the primary links can be displayed either as a block, and in that case the primary links are shown in their complete hierachical relation, or as a theme element where it doesn't work since only the first level of menu is shown. It however works when the menu is selected. There is no quick hack possible since the "primary links" are generated by menu.inc, not the module menu.

Comments

ultimateboy’s picture

ultimateboy commented
Version: 6.x-dev » 7.x-dev
Category: feature » bug

Agreed. With a quick search I found many people with this problem. I think that we should either allow primary menu items to be expanded or remove the option through the UI.

This could be considered a usability issue, but I will keep it as a menu component as I feel it is a better fit there.

alexanderpas’s picture

alexanderpas commented

+1 for option removal from that place, we need to have a non-expanding menu-block instead.

ultimateboy’s picture

ultimateboy commented

I think there is a better solution.. I think that instead, we should allow expanding on primary menus.. if we want to take it one step further, lets add a dropdown menu system to core themes (of course with the option to turn on/off). It seems like this is an extremely requested feature, and with the little css/js it requires, it is almost so crazy not to.

derjochenmeyer’s picture

derjochenmeyer commented

I like version #3

marcoBauli’s picture

marcoBauli commented

This is a long-time usability bug, also for the styling of menus:

a. theme primary links do not show child menu items in an "expandible" fashion, but have granular <li class="..."> classes for deep styling
b. block primary links support expandible child items, but have generic classes that do not help designers get what they want

(just google a bit about "style drupal menu" to see yourself)

A really useful module to fix this is the Menu Block module - http://drupal.org/project/menu_block - but do we really need to install an extra module to get there?

AdrianB’s picture

AdrianB commented

This is indeed confusing. Subscribing.

alienzed’s picture

alienzed commented

needs work imo, there's no reason why the primary links block or ANYTHING in Drupal should be so difficult to customize.

ultimateboy’s picture

ultimateboy commented
Version: 7.x-dev » 8.x-dev

I'm thinking this has to be pushed on to 8.

David_Rothstein’s picture

David_Rothstein commented

See also: #503810: Convert primary and secondary menus to blocks

asb’s picture

asb commented

Yes, this is a recurring issue for years. Subscribing.

ndmaque’s picture

ndmaque commented

subscribing

NROTC_Webmaster’s picture

NROTC_Webmaster commented

I think this has the best chance of fixing this if anyone wants to take on the necessary changes.

http://drupal.org/node/474004

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

pameeela’s picture

pameeela commented
Issue summary: View changes
Status: Active » Closed (duplicate)
Issue tags: +Bug Smash Initiative
Related issues: +#1869476: Convert global menus (primary links, secondary links) into blocks

Went on a bit of a ride through a related issues loop, but ultimately I believe this was fixed by #1869476: Convert global menus (primary links, secondary links) into blocks.