Closed (duplicate)
Project:
Drupal core
Version:
7.x-dev
Component:
menu system
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
24 Feb 2009 at 23:29 UTC
Updated:
9 Aug 2010 at 19:50 UTC
Jump to comment: Most recent file

Comments
Comment #1
yoroy commentedActually, the current Navigation block has the account name as the title. Let's put it in there as well. Bonus points for making that a link to 'my account' (and lose the explicit 'my account' one)
Comment #2
catchSubscribe. I'm never user about the "Welcome, [my name linked]" - sort of like the 'my account' link, but otherwise a massive +1.
Comment #3
sun+1, much better than rushing #273137: Split Navigation to User and Administration menu in.
Comment #4
yoroy commentedI guess this technically would be creating a new core block that is enabled by default?
Comment #5
catchWould either be a new menu (and hence block) or we'd need to use primary/secondary links for it.
Comment #6
Frando commentedNo, let's not use primary/secondary links - this would be quite confusing UI wise IMO. Instead, I'd vote for a new block, enabled by default. Oh, and +1 on the idea.
Comment #7
gaele commentedRe #1: So that would be <Username>, Help and Log out?
That's great. It's almost like sun's admin_menu ;-)
Steve Krug calls these Utility links. They are not navigation links, so they would need a new menu.
Comment #8
Noyz commented+1
For as long as I can recall, these are called "global navigation links"
Comment #9
catchIf we don't make these into a new menu, then they'll need to be hard coded into the theme (or a hook_block()) - neither of those two options fill me with joy.
I'd suggest something along these lines, there might be a cleaner way to do it which is passing me by though.
1. Add a new default menu called 'global navigation links' / 'utility links'
2. Move these links into that menu
3. Add a template for block-menu_utility or whatever it is inside menu.module to get it inline.
4. Add a region to all core themes with the right placement, and enable the block in that region by default.
Comment #10
beeradb commentedThis idea is totally awesome. Although initially I was thinking these should use the secondary links, I'm thinking we should actually be getting rid of the magic associated with primary/secondary links, not adding more items (by default) to them. At this point I think catch's suggestions sound most sane, these should go in a block and be placed the same way (nearly) all other elements in Drupal are.
Comment #11
sunKick-start.
Comment #12
pwolanin commentedI think the implementation should be to split out all the admin links to a separate menu, and then make the existing navigation menu be the source for the primary and secondary links. Wed' need to fix this too: http://drupal.org/node/279399
Comment #13
wretched sinner - saved by grace commentedComment #14
johnalbinFirst, some background: I hate the $primary_menu and $secondary_menu variables in page.tpl. They're not configurable enough and the current secondary menu's configuration is confusing. Optionally allowing "secondary menu" to mean the second level of the "main menu" means IRC headaches. And you can't move those variables around on the page without modifying the page.tpl. They should be configurable blocks that you can move around on the page. Just like the "navigation" menu block is now. I'm going to write a patch for that soon. (menu_block.module in core essentially)
So… (now that you know where I'm coming from) I like catch's suggestion in #9. Those user links could also just go into the "secondary menu". Then, at least, people would understand what we mean by "secondary menu". But I'm fine with them in a new menu or with them in "secondary menu".
Comment #15
sunYes, Menu Block will essentially replace primary links and secondary links.
However, the links affected by this issue are rather statically displayed user links on all pages and not related to primary/secondary links, and should go into a new menu.
Comment #16
pwolanin commentedDiscussed with catch, noyz, JohnAlbin today - the conclusion was that we should put "Create content" and all admin links in a separate menu, and then put the remaining navigation menu into the secondary links.
Comment #17
sunThen I can only guess that all of you overlooked the fact that all kind of modules add their non-administrative items to the Navigation menu. It is the default menu for all menu router items. Which means it holds more than "Create content", "Administer", and the items that have been proposed to move out of it in this issue.
Thus, altering the purpose of the Navigation menu would require substantial changes to the entire menu router item handling, which was not changed for quite some major versions of Drupal.
Comment #18
catchpwolanin, sun - I thought we'd agreed to put My Account, logout etc. in secondary links and then another patch to move create content and administration from Navigation - but then leave Navigation itself as an empty dumping ground for random links for the moment.
Comment #19
sunMoving them into secondary links would require to remove the special handling for primary/secondary links first. Why all this scope creep? Why can't we just do what this issue suggests (and everyone agrees with AFAICS) ?
Comment #20
yesct commentedI'm not a big name, but from a moderate admin / user point of view ..
+1 to move help logout to a new block, enabled by default, at the top in the core themes.
+1 also to the other issue/idea: moving the admin menus into their own block (enabled by default)
+1 to leaving the navigation menu the dumping ground
I don't think these two issues need to involve primary or secondary menu magic.
Comment #21
yoroy commented#20 Summarizes things best imo. I too see no reason to use primary/secondary menu magic for these.
Comment #22
pwolanin commentedhttp://drupal.org/node/273137
Comment #23
emmajane commentedRelated follow-up discussion taking place in #410646: "Secondary menu" exists but is no longer the default source for the secondary links