Skip to:

Opened 13 years ago

Closed 13 years ago

Last modified 13 years ago

#2998 closed defect (bug) (wontfix)

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

Reported by: boonebgorges's profile boonebgorges Owned by:
Milestone: 1.5 Priority: major
Severity: Version:
Component: Core Keywords:


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, 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.

Change History (4)

#1 @DJPaul
13 years ago

I vote for wontfix

#2 @r-a-y
13 years ago

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

#3 @boonebgorges
13 years ago

  • Resolution set to wontfix
  • Status changed from new to closed


#4 @boonebgorges
13 years ago

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

Note: See TracTickets for help on using tickets.