Its not a BP component, its actually a page under the page post_type.
I’ve now got my code working, it was conflicting with the BP custom profile menu plugin (or vice versa). After disabling that plugin and applying the suggestion as provided by Shane, it now works.
However when using the BP custom profile menu plugin, whatever pages were added (as per the normal WordPress Menu system) would correctly load themselves upon navigating to said URL.
With the manual method I am using above, the URLs do 404 on me.
So using the screen_function callback I can run a query for the page named account – which is fine, happy to do that.
But I’d like to know whether there is a particular method I need to apply (rewrite rule) to have the links work (navigate to their permalink destination) without having to use the screen function?
Anyway, for now thanks for the assistance and to Shane for providing the insight I needed to get this working correctly.
I tried adding the screen function with an empty test function to no avail. If I change the slug to $bp->profile->slug then the Sub Nav item appears as a sub item of the Profile Parent tab but seems not to work with my custom added “TEST” parent.
It seems like its a slug issue, but whether I am declaring,
‘slug’ => $bp->account->slug
or ‘slug’ => ‘account’
…it still doesn’t seem to take. When I dump the $bp global varaible, I can see my parent menu item exists as it should, so that doesn’t seem to be the issue. Thanks for your input thus far.
