Top-level components as sub-pages hides them in bp-default tab nav

[boonebgorges]

If you set the WP page for a component as the child of another page, for example if your Groups page is a child of a page called Community, giving it a URL of example.com/community/groups, it does not show up as a top-level tab in the main site nav. Instead, it shows up in the Community dropdown.

Maybe this is a wontfix: If site admins are unhappy with this arrangement, they can (1) use a WP custom menu, (2) modify header.php manually, or (3) move the component page back up to the top level in the hierarchy. But I wanted to bring it to the attention of other devs so there could be a bit of discussion.

[DJPaul]

I vote for wontfix

[r-a-y]

I vote wontfix as well because the site admin is consciously making the decision to put BP Groups as a child page.

[boonebgorges]

Cha-ching!

[boonebgorges]

We should try to remember to add this to the codex somewhere though.