Opened 13 years ago
Last modified 6 years ago
#20289 new defect (bug)
wp_nav_menu container is not set when menu isn't defined
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 3.3 |
Component: | Menus | Keywords: | dev-feedback needs-patch |
Focuses: | administration | Cc: |
Description
When you use wp_nav_menu in your theme, but the actual menu isn't set via the backend menu interface, the container provided in the args is ignored and falls back to 'div'.
Attached diff always uses container provided in args, if 'div' or 'nav' is provided. If no container arg is provided, falls back to using 'div'.
wp_nav_menu( array( 'theme_location' => 'main_menu', 'container' => 'nav', 'menu_class' => 'main-menu-navigation', ) );
To test this: Use this function in your theme, without assigning a menu to this theme_location.
Attachments (1)
Change History (5)
Note: See
TracTickets for help on using
tickets.
Related: #13998, #18232, #13979, #18842