[buddypress-trac] [BuddyPress Trac] #7871: defined BP_DEFAULT_COMPONENT is not honoured when BP Nouveau is active
buddypress-trac
noreply at wordpress.org
Fri May 25 14:07:14 UTC 2018
#7871: defined BP_DEFAULT_COMPONENT is not honoured when BP Nouveau is active
-------------------------------------------------+-------------------------
Reporter: sbrajesh | Owner: (none)
Type: defect (bug) | Status: new
Priority: normal | Milestone: Awaiting
| Review
Component: Templates | Version: 3.0.0
Severity: normal | Resolution:
Keywords: reporter-feedback 2nd-opinion has- |
patch |
-------------------------------------------------+-------------------------
Changes (by imath):
* keywords: => reporter-feedback 2nd-opinion has-patch
Comment:
Hi @sbrajesh
Thank you for your feedback. Actually BP Nouveau is honouring this
constant the same way BP Legacy does. You think the opposite because by
default Nouveau is using the custom front page feature. If you deactivate
this setting from the customizer (see the screencapture below), you should
see the Profile nav is the default component.
[[Image(https://cldup.com/sU4O28bjiu.png)]]
Alternatively, if you add a {{{front.php}}} template in {{{bp-
legacy/buddypress/members/single/}}} (or in a theme's
{{{buddypress/members/single/}}} folder) you'll see that BP Legacy is not
using the constant to set the landing page.
So I have a suggestion : edit this ticket as an enhancement so that we
remove the restriction about the first nav item of the primary nav into
the reordoring panel of the customizer, this way we could land on profile
and have it at the first position if the custom front is disabled (see the
screencapture below). I don't see any trouble about doing this ;) What do
you think @hnla ?
[[Image(https://cldup.com/tFrWNrAMy0.PNG)]]
7871.patch is removing this restriction.
--
Ticket URL: <https://buddypress.trac.wordpress.org/ticket/7871#comment:1>
BuddyPress Trac <http://buddypress.org/>
BuddyPress Trac
More information about the buddypress-trac
mailing list