WordPress.org

Make WordPress Core

Opened 19 months ago

Last modified 3 months ago

#39056 reopened defect (bug)

Twenty Seventeen: No Default Menu option creates extra work

Reported by: ElfIRL Owned by:
Milestone: Awaiting Review Priority: normal
Severity: normal Version: 4.7
Component: Menus Keywords:
Focuses: Cc:

Description

A new WordPress site is created with a sample post, and sample page. In previous themes, there was a menu with Home and Sample Page listed, which was nice to see where the menu lives, and preview what a page looks like.

On Twenty Seventeen there is no default menu. This prevents me from both identifying where those links would be, as well as not allowing me to view the Sample Page.

Change History (6)

#1 @swissspidy
19 months ago

  • Component changed from Menus to Bundled Theme

#2 @helen
19 months ago

  • Component changed from Bundled Theme to Menus

In Twenty Seventeen, you should see a more fully populated nav menu when customizing a brand new site, which is a bit different than looking at the live view of a new site. I suppose this is a matter of whether there should be a fallback for wp_nav_menu() at the top?

This ticket was mentioned in Slack in #core-themes by helen. View the logs.


19 months ago

#4 @davidakennedy
19 months ago

  • Milestone Awaiting Review deleted
  • Resolution set to wontfix
  • Status changed from new to closed

Hey @ElfIRL – thanks for the report!

This is a design decision, and something that isn't going to change. When a menu is not assigned to either the top menu or social links menu, no markup is outputted and no fallback menu is present. This means users can not have a menu if they don't want one.

As Helen mentioned, you can see where a menu would be on a fresh site when viewing it in the Customizer. Or by assigning a menu in the Customizer and previewing it.

#5 @anmari
9 months ago

  • Resolution wontfix deleted
  • Status changed from closed to reopened
  • Summary changed from Twenty Seventeen: No Default Menu to Twenty Seventeen: No Default Menu option creates extra work

I think this should be re-opened as a bug. If one is happy to use the page structure as one's menu, then one should have the option of a default menu based on the page structure. Currently twenty-seventeen creates additional unnecessary work. After creating pages, one still has to go create the menu structure.

While one can specify that pages should be automatically added to the menu one had to manually create, they are not added based on the page structure. So one has to continually visit the menu editor as well as the page editor. This feels painful and a backward step.

While I understand allowing for the option of no menu, surely it is equally important to allow for the original 'just use the page structure as menu' option? Arguably perhaps this is a menu customiser feature that the themes should then implement.

#6 @SergeyBiryukov
3 months ago

  • Milestone set to Awaiting Review
Note: See TracTickets for help on using tickets.