BuddyPress.org

Common usage

To get automatically a buddypress translation for your site, you have nothing special to do, except setting up WordPress to a custom language.

Note that the language should exist on GlotPress and must be completed to 100%.
https://translate.wordpress.org/projects/wp-plugins/buddypress

In this case, which is default situation, the translation will be automatically uploaded to wp-content/languages/plugins/

For each new BP version (at least any major releases), you will receive the latest translation available. And the existing po/mo files are then overiden.

Custom usage

If you use a custom translation, you have to protect your work from automatic updates which continues to work. To do that, you need to create a buddypress folder in the default location:

wp-content/languages/plugins/buddypress

Once this location exist, it receives priority when a new translation is available. From this point, you continue to receive the translation in the new directory and you can store your custom version in the first directory wp-content/languages/plugins/.

This is how it works actually for BuddyPress. Will perhaps be modified in the future. But no idea when and how.

There is no plugin for that. If you have subdomains, you should setup your host so it can work with subdomains…
If it is allowed by your host, you can setup a wildcard.
And your network will be namrezi.org, with sub-domains like blog1.namrezi.org, blog2.namrezi.org
and your users can then create their own blog inside that network.

Read here https://codex.wordpress.org/Configuring_Wildcard_Subdomains

How can you have define(‘MULTISITE’, true); if you have NO multisite and 13 subdomains if subdomain install is set to false ?

Please read attentively here: https://codex.buddypress.org/getting-started/installation-in-wordpress-multisite/

Hi,

thank you for reporting your thoughts. But the mentionned warnings are very generic, and more important, related to vulnerabilities listed by WPScan Vulnerability Database. It gives you an information, but you have to investigate more about it when you get some alerts.

But before you get in panic, check WPScan and one or two other service, to confirm. In 2016, such informations are also relayed by social networks. If you find nothing there, you’re probaby not concerned, even if the plugin let you know about a defection. 🙂

In your examples, the first message is related to a step cookie using json, and the second mention a deprecated function. This doesn’t mean it is bad or dangerous, but that it is no more used or mostly because it will be removed in a next version. Until, it continues to work.

Once reported by WPScan, the plugin relies a vulnerability on your site. That’s fine, but doesn’t mean the vulnerability affected your site, or even that the vulnerability wasn’t already solved. For example you will see that BuddyPress isn’t reported on WPScan. And the 2 vulnerabilities reported for bbpress (in 2014 !), where both solved in version 2.0. FYI, latest stable version of bbpress is 2.5.8

By experience, i can tell that most of WP vulnerabilities and sister projects like BuddyPress, are actively handled in a few hours after they have been reported.

It’s important to be concerned by security, but it’s also important to know about security (not only trusting to a plugin) and very health savy, to not to sink into paranoia. 😉

A first step into WP security would be to read here.

As best practice advice: contact directly the devs when you are aware about a vulnerability. Don’t give any public information or details about it (to avoid replication) and stay discreet, at least until you received some official instructions.

Of course you can also mention all this to the devs here: https://buddypress.trac.wordpress.org/report

If your WordPress is correctly declared as multisite and is network activated, no, there is no other blog setting inside BuddyPress.

In the network admin menu, you normally have two network items under Settings:
network setting and network setup.

What do you see in the first box of network setup ?

@noahboddy BuddyPress is compatible with nearly all WordPress themes. Checked out the source code of your theme’s page.php. It’s clean and should work with BP. So in all probability, the conflict could with another plugin. Good luck.

YES WE CAN!!

We can combine simultaneously these 2 features below:
– Multiple forums assigned to 1 or more Groups
– Multiple groups assigned to 1 or more Users

Just using THIS PLUGIN: https://wordpress.org/plugins/bbp-private-groups/
This guy is a holy person!!!

@jazzbuzz The page is not available at this time. Check out the list of plugins tagged ‘buddypress’ at WordPress.org. Disclaimer: There are some plugins which use the ‘buddypress’ tag but could just only be compatible (no conflict) with BP or just use the tag for “SEO”.

In that case, try checking if there’s a plugin available. There could be something for WordPress which you could try to adapt to your needs.

Ref: https://en-gb.wordpress.org/plugins/

@djpaul Does BuddyPress use the same email-address for sending like WordPress? If not, that might be the problem: Some webhosters (like Hosteurope) restrict the usage of email addresses in scripts like WordPress to prevent spam.

For example I usually have to choose one email-address on my webhoster´s config platform. After that I can use it in WordPress. Any other email address won´t work for sending with WordPress, if I don´t use a plugin like https://wordpress.org/plugins/wp-mail-smtp/.

https://wordpress.org/plugins/buddymenu-buddylinks/screenshots/

not updated for a while check if it still works

change in ur DB or use this

https://wordpress.org/plugins/velvet-blues-update-urls/

You need to do more than add a button – you need a plugin:
https://wordpress.org/plugins/buddypress-followers/

If you don’t want Friends functionality, turn off the Friends component:
wp-admin > Settings > BuddyPress

We’re unable to help you for Yoo Helios premium theme.

Have you assigned a particular template to the mandatory BP pages: activity, members, groups,… ? If yes, remove them, as BP pages must stay “empty”. Just give them a title and nothing else.

Instead of using an exotic function, better try this solution.

is_buddypress fn definition: You can tell if a page is displaying BP content by whether the current_component has been defined. More here.