With the furthering of functionality AND flexibility in Omega... The following issues have arisen:

  1. As discovered by most theme maintainers, managing a custom dropdown/hierarchical menu is problematic.
  2. Drupal core and contrib modules like Context don't easily support a full menu tree for primary navigation.
  3. For fully functional dropdown menus and integration, it's best to rely on contributed modules

With the above in mind, (and there are MANY more related issues throughout contrib and core related to menus) Omega will be phasing out support for ANY advanced menu functionality built directly into the theme layer.

This presents a couple of issues:

  • The original/current implementation of dropdowns in Omega must be preserved in order to not break any existing functionality in current subthemes from users, and for the Gamma Theme
  • Maintaining multiple options for menu rendering

With this stated... Omega will be handling menus in the following way in the upcoming Beta4 release (after Git migration is complete)

For subthemes that have already been created, Omega will respect the original settings and render the dropdown menus. (screenshot)

For new subthemes created from the HTML5 or XHTML starterkits, the default option will be to render traditional Drupal menus. (primary and secondary nav) (screenshot)

The option will exist to disable ALL menu items, and place either the core Drupal menu blocks, or use a contributed module to create primary navigation/dropdowns. (as in the screenshots attached, we can see this is actually the "recommended" option)

Also, in new subthemes, the branding (logo/site title/slogan) region is now a REAL region, as well as the menu region, which were "faked" regions previously. This should not affect any existing sites, unless you have customized the region--branding.tpl.php or the region--menu.tpl.php templates provided in Omega core. The branding zone, which contains the branding and menu regions will act/react the same for sizing and placement, but now in addition to rendering the custom data for those regions, will also allow for placing ANY blocks in those regions.

Comments

himerus’s picture

Status: Active » Fixed

Fixed in stable 2.0 release.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.