Skip to content

Navigation: Replace default Page List block with Auto add page navigation block setting #85156

Open

Description

@jeryj

The Page List within the Navigation Block either needs a huge overhaul to allow customization, or we should replace it with an auto-add pages option as explored in #84508.

At the moment, a user's first experience interacting with the navigation in an way is met with this confusing, scary message:

Detach Page List
This Navigation Menu displays your website's pages. Detaching will enable you to add, delete, or reorder pages. However, new pages will no longer be added automatically.

It's not a warm welcome. I believe the intention with the page list was to offer an experience where you don't need to interact with the navigation. But, often, you want to reorder or remove an item, which gives you that big warning message.

Rather than add more improvements to the Page List block and fragment the experience further, I think we should default the page list menu to a navigation block with a new setting called "Auto add pages." This way, they get the same benefit of the basic page list without needing to encounter that scary message.

Activity

  1. 369work commented on Oct 21, 2026

    @369work
    Contributor

    Test report

    I tried this on my local site and wanted to share what I found.

    Environment

    • WordPress: 7.1.3
    • PHP: 8.4.26
    • Browser: Chrome 155.0.0.0
    • OS: Windows 10/11
    • Theme: Twenty Twenty-Five 1.5
    • MU Plugins: 99-studio-loader.php
    • Plugins: Test Reports 1.3.1

    Steps

    1. In the Site Editor, open the "Blog Home" template (home.html).
    2. Click the header, then click "Edit navigation" in the block toolbar.
    3. In the right sidebar, click "Edit original" under the header.
    4. In the navigation menu items list, click "Page List" twice.
    5. The message from this issue appears in the sidebar, along with an "Edit" button.

    Results

    • The message did not appear when I simply clicked the menu in the header.
    • It only appeared after the steps above.
    • I've edited navigation menus many times, but I had never noticed this message until now.

    About the wording

    I found the current message a bit hard to understand:

    • The first sentence doesn't say that the menu lists pages automatically.
    • "Editing" doesn't make it clear that the Page List will be converted into regular links.
    • What you lose is added at the very end, after "However".

    Because of this, it reads a little like "don't touch this".

    Current:

    This Navigation Menu displays your website's pages. Editing it will enable you to add, delete, or reorder pages. However, new pages will no longer be added automatically.

    Suggestion:

    This menu lists your pages automatically. New pages are added as you create them.
    To reorder or remove items, select "Edit". The menu will turn into regular links that you can move freely, but new pages will no longer be added automatically.

    If the "Auto add pages" setting replaces the Page List as proposed, this message may no longer be needed. Until then, I think updating the wording alone could make it clearer.

    Image
  2. mikachan commented on Oct 21, 2026

    @mikachan
    Member

    Thanks for opening this, @jeryj! I'm in favour of this. The Page List message is often the first thing people see when they try to change their menu, and I agree this message could feel intimidating to users. An "Auto add new pages" setting keeps the main benefit of Page List, and the menu would stay fully editable. I also like that it matches how classic menus already work, so it should feel familiar to a lot of users.

    Also, I agree that @369work's suggested wording is clearer than the current message. It could be a nice quick improvement for the meantime.

  3. jeryj commented on Oct 21, 2026

    @jeryj
    ContributorAuthor

    Another reason the Page List flow is confusing. Adding a new page via the navigation block with a page list results in duplicate copies of the navigation item.

    • On a Navigation Block with a Page List:
    • Click the Navigation Block Appender
    • Using the popover, add a new published page
    • The page list also displays your new page, so it's in the navigation twice
    Screen.Recording.2026-10-21.at.10.33.34.AM.mov

    With the "Auto add new pages" as a setting on the navigation block, it should be able to tell that the page is already in the navigation and not add a second copy.

  4. jeryj commented on Oct 26, 2026

    @jeryj
    ContributorAuthor

    Maybe this should also handle deleting pages too. If a page is deleted and it's in your menu, then it should also be removed from your navigation block. I'm not sure if it should be on first page deletion or when it's removed from the trashcan entirely.

  5. mikachan commented on Oct 26, 2026

    @mikachan
    Member

    Maybe this should also handle deleting pages too.

    I'm in favour of this, and I think it makes sense to remove the page on initial deletion rather than when it's removed from the trashcan entirely. I wonder if this should also handle pages that are put into draft (after being published) as well?

  6. jeryj commented on Oct 26, 2026

    @jeryj
    ContributorAuthor

    Maybe this should also handle deleting pages too

    Actually, when something in the menu is permanently deleted, it should go ahead and be removed regardless. There's no reason for a user to need to go through all their menus and remove a page they already deleted. This seems like default expected behavior, not reliant on if you have a navigation block setting chosen. I can't imagine a scenario where you permanently delete a page yet still want that page in the navigation.

    So, I'll open a separate PR and issue for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions