Skip to:

Opened 3 years ago

Last modified 9 months ago

#3231 assigned defect

Links to the user profile are broken if bbPress is activated on the child site, and BuddiPress is activated on the network.

Reported by: krioteh Owned by: johnjamesjacoby
Milestone: 2.7 Priority: high
Severity: major Version: trunk
Component: Extend - BuddyPress Keywords: needs-patch


Tested on version bbPress 2.6 RC6 and BuddyPress 3.2 and 4.0 RC1

It is necessary to add a check if the bbPress is activated on the child site, and the BuddyPresss in the network mode is not to integrate these components (leave the standard bbPress profile on the child site)..
Or broadcast all the activity from the child site to the head site of the network.

Change History (9)

#1 @johnjamesjacoby
3 years ago

  • Milestone changed from 2.6 to Under Consideration
  • Owner set to johnjamesjacoby

If BuddyPress is network activated, it expects for all profile links to be pointed at it.

bbPress activity should end up in each profile, but you’re correct that the “Forum” profile section doesn’t include a site picker.

Future versions of WordPres (5.1 and beyond) will make this easier, as provisions exist to more easily identify which sites bbPress is active on.

In the meantime, I’ll think on if there should be a way to omit bbPress forum profiles from BuddyPress’s grasp under certain conditions.

#2 @krioteh
3 years ago

I will clarify:
The problem is that the profile links on the child site in RC6 do not lead to the BuddyPress profile.
They lead to a forum page or topic that is currently open.
In version 2.5.14 they led to the BuddyPress profile.
In 2.6RC5 in profile bbpress.
At 2.6RC6, they are just broken.

#3 @johnjamesjacoby
21 months ago

  • Milestone changed from Under Consideration to 2.6.1
  • Status changed from new to assigned

#4 @johnjamesjacoby
21 months ago

  • Milestone changed from 2.6.1 to 2.6.2

Move these to 2.6.2.

#5 @johnjamesjacoby
20 months ago

  • Milestone changed from 2.6.2 to 2.6.3

#6 @johnjamesjacoby
20 months ago

  • Milestone changed from 2.6.3 to 2.6.4

#7 @johnjamesjacoby
18 months ago

  • Milestone changed from 2.6.4 to 2.6.5

Moving open issues from 2.6.4 to 2.6.5, for 2.6.4 release today.

#8 @johnjamesjacoby
14 months ago

  • Milestone changed from 2.6.5 to 2.6.6

#9 @johnjamesjacoby
9 months ago

  • Milestone changed from 2.6.6 to 2.7

I'm unable to duplicate this right now, but I remember being able to previously.

Moving this to 2.7 so it can get more attention later.

Note: See TracTickets for help on using tickets.