BuddyPress.org

There is one other tweak that’s coming up in BuddyPress 2.5.3 (not sure when it’ll be released, would guess a week or two) that might address it. After 2.5.3, BuddyPress should be identical with WordPress in terms of compatibility with the majority of plugins that help WordPress support SMTP.

For the record, if you’re running a plugin that defines wp_mail() that helps you have WordPress’ emails be sent, then it just won’t work with BuddyPress.

This doesn’t work: /wp-content/languages/buddypress-fr_FR.mo, except if you want to use “buddypress” as your site language. BuddyPress isn’t a language, so i won’t recommand to do that. So, guess it’s not required.

Auto update means “auto”, YOU have NOTHING to “put in”.

if you use /wp-content/languages/buddypress/buddypress-fr_FR.mo, it doesn’t work.
You have to create a BP folder in /plugins/ like this /wp-content/languages/plugins/buddypress/

… and read again what i wrote previously. I don’t like to write things twice. 😉

See https://buddypress.org/support/topic/filter-for-wp_mail_from-stops-working-with-activated-buddypress/

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.

Hi,

take a look here: https://buddypress.org/support/topic/code-for-adding-new-members-to-groups-automatically/

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 ?

Hi,

a simple, but raw solution would be to use CSS. Something like:

#buddypress .standard-form #profile-details-section {
   float: left; 
   clear: left;
}

But it’s raw and probably need some adjustment with your theme, and some mobile devices detection rules.

Another solution could be to use this premium plugin, by BuddyDev.