The Navbar is a separate module in the theme with its options in
navbar-options.php. It is typically used in the Header but it could be placed elsewhere. It is built using the WordPress
The first option for the Navbar chooses between having eight fixed width buttons or allowing the size to vary with the size of the button text.
The second option gives the option to display thin arrows (→ ↓) or thick arrowheads (► ▼) alongside pages that have 'children'.
The third option specifies the number of levels of the page hierarchy to show in the Navbar. It is actually used to specify the
depth= to the
The next six options further control the way the menu is built using the
wp_list_pages() function. They allow pages, or hierarchies of pages, to be hidden from the menu. There are two that apply all the time, two to exclude extra pages when there isn't a user logged in, and two more that exclude extra pages when there is a user logged in. The values entered are used as the
exclude_tree= arguments so should be comma separated lists of numbers. WordPress doesn't prominently display page numbers but you can typically find them by going to the Pages menu in the dashboard and hovering over the name of the page. Your browser will normally show you the URL the name links to and that includes the number of the page (e.g.
In theory the
exclude= option should exclude individual pages by ID and collapse the hierarchy underneath them, and the
exclude_tree= option should exclude the pages and also all those in the hierarchy underneath them.
Prior to WordPress 3.9.0
exclude_tree= had a longstanding bug where it only worked with the first ID listed. However
exclude= also had a bug where it behaved like
exclude_tree= is meant to if a
depth= argument is used (which it is in the theme). So prior to 3.9.0 excluding more than one hierarchy from the Navbar was only possible by exploiting a bug in a WordPress function.
exclude= bug remained in WordPress meaning hierarchies could not be collapsed in the theme, though whether you would want to do this is another matter. The outstanding bug was reported (by me), confirmed by developers, and a patch created for it. The original defect report doesn't indicate that the patch was ever applied to a release, so it is possible the bug remains.
The next six options select the background colour for the three levels of the Navbar. For the first level the default background is Scout Teal, changing to Scout Purple when highlights. For the second level the colours are Scout Green and Scout Navy, and for the third level the colours are Scout Red and Scout Pink. The foreground colour is always white.
The remaining option is for the colour of unused 'slots' in the top level of the Navbar. The default is Scout Teal to give a solid bar across the page. It is worth mentioning that choosing white is also quite reasonable for the empty slots as then there is an empty space between the main menu and the 'Login' / 'Logout' button (if it is used). So you get a different look.
The next two options control whether the 'Shop' menu entry is shown and allows the URL to be specified. The default is to show a Shop entry and link it to the Scout Store (formerly known as ScoutSHOPS). The 'target' attribute is no longer deprecated in HTML so the theme lets you specify one (e.g.
_blank) if that is how you like to do things.
The next options control whether the 'Login' / 'Logout' entry is shown in the menu and which background colours to use for it. The default is to show it with a background colour of Scout Purple and a highlight colour of Scout Green (the reverse of the default colours).