This feature was introduced a long while back, when we still had the concept of everything living in Garland. But now that we have an administrative interface, it does not make sense to have heavy administrative duties living on theme level. Also this item caused a lot of confusion, by many users since you can select this as the menu parent.

My suggestion is to remove this completely from the interface, although it has its purpose its somewhat of a symptom of the menu system interface that is context insensitive.

I believe its a conceptual good move, to remove this item. Since then we won't have administrative action exceptions in the normal interface nor confusion over where to find out what menu's exist.

Comments

Bojhan’s picture

In regards, #503938: Users Set the Parent Menu Item to "Add a main menu item" - would fix the issue of selecting the parent menu item.

clemens.tolboom’s picture

Dan Silver’s picture

just my opinion, but I think that the link is very useful for new users like me.

clemens.tolboom’s picture

@#3 : I said the same to Bohjan@irc but we expect #473268: D7UX: Put edit links on everything will solve this.

yoroy’s picture

We all thought it would be useful. But thing is, it was observed in usability testing that people added new items under this existing link. This adds confusion instead of making things easier. The contextual edit links of #473268: D7UX: Put edit links on everything want to solve this indeed. To be able to test if they do, we should remove this previous pattern that has proven itself to be confusing.

clemens.tolboom’s picture

What if #473268: D7UX: Put edit links on everything does not make it regarding menus? Then we have no improvement :(

yoroy’s picture

Well, that one's a code freeze/slush exception. Does removing this link here constitute an API change?

Bojhan’s picture

Status: Active » Closed (duplicate)