BuddyPress.org

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

Having the same type of issue. I cant use xprofile_get_field_data from the functions.php in a child theme.

You might just over load members/single/parts/item-nav.php and members/single/parts/item-subnav in your child theme and just remove all the navs or replace them with something of your own.

you could keep searching forums for topics on removing tabs there are some “solutions” to removing tabs.

https://buddypress.org/support/search/bp_core_remove_nav_item/

> Buddypress: version 5.0 was added to the theme as a plugin

What does it mean?

BuddyPress is not installed from the Plugins Management screen?

Please make sure to follow all suggested checks into this topic, in particular testing with only BuddyPress activated and a Twenty* WordPress bundled theme.

They can choose the password of their choice and use the checkbox to confirm the use of weak password if needed.

Having a password to log in is required. Having a strong password is important for the safety of your site.

Disabling this feature would be too bad imho. But you can always override the /members/register.php from a /buddypress/members/register.php template in your active theme (or better child theme).

Try to disable all your plugin then change to default theme then try to upload an image again then if it’s working try to one by one enble all your plugins then figured out which plugin is not compatible to your setting .

It’s probably a javascript conflict with some code in your theme or some other plugin.
Did you check your browser’s console for js errors?
To confirm it is your theme, try momentarily switching to a WP theme like 2018 and see if the error persists.
Are you using a caching plugin or something that minifies javascript?
Try deactivating it or the minify part and see if the error persists.

Edit timed out on me up there and didn’t get to revise my reply in time!

/buddypress/activity/post.form.php, overload it child theme

/*
 * Template tag to prepare the activity post form checks capability and enqueue needed scripts.
 */

if( bp_is_group() && !current_user_can('administrator') ) {

} else {

bp_nouveau_before_activity_post_form();
?>

<h2 class="bp-screen-reader-text"><?php echo esc_html_x( 'Post Update', 'heading', 'buddypress' ); ?></h2>

<div id="bp-nouveau-activity-form" class="activity-update-form"></div>

<?php
/*
 * Template tag to load the Javascript templates of the Post form UI.
 */
bp_nouveau_after_activity_post_form();

}

@meisinotti you can restrict the post form to admins depending on what template pack you use… you could set something like,

with nouveau, /buddypress/activity/post.form.php, overload it child theme

/*
 * Template tag to prepare the activity post form checks capability and enqueue needed scripts.
 */

if(bp_is_group_activity() && current_user_can('administrator')) {

bp_nouveau_before_activity_post_form();
?>

<h2 class="bp-screen-reader-text"><?php echo esc_html_x( 'Post Update', 'heading', 'buddypress' ); ?></h2>

<div id="bp-nouveau-activity-form" class="activity-update-form"></div>

<?php
/*
 * Template tag to load the Javascript templates of the Post form UI.
 */
bp_nouveau_after_activity_post_form();
}

assuming you don’t allow users to create their own groups, if you want to allow them to post updates on their own created groups then you’d need to check for that.

Hey everyone. Thank you for the insightful conversation. This is exactly what forums and communities are for, and is a great example of why it is so important to have them.

This question has come up just about every 180 days for the past 10 years, for both bbPress and BuddyPress. I usually don’t chime in on them, because they almost always go through the same motions:

1. Some people are worried
2. Some people don’t like the core functionality
3. Some people think it’s too difficult
4. Some people think it’s not powerful enough
5. Development team defends the project
6. Unhappy people trash the project
7. Nobody really feels much better
8. People get bored and the topic fades away
9. Someone bumps it back up every once in a while

I’m replying here and now, because I agree a lot with everything everyone has said here, even if I don’t like or agree with how it’s said.

There are a lot of things about BuddyPress not to like. There has been a lot of added complexity over the years that has made it more difficult to understand and to work with. Building a community website with it takes a long time and requires a lot of experience to do well, and that’s even before the community has activity, membership, or growth.

Without a big huge obvious whale of an example community, and without a big huge corporate sponsor, it’s hard to see the penultimate standard for what BuddyPress can be used to achieve.

Because BuddyPress.org and bbPress.org are part of the WordPress.org network of sites, and because WordPress.org doesn’t really use the social features that BuddyPress provides, even it isn’t that great of an example anymore.

The folks at BuddyBoss have, no doubt, invested nearly the same ten years as the rest of us have, working hard to make something out of nothing, only with a different set of goals in mind, that now is taking them in an exciting new direction.

Having met several members of the BuddyBoss family, and after spending more than a few hours hanging out with them through the years at various WordPress related events, it cuts deep to hear how negative their perspective is on BuddyPress, but I don’t disagree with them, or think they’re wrong.

Ten years ago when everyone was excited about BuddyPress, wasn’t because of the technology or the tools or the potential. It was a pain in the butt to setup. It required a version of WordPress (MU) that didn’t even come with an installer. It did everything “the wrong way” and not “the WordPress way.”

Everyone was excited because it looked cool.

Source: Venturebeat

While not an exact clone, BuddyPress 1.0 popularized the 3 column design layout that Slack, Discord, Teams, and Mattermost, and others have built empires on top of today. Since 2.0 and later, we listened to user feedback instead of our guts, and worked to make BuddyPress simpler to drop into any WordPress installation, but in doing so we sacrificed the opinionated design that made all of us curious about what we could build on top it ourselves.

I believe BuddyPress is, still to this day, the single most important piece of software on the open web. It empowers anyone to foster free and open dialogue with the privacy and freedom of having their own website on their own hardware, while also being powerful enough to scale up and grow as a community of people garners momentum. And it empowers people like the folks at BuddyBoss to grow even beyond BuddyPress itself.

BuddyPress also continues to be a faithful sister-project to WordPress, bbPress, and GlotPress, acting as a playground for just about anyone to jump in and start helping improve the software that over 11 million users on WordPress.org and 300k other installations rely on to power their activity streams, member profiles, and more.

I personally have met or know a few hundred people that have amazing careers (in WordPress or elsewhere) because of the knowledge and insight that contributing to the BuddyPress project has trained them for. (This is one of the most valuable things about BuddyPress that you can’t write on the tin, in my opinion.)

To the folks that feel like leaving BuddyPress behind, happy trails until we meet again. And I hope we meet more often than we have, because our diversity of experiences and opinions is how we forge great open source software together, and that’s hard to find when you’re always looking inward at the same project for this long.

To the folks that love BuddyPress as much as I do, thanks for sticking around and helping out and being a part of this community here. The best is yet to come, with media attachments, database improvements, deeper WordPress Admin integration, and if wishes were fishes we’d revive a retro bp-sn-parent theme to bring some of that old excitement back again.

Here’s a corny quote from a favorite movie of mine that feels fitting:

I cannot tell you how long this road shall be, but fear not the obstacles in your path, for fate has vouchsafed your reward. Though the road may wind, yea, your hearts grow weary, still shall ye follow them, even unto your salvation.