Shouldn't the menus depend on the theme rather than the site?

Or better, leave the global menu and let themes override it through the specific theme configuration if needed.

Another - probably easier to implement - possibility would be to be able to assign a default top menu for a theme among menus created with the global menu system. A bit like with blocks which are available throughout all sites but can be added or not to each time.

This second possibility might be feasible for a 5.X release in my humble opinion.

Implementing this feature would allow:

- easier multi-site menu management without having to prefix the menu tables of the database
- possibility to provide different features to the site for each theme

With Drupal 5, we can already do multi-site wuthout table prefixing by using Views and site specific themes. The only problem for those doing this are menus. For the moment we have either to prefix the menu-related tables or to hard-code menus.

Comments

neural’s picture

"throughout all sites --> "throughout all themes" I meant.

But it's correct when speaking of using themes for a multi-site configuration ;).

stevenpatz’s picture

Version: 5.x-dev » 6.x-dev

Features go in HEAD

mdupont’s picture

Status: Active » Closed (fixed)

There are now many ways to deal with theme-specific menus and multisites in recent versions of Drupal (menu block, context, etc), so I amclosing it as it is no longer valid.