BuddyPress.org

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.

All 3 of these options (BP Simple Private, Buddypress Lock, or the custom code) all cause significant page speed issues. (like 3 seconds)

Any suggestions to combat the privacy issue without compromising speed?

Hi @meganelford,

basically, your developer is requesting information so that the app can authenticate with the BuddyPress site. Due to the fact users are authenticated, the app needs permission to authenticate using those keys you mentioned.

To make that happen you would need to have a token or oAuth plugin setup on your buddypress site. After that, create those API keys and provide to her.

Here are a few plugins you could try:

JWT Authentication for WP REST API

WordPress REST API Authentication

Application Passwords

https://github.com/WP-API/jwt-auth

Just be aware that whatever choice you make, there will be a learning curve.

Also, I’d recommend checking how the API will affect the intranet nature of your site. For example, if you intranet is private (the front-end of the site), current BuddyPress API is open. Meaning, some information is open to the public (not logged in information, of course).

Just something to keep in mind. Hope this answer your question, or at least, provides you with next steps (install the plugin and pass the keys information to her).

🙂

With as much as @buddyboss depends on buddypress and with how much they charge, I sure hope they are doing the ethical thing and donating to the buddypress group that they are profiting off of.

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.

Hi,

Well, as a start, you can try to paste the first example of code of this section: https://codex.buddypress.org/developer/group-extension-api/#examples into a bp-custom.php file and replace the display method of the Group Extension with:

public function display( $group_id = NULL ) {
   $group_id = bp_get_group_id();
   
   $page = get_post( 27 );
   echo apply_filters( 'the_content', $page->post_content );
}

Hi,

What is your BuddyPress version ?
What is your WordPress configuration ? Multisite or regular ?
What is your active Template pack ? Nouveau or Legacy ?
Have you tried with a bundled WordPress theme like TwentyNineteen to see if this was an issue with Kleo ?
Are there other plugins active ?
Can you add a screenshot ?

Hi!

For your information and as a follow up of the ticket you opened on Trac ( https://buddypress.trac.wordpress.org/ticket/8159 ), I’ve checked on my side and wasn’t able to reproduce.

My config is WordPress 5.2.4, BuddyPress 5.1.0-beta1, Twenty Nineteen as the active thme. No other plugins or specific custom code in /wp-content/mu-plugins or /wp-content/plugins/bp-custom.php.

@buddyboss Why didn’t you contribute to the buddypress code instead of creating competition off of thousands of hours of donated development for this free plugin?

Sorry I misinterpreted the initial question, so you have 2 questions
1. Upon logging in you’d like to redirect the user to his profile activity page.
2. How to disable the wp-login for non-admins or something like that so that regular users never see wp’s login screen.

2. https://wordpress.stackexchange.com/questions/62889/disable-or-redirect-wp-login-php would this be a good start to a solution

1.https://buddypress.org/support/topic/login-redirect-to-activity-personal-page/ ?

I’m having a similar problem. How do I enable profile fields inside buddypress settings?

did you try https://buddypress.org/support/topic/making-users-profiles-forums-and-activity-private/