In 6.x, menu names and node titles are separate fields. They are probably identical the vast majority of the time, so this makes us manage duplicate data. This is pointless complexity that hurts usability.

The node title is the authoritative record since it's closest to the content it describes. The menu is auxiliary to the node, so it should reflect the node title. The menu name should only be different if the site admin intends it.

The logic that implements this must not be exclusively client side and must not depend on usage of the node edit form. Otherwise API-based changes of the node title will not affect the menu name. (That distinguishes this from #410464: Menu name = node title upon node edit through user interface.)

These are related but not the same:

Comments

aren cambre’s picture

aren cambre commented

A complete solution ought to:

  • Use the node title if the menu title field is blank.
  • Reconstrue the menu title field's UI as "only fill this out if you don't want to use the node title."
  • Be implemented on the server side.
  • Will only have client-side logic (JS) as an adjunct to a fully-implemented server side solution, although I see no need for JS if the prior points are implemented.

This issue was created as an alternate solution to #410464: Menu name = node title upon node edit through user interface. See comment 50 for more details.

aren cambre’s picture

aren cambre commented

This should be implemented alongside #576916: Default menu "Parent item" should be Navigation, not Primary links and #322703: Use on/off checkbox to enable node's menu item (see #410464: Menu name = node title upon node edit through user interface comment #51).

This change improves the lack of a toggle: right now you turn on a per-node menu item by putting text in Menu link title and turn off by 1. checking Delete this menu item. and 2. clicking submit.

These three issues will convert per-node menus into an intuitive, one-click "it just works" feature.

sun’s picture

sun
Primary language German
Location Karlsruhe
commented

Honestly, I think that the solution over in #322703: Use on/off checkbox to enable node's menu item is sufficient. That makes it work totally intuitive for 99% of all users (i.e. except those without enabled JavaScript).

aren cambre’s picture

aren cambre commented

It creates a different UI interaction for handling a menu item name change when the node's title is changed. There is a big complexity difference between the two interactions.

sun’s picture

sun
Primary language German
Location Karlsruhe
commented
Component: menu system » menu.module
aren cambre’s picture

aren cambre commented

And problem with #322703: Use on/off checkbox to enable node's menu item is it doesn't gracefully degrade if one doesn't have Javascript working.

xjm’s picture

xjm
she/her
Primary language English
commented
Title: Menu name should be node title by default » Menu item name should be node title by default
Bojhan’s picture

Bojhan commented
Status: Active » Closed (fixed)

This is already in core.