BuddyPress.org

This issue is caused by Yoast SEO update. Either disable Yoast SEO or downgrade it to v12.5.1 and the site should work again.

I have reported this issue to buddypress on the Yoast WordPress support forum.

Hi,
I am not aware of any free theme currently but it is going to change in 2020.

We are looking forward to change this completely from 15th January onward. We will provide you with multiple free themes(1st releasing on 15th January). I am looking forward to help make BuddyPress experience pleasant and smooth.

Regards
Brajesh

Hi
We are in the process of releasing a free theme for BuddyPress which should compete with any available premium theme on design/quality.

Since the holidays are here, we are scheduling for 15th January. I am hoping to encourage BuddyPress adoption with our free theme.

Regards
Brajesh

Thanks for your report! I’ve created a ticket with a patch that corrects the behavior here: https://buddypress.trac.wordpress.org/ticket/8167

You may have found a bug.
You can open a ticket here.

Using the proper hook always helps. Can be tricky to figure out.

This is not up to date or comprehensive, but should help: bp hook order

You should not need to write a custom query to retrieve a piece of profile data, but if you do then this is more distributive:

global $wpdb;
$bp = buddypress();
$user_id = get_current_user_id();
$field_id = 2; // for example
$field_value = $wpdb->get_var( $wpdb->prepare( "SELECT value FROM {$bp->profile->table_name_data} WHERE field_id = %d AND user_id = $user_id", $field_id ) );
var_dump( $field_value );

You are making some basic mistake.
You shouldn’t need to create an instance of bp
Try using the bp_ready hook instead of bp_loaded.
Instead of $bp->loggedin_user->id use bp_loggedin_user_id() or get_current_user_id()
You don’t say where you are trying to use it in your child theme.
Why not use pastebin to share the section of code that is not working?
Use var_dump rather than echo to see what is really being returned.
Try your code in bp-custom.php

I second action here.

WP now has a password strength indicator with an option to allow a weak password. There is a plugin here that removes that option, so a user setting their password in the backend cannot set one WP regards as weak.

Bu there is nothing to stop a use setting a very weak password in their BuddyPress profile. It warns you it is weak but still allows it. Please can we have the ability to block that?

No response. I don’t understand how is it possible to have such a bad navigation system on buddypress. It’s basic but the ajax system is completly anti-ergonomic. When you click on page 2 then click on a profile and click the return button you go back on page 1. This made me crazy that nobody correct this.