BuddyPress.org

I’m usind PmPro, BuddyPress and bbPress on my website.

I would like to create 4 separate, private forums, each one requiring a separate membership level for access. All information pertaining to group members should be absolutely private — not only for non-logged in users but also for users who are not part of the respective group.

I’ve done a lot of research and know how to hide member profiles, activity page, etc from non-logged in users in general.

But how can I achieve the same effect for non-logged in users of specific forums?

I’m so sorry if I’m missing something — I’ve spent days researching this.

Thanks so much,
Kat

Hello,

I encountered an issue with Buddypress group slugs in foreign language.

When a user registers a BP group with a non-English name then the slug for this new group is created using %-encoding and lower-case characters like mysite.com/groups/%d1%80%d0%be%d1%81%d1%81%d0%b8%d1%8f/

The issue happens when some user agents and Google in particular are trying to access this URL.

When I try to fetch this URL as Googlebot from my Google Search Console, I see that Google is trying to access this same URL using upper-case characters like this:
mysite.com/groups/%D1%80%D0%BE%D1%81%D1%81%D0%B8%D1%8F

The response Google is getting is:

HTTP/1.1 301 Moved Permanently
Location: mysite.com/groups/%d1%80%d0%be%d1%81%d1%81%d0%b8%d1%8f/

But unfortunately Google is not following this redirect.
Apparently Google thinks that the URL is redirecting to itself and stops indexing it.

1. Does anyone know a solution for this issue?
2. Is’n it making sence to make Buddypress treat such URLs as equal and respond with a proper 200 response instead of 301-redirecting?

Buddypress behaviour in this case is quite different to how WordPress is handling this same problem. In the case of Worpress requesting a %-encoded URL always produce a 200-response regardless of the case.

Thanks a million in advance!
Anton.

Hi!
We’ve found a bug and we’d like to notify you about it.
Slider Revolution 5.2.5 + BuddyPress 2.5.2 + bbPress 2.5.8 shows next notices:

Notice: bbp_setup_current_user was called incorrectly. The current user is being initialized without using $wp->init(). Please see Debugging in WordPress for more information. (This message was added in version 2.3.) in wp-includes\functions.php on line 3901

Notice: bp_setup_current_user was called incorrectly. The current user is being initialized without using $wp->init(). Please see Debugging in WordPress for more information. (This message was added in version 1.7.) in wp-includes\functions.php on line 3901

Best regards,
Maksym

Hi all,

This “trick” is intended to allow certain WP user roles (like Admin or Subscriber) to create groups while preventing the rest, and it is intended for installations based in WP4.5 and BP2.5.2. I cannot assure it works for other versions.

NOTE: As a BP plugin file will be modified, the trick will not survive BP updates.

1) Make sure that users cannot create groups by default (Settings -> BuddyPress -> Options).

2) Choose the users that you want to enable (to create groups). Get the list of WP capabilities for each of them from here (or use a role/capability editing plugin):

https://codex.wordpress.org/Roles_and_Capabilities

Choose one capability which is only shared by those users that will have the ability to create groups.

For example, if you want WP roles Contributor, Author, Editor and Admin to have the ability to create groups but you want to exclude Subscribers, then choose “delete_posts” or “edit_posts” as your differentiating capability (they all -but Subscriber- can “delete_posts”).

Combinations of custom Roles and Capabilities also work. In my case, I am using s2member Roles and Capabilities (i.e. “access_s2member_level2”).

The choosen capability will be called my_choosen_capability beyond this point.

3) Then, edit /path/to/your/installation/wp-content/plugins/buddypress/bp-groups/bp-groups-template.php. In line 4312 you will find the following function:

function bp_user_can_create_groups()

After the if structure that enables Admins to create groups regardless the settings, add this:


if(current_user_can('my_choosen_capability')){
return true;
}


In my case as my_choosen_capability = access_s2member_level2, the code looks like this:


if(current_user_can('access_s2member_level2')){
return true;
}


Then save and enjoy till next update.

4) When the enabled users visit the group page, two buttons will be printed:

-Join group
-Create group

This is it. Have fun!

I have been using the theme “Flatsome” with BuddyPress Groups fine for several months now. However, when I switch to the very popular theme “Bridge”, I can no longer see my list of groups. I just see a blank page.

I cannot understand why BuddyPress Groups would not be compatible with such a very popular theme such as “Bridge.”

Any help would be greatly appreciated.

Thanks,
John

A while ago I created a field in my registration page called “country” so user in my buddy press install would write their country. That was really badly planned as people are writing their country name in different forms. I want now to replace that field with a dropdown menu and my question is: if a remove the existing field from the registration page, would I delete also all the information on the database? Many thanks.

I am using the latest WordPress and buddypress versions.

Hello I was wondering if it is possible to assign the author of a blog post to a buddypress user? It seems only admin or editor members appear as options in the author drop down of a blog post.

Any help would be really appreciated.

Thank you

Hello BP community,

We are experiencing an issue with the email notifications buddypress is sending to our forum members. This is the link I mean that was sent by bp:

The problem is, the link is not working. When clicked it only redirects to the main website. I also tried to click the link when logged-in but still the link doesn’t work and still redirects to the main website.

This happened when we updated to BP 2.5.2. We are running WordPress version 4.5

Mark