BuddyPress.org

@maganiza,

it’s possible. I suppose you need a unique code for some later user specific actions. But that code exist nowhere when a user register. What can we do ?

1) generate a 6 digit code and show it on the register page
2) asign that code to the user
3) show the code on his profile

1 – we use php mt_rand to generate the code and one of the available action hook on the register page for his output. Add this snippet to bp-custom.php

function bpfr_digit_generator() {
$num = mt_rand ( 0, 0xffffff ); 
$output = sprintf ( "%06x" , $num );
 
	echo '<strong>Your personnal code: '. $output .'</strong>';

}
add_action( 'bp_after_account_details_fields', 'bpfr_digit_generator' );

2) create a new xprofile field, call it Personnal Code or whatever. Make it mandatory and asign it the visibility level you want. In field description, ask the user to copy/paste in the code.

3) as the user entered the code in a xprofile field, you get automagically this field on his profile.

I’m a bit unsure how to insert this field value in the activation email, or if it’s even possible. Perhaps somebody else can help you. See email on codex.

A bit raw, but at least you have a start point how to do that.

Here also another method, you may use if you don’t want the user to copy/paste the code.

Yes. Every member in your install will have a user ID. So both BuddyPress and WordPress users will get a number. In fact, at the back end WordPress users and BuddyPress members are the same thing.

User IDs are assigned automatically so you don’t need to activate them. With reference to displaying the number on your BuddyPress site, check out this article:

Playing with the user’s ID in different contexts

Hi, i’ve a working solution for those like me who did not receive any buddypress email with html format (because there was a 3rd party plugin which was redeclaring wp_mail for eg.), here is the code to put in your functions.php file in your theme :

/**
* Provide an HTML template for all your BuddyPress emails
* BuddyPress 2.5 introduced a new stylised HTML email system. 
* By default the HTML system doesn't work if a 3rd party transactional email plugin is active 
* (e.g. wpMandrill or SendGrid), and reverts to sending plain text emails.
*
* This function allows the stylised BuddyPress HTML emails to be sent using some 3rd party plugin. 
* It does this by sending the email through wp_mail() rather than directly with PHPMailer.
*
* @author Mecanographik
*
* inspiration :
* @link https://github.com/21applications/bp-wpmandrill
* 
*/
add_action( 'init', 'my_prefix_bp_wp_mail_html_filters' );
function my_prefix_bp_wp_mail_html_filters() {
    add_filter( 'bp_email_use_wp_mail', function( $bool ) { 
      return false;
    }, 10, 1 );
}

hope this helps 😉

@radair2002,

nothing out of the box on hand, but what if you make any of the fields with “only me” visibility level as default , for everybody ? If site admin approve the content, he can change the level to something more public.

For email notification, a solution is given in this topic.

Perhaps you can also use this plugin, with some custom restriction/adaptation.

Maintenance mode is related to WP. BuddyPress was updated 24th may and WordPress 6th may.

Have you tried to debug by deactivating theme and all plugins (except BP) ? Use one of Twenty’s theme for that test and see if the notice remains.

Read also here to have a global overview of how this notice is coming up.

I have no idea where or what BuddyPress might be doing to cause that. More likely, it’s causing some issue with custom code. I think you might have to debug it, if you know PHP.

Sorry, no, it’s not a perfect solution, just a workaround. Best practice would be to use what is explained here.

As said previously you cannot change the Name field, and to exclude or modify his description you can’t even (so far i know) modify the default view level (All) for that field.

So you have to use another CSS trick and perhaps add an “only me” message to the Name field description.

#field-visibility-settings-toggle-1 {
display:none!important;
}

Hi @ma3ry,

it’s impossible !

But there is an all or nothing trick. You can apply a CSS rule.
Try to add this to your child-theme style.css

tr.field_1 {
 display: none!important;
}

Do you mind telling what version of Buddypress you are running since I am experiencing the same issue.

Thanks for the post, and thank you everyone that chimed in to alert the OP about the protocol for security concerns. Understanding it’s possible there’s a communication gap here, this topic does also read (to my eyes) as condescending & inflammatory, which is honestly not going to yield a very positive conversation. I think y’all did a great job staying positive, and I for one greatly appreciate that.

To be clear to anyone else that runs into this topic, what the OP sees is not a BuddyPress or bbPress bug; this is WordPress doing it’s best to show published content from public post types.

About BuddyPress:
* Neither BuddyPress nor bbPress modify this core behavior
* BuddyPress does not use this interface; bbPress does
* The .org sites have not disabled this, they just do not have any unusual content to leak

