BuddyPress.org

Cannot duplicate this.

You might have a javascript conflict.

Try disabling all plugins except BuddyPress and try again. If it works, then it’s a plugin conflict somewhere. If you’re running a custom theme that has purported BuddyPress support, also switch to a default WordPress theme.

What is the “latest buddypress version” for you?

If you were using v2.9.0, then the patch I linked to should apply cleanly. There should be no changes between your copy of /bp-core/bp-core-avatars.php and v2.9’s /bp-core/bp-core-avatars.php.

If your version is v2.9.0, then I would recommend re-installing BuddyPress from the wordpress.org plugins repository.

different problem, but was told to post here:

When I try to create a group, I get to an error page (unlike you, I see the button). I figured there might be a problem with the link (It links to /groups/create).
I though it might be a problem with my permalinks, so I tried to update them, but nothing happens. Also, creation of new emails, for example, work without problems.
I installed the plugin as usual through the wordpress plugin directory. I’m running buddyPress 2.9.0 and Worpress 4.8.1

This is more of a WordPress question than something specific to BuddyPress. Try asking here https://wordpress.org/support/

Hi! This evening I had the same problem about comments in BuddyPress. It took me a couple of hours to find the solution, but was in part thanks to this forum that I could do it. I wrote a post joining all the solutions that I found and applied together. I hope that you considerate this usefull, the post is this: Cómo evitar que se muestren todos los comentarios de WordPress en las páginas de BuddyPress. Thank you for this amazing forum.

¡Hola! Esta tarde tuve este mismo problema acerca de los comentarios en BuddyPress. Me llevó algunas horas dar con la solución, pero en parte gracias a este foro pude hacerlo. Escribí un artículo recopilando todas las soluciones que encontré y fuí aplicando. Espero que les sirva, el artículo es este: Cómo evitar que se muestren todos los comentarios de WordPress en las páginas de BuddyPress. Gracias por este maravilloso foro.

Thanks for the report.

If you are able to, can you see if the following will fix your problem?
https://buddypress.trac.wordpress.org/attachment/ticket/7578/7578.01.patch

2.9 is the latest stable version. You can download here: https://wordpress.org/plugins/buddypress/

2.9 is the latest stable version. You can download here: https://wordpress.org/plugins/buddypress/

I’ve added a potential fix for this here:
https://buddypress.trac.wordpress.org/attachment/ticket/7577/7577.01.patch

Let me know when you’ve had a chance to test.

Thanks for the report. I’ve created a ticket here to track its progress:
https://buddypress.trac.wordpress.org/ticket/7577

You could replace this: ($_SERVER['PHP_SELF'] != '/wp-admin/admin-ajax.php')

With this: ! wp_doing_ajax()

wp_doing_ajax()

I am using the plugin “TinyMCE Advanced” for wordpress pots, maybe it makes the error, but I need it for wordpress posts.

This has been filed as a bug, but was too late to make v2.9:
https://buddypress.trac.wordpress.org/ticket/7569

There is a patch attached with a fix if you want to fix this temporarily.

I just don’t know what impact this will have on overal performance when I go wish in other tables for content.

It depends. WordPress and BuddyPress do a great job when it comes to optimising queries but there are things that will cause a big site to simply fall over (the meta_value column isn’t indexed for example so meta querying could be problematic).

You can turn off registration.
Head over to Settings » General page in your WordPress admin area. Scroll down to the ‘Membership’ section and uncheck the box next to ‘Anyone can register’ option.

get_post() will get a WordPress post from the wp_posts table. This is different to a BuddyPress activity item which is stored in the wp_bp_activity table.

Try with this:

function tubs_sanitize_user($username, $raw_username, $strict) {
    $new_username = strip_tags($raw_username);
    // Kill octets
    $new_username = preg_replace('|%([a-fA-F0-9][a-fA-F0-9])|', '', $new_username);
    $new_username = preg_replace('/&.?;/', '', $new_username); // Kill entities

   // If strict, reduce to ASCII for max portability.
   if ( $strict )
        $new_username = preg_replace('|[^a-z0-9 _.\-@+]|i', '', $new_username);

    return $new_username;
}
add_filter( 'sanitize_user', 'tubs_sanitize_user', 10, 3);

Source

Or try with this:

// Force Strong Username
function strong_username() {
 global $bp;

 if ( !empty( $_POST['signup_username'] ) )
   if ( !valid_username( $_POST['signup_username'] ) ){
    $bp->signup->errors['signup_username'] = __( 'Your username is not strong enough. Use uppercase, lowercase, numbers and special chars like - _', 'bp-strong-username-password', 'buddypress' );
   }
 }
 add_action( 'bp_signup_validate', 'strong_username');

 function valid_username($candidate) {
   $r1='/[A-Z]/';  //Uppercase 
   $r2='/[a-z]/';  //lowercase
   $r3='/[0-9]/';  //numbers
   $r4='/[-_]/'; //Special chars, underscore...

   if(preg_match_all($r1,$candidate, $o)<1) return FALSE;
   if(preg_match_all($r2,$candidate, $o)<1) return FALSE;
   if(preg_match_all($r3,$candidate, $o)<1) return FALSE;
   if(preg_match_all($r4,$candidate, $o)<1) return FALSE;
   if(strlen($candidate)<6) return FALSE;

   return TRUE;
}

is_user_logged_in() is a WordPress function. It’ll return true if the user is authenticated and false if not.

bp_loggedin_user_id() will return the ID of the BuddyPress member currently logged in.

The two functions are different.

Already reported.

See https://buddypress.trac.wordpress.org/ticket/7139

Is https://www.example.com/example/ a WordPress page? If it is you can target it with

if ( is_page( 'example' ) ) {
    // Do something.
}

Also, I just added the code below and I can still access the members directory when not logged in

Where did you add the snippet? The code should work.