BuddyPress.org

@beo9999 It’s already fixed you can followup following discussion
https://buddypress.trac.wordpress.org/ticket/7391

@demiano Profile Name field is mandatory and it’s created at a time of plugin activation. It’s hard to add visibility control on it.
You can also check a related discussion on it
https://buddypress.trac.wordpress.org/ticket/7391

This is a bit of a wordpress issue in general, not just BuddyPress, for example much of the user info is actually from the WP user db, it’s also to do with the applications that you choose to use on WP. I believe the plan is for WordPress to build into core a Privacy Policy management system whereby plugins will be able to register their privacy/compliance options and the system admin will be able to use those to put together privacy policies using the mechanisms made available within this framework. Plugins can of course choose to implement their own solutons to GDPR.

The discussion regarding BP’s response to GDPR is here:

https://buddypress.trac.wordpress.org/ticket/7698 looks like the BP solution to this will be in 3.x.

You could ask for this as a feature request on Trac

There is a premium plugin I know of that does this – BuddyPress Profile Visibility Manager by BuddyDev.

Do you have a validation function in your class?
Something like:

public function is_valid( $values ) {
   $this->validation_whitelist = null;
   return parent::is_valid($values);
}

For a fairly simple example of adding a custom xprofile field, see BP xProfile Location
( yes, I know it does not yet reflect the recent changes to the Google API, but it should pass validation for your purposes )

Sounds like you need to remove the nav item that corresponds to that link.

There’s two menu items that possibly need to be removed. the most common one could be removed with the bp_core_remove_subnav_item( 'settings', 'general' ); function.

Do you also use the WordPress/BuddyPress adminbar?

I think I’d be tempted to raise this as a bug on trac:

https://buddypress.trac.wordpress.org/

https://buddypress.trac.wordpress.org/ticket/7792

I’ve raised a ticket for this.

@mrditt
You can switch in real time.
Mailgun will send email sent to WordPress or any other plugins including BuddyPress.
Mailgun has a free slot and paid stot, based on usages you can increase your plan.
When someone sends a message to Adam (just random username), Adam will get an email notification as well.

You can find the doc here https://codex.buddypress.org/emails/
It will help you disable all bp emails, alter them and disable some emails based on their actions.

Thank you Paul for commenting. I wish I was clearer.

I was referring to the Log In and Register buttons on the admin bar (which is Buddypress) in the top left.

Im using this to disable BuddyPress’ registration process and fallback to WordPress. I want to merely change the link of the Log In button so it goes to my custom login page. How do you go about doing it?

<?php

/**
 * Disables BuddyPress' registration process and fallsback to WordPress' one.
 */
function my_disable_bp_registration() {
  remove_action( 'bp_init',    'bp_core_wpsignup_redirect' );
  remove_action( 'bp_screens', 'bp_core_screen_signup' );
}
add_action( 'bp_loaded', 'my_disable_bp_registration' );

?>

$wpdb->get_col returns an array
$wpdb->get_var returns a single value – try it

https://codex.wordpress.org/Class_Reference/wpdb

@pandreas you can create group type with https://wordpress.org/plugins/bp-create-group-type/
and you can display them via shortcodes on any pages with group type parameters

and with https://github.com/wbcomdesigns/shortcodes-for-buddypress you can have a shortcode to display groups with group-type anywhere as a shortcode
e.g. [groups-listing type=”sports”]

You can use https://wordpress.org/plugins/mailgun/ and it will work perfectly. I am also using it on my sites.

@luke_devon You can check https://wordpress.org/plugins/bp-member-type-generator/, with their pro version you can also map them to user roles.

Loop functions are a pretty basic feature of WordPress, in WP 101 terms it’s basically lesson 2 – how the posts page displays a list of all posts. It does this by having a loop – using a function to pull in all posts (or in bp members or groups) then using a while loop to iterate through all those posts, members groups etc, depending on the context.

So a bp Loop looks something like this:

If has_members:
While has_members:
print out the info you want
End while
Else
// there were no members