Thank you both for the screenshots!
I had a plugin called “Exclude pages” to hide selected pages from navigation (not from menus)
In many cases, “menus” and “navigation” are the synonyms, so that makes sense as a source of part of the issue. It now sounds like Dyad is using its default menu and listing all of your pages. That indicates that while you have menus set, they aren’t being loaded.
The fact that you are now seeing the default menu as well put you in what looks like the same position as @mikeenz.
Now that your symptoms match more closely, I was able to find the problem – the menu ID being registered is different than the one being called by the header.
I’ve put together a child theme you can install as a workaround, and I’ll open up a bug report so it can be fixed directly.
When you visit that link for the child theme, use the Clone or Download button and choose the Download ZIP option. Then install and activate like a normal theme.
https://cloudup.com/cArUiawsXh0
@communitymanagerjugavi – depending on how you’ve implemented the extra menus you’re using, you may need to make adjustments. If you’re using a child already, here is the function I’ve used to remove the current menu and register one with the right name:
function dyad_2_menu_fix() {
unregister_nav_menu( 'menu-1' );
register_nav_menus( array(
'primary' => esc_html__( 'Primary Menu', 'dyad' ),
) );
}
add_action( 'after_setup_theme', 'dyad_2_menu_fix', 12 );
Give that a try and let me know how it goes – we’ll also post here when the parent theme is updated!