The gist:
* If plugins allow for private content, it’s up to those plugins to protect it
* If you create roles with content limitations, it’s up to you to confirm they’re working

For anyone looking to modify or restrict content that appears in this list, use the wp_link_query_args and wp_link_query filters to do so.

Here is how WordPress calculates the results in this list. Note that it only uses published posts from public post-types:

$pts = get_post_types( array( 'public' => true ), 'objects' );
$pt_names = array_keys( $pts );

$query = array(
	'post_type' => $pt_names,
	'suppress_filters' => true,
	'update_post_term_cache' => false,
	'update_post_meta_cache' => false,
	'post_status' => 'publish',
	'posts_per_page' => 20,
);

WordPress has a built-in way to calculate privacy scope using 'perm' => 'readable' and even that is not used here (though bbPress does use this in its own loops.) WordPress instead takes a strict position of published public content by default.

If anything unexpected is appearing here, it is not because of BuddyPress or bbPress, and we are still happy to help anyone discover the source of this in a new & more friendly topic.

@sbrajesh (BuddyDev) published a pretty cool tip about page titles:

Using WordPress Page Titles for BuddyPress Directory Page heading & Titles

Is there a formal process for requesting this feature?

Yes. The formal place to request features is Trac.

Hi @handyandywilson

Your first stop when customising the activity stream should be bp_parse_args(). Check out this article:

Using bp_parse_args() to filter BuddyPress template loops

@earl_d

As the registration process can be different according to WordPress configs, can you please provide some details about yours :
– Multisite ? If so is BuddyPress network activated or activated on a specific blog of the network
– Plugins ? Especially the ones that might play into the registration process.

FYI, i’ve just rechecked on 2 freshes WordPress configs (regular & multisite) having only the BuddyPress plugin activated. Registration is working great.

@nnyorker you’re probably activated a standalone BuddyPress theme that has no support for the cover image feature.

I advise you to have a look at this post:
BuddyPress 2.4.0 will introduce Cover Images for members & groups!

Thank you for getting in contact with the BuddyPress team. Some of the attitudes displayed in this discussion have not been respectful and are not conducive to a productive conversation, so I am going to close this topic for that reason only. If anyone has questions about this moderation action and is prepared to discuss them civily, you can find my contact details on https://profiles.wordpress.org/djpaul/.

All projects, including bbPress, BuddyPress, and WordPress, appreciate responsible reporting of suspected vulnerabilities. Read this page on the WordPress site for reporting guidelines for all the aforementioned projects: https://make.wordpress.org/core/handbook/testing/reporting-security-vulnerabilities/

@djsteveb On the whole, the BuddyPress team enjoys a good working relationship with rtMedia, and we have often discussed issues when it’s vague when the root cause lies. I appreciate that it’s frustrating to be passed from pillar-to-post when you’re trying to get support or report a problem. If you still have the information, I’d encourage you to get in contact with the rtMedia team to start the conversation.

Hi @paulrooms

The Italian translation of BuddyPress is up to date: https://translate.wordpress.org/locale/it/default/wp-plugins/buddypress

For the menu items (at least what I think you mean), you’ll need to go into wp-admin > Pages > Edit, and just rename/translate the pages yourself.

I am pretty sure this this not easily changeable and is hardcoded to use the login or nicename (depending on the value of the BP_ENABLE_USERNAME_COMPATIBILITY_MODE constant; https://codex.buddypress.org/developer/filters-reference/).

Problem with display name is that because people can change that (unless you customise a site to prevent people doing that, but that’s not something we want to force on in BuddyPress), you can have situations where people swap display names (accidentally or maliciously) and then start receiving at-mentions intended for other people, etc.

@navyspitfire BuddyPress does not use wp_mail(), so any calls to that function are ignored and not treated with BuddyPress’ email templating.

If your BuddyPress emails were being sent plain text, then that means you have a plugin that re-declares the wp_mail() function — probably your SMTP plugin, I’d guess. There are other SMTP plugins that don’t redeclare the function, and so compatible with BuddyPress.

We fallback to plain text in these cases to maximise compatibility with all the many ways of customising emails that WordPress permits.

The equivalent function is bp_send_email(), and for the type of email you mention, here’s an example usage: https://github.com/buddypress/BuddyPress/blob/master/src/bp-core/bp-core-filters.php#L533

This is not a BuddyPress problem. It’ll be a issue with the PHP you’ve added. You’re probably missing a semi-colon from the previous line, or something.