BuddyPress.org

PBCK ! Annoying for you, but read here please before telling “it doesn’t work” and give some information about what and how you are handling your issue.
https://buddypress.org/support/topic/when-asking-for-support-2/

If you remove something from the original BP files, and this something is still appearing, you probably use a theme or a child theme containing this part.

You should also clear your navigator history. This mostly resolve such situations. 😉

You are right the css override does not work sorry. I just remembered how I did this sorry, try this function to turn off mentions:

// remove buddypress mentions
add_filter( 'bp_activity_do_mentions', '__return_false' );

Try Adding it to your theme functions file or a custom plugin.

Why isn’t Buddypress doing something about this!! No social/dating site I have ever seen has this @ username!!
Just don’t get it… give us a check box to get rid of it please.

Yes, you can use the BuddyPress Like plugin to do that: https://wordpress.org/plugins/buddypress-like/

The wording can be changed via the admin area.

The WPMU one is good, I use that in tandem with Buddypress on one of my sites – there’s a range of other goodens too that might be worth a look at – http://www.ventureharbour.com/membership-plugins-for-wordpress/

Thanks for the feature request. At this time BuddyPress only provides visibility settings for individual profile fields. We’ve been putting off building a robust member to member permissions component until after we have attachments. Right now, everything in BuddyPress is loosely considered public.

Remember that BuddyPress is still powered by WordPress, and WordPress’s roles and capabilities system isn’t really powerful enough or scalable enough to handle permissions for millions to millions of users.

That said, there have been plugins that attempted to fill this void, but none of them gained a whole ton of traction unfortunately. We’ll get there, but it’s a bit of a long road.

We’ve talked about more deeply integrating activity stream likes into other parts of a BuddyPress powered site, but haven’t prioritized it yet. This is the first report of any incompatibilities between 2.0 and Jetpack.

Hi, I am facing similar 404 error. I am running wordpress 3.8.1 with buddypress 1.9.2 plugin. The front pages are working fine but the buddypress pages, including register pages are showing 404 error.
I found this solution for APACHE http://www.youtube.com/watch?v=m9zESEfNzSQ but I am on Windows.

Hi – I’m using Frisco for Buddypress, which inherits from Buddypress Default. What’s the fix for my situation? I don’t see home.php in either theme.

What @boonebgorges said.

BuddyPress’s URI router came from a much older codebase, in a time where BuddyPress was intended to be bolted on top of a WordPress Multisite installation similar to WordPress.com, and not much else. Once that was achieved, we quickly saw the potential in it being something much more powerful (to a larger audience) by quickly iterating away from that original goal, making it work on single-site WordPress, and refactoring the individual components to be less dependent on each other, and only dependent on a core set of common functionality — part of which was the URI router.

We’ve recently chopped two large pieces out of BuddyPress core and turned them into separate components: Settings and Notifications; and we’ve taken huge strides and helped simplify the getting-started process with making it theme agnostic. Bigger ideas like attachments, permissions, and deeper WordPress integration (both in wp-admin, and it’s API’s) is something we continue to improve with every release. Rewrite rules just so happens to touch every component, every file, and every page request, so it’s a refactor that is going to take several months of architecting before it’s complete (similar to theme compatibility.)

Basically… we’ll get there, and there is a plan. It’s been said that before creating David, Michelangelo stared at a block of marble for 8 hours a day, for 4 months, before making his first chip into it. Not trying to compare ourselves to prolific artists or anything, but the idea is the same in that we’re all staring at a huge codebase and coming up with our own map of how to approach the problem.

Hi,
I am running buddypress plugin on wordpress 3.8.1 and using Windows hosting for http://haflongbosconians.org/ . While the front pages are working fine, the buddypress pages are showing a 404 error.
I found this solution for APACHE http://www.youtube.com/watch?v=m9zESEfNzSQ . What can I do for Windows hosting?
Appreciate your help.
Regards.
Soumya

> the hobbled together mess

Just to push back a little on this one. There are a couple of key ways in which BP’s current permalink router is not ideal (it’s not amenable to caching; it’s not non-pretty-permalink friendly; it’s hard to write unit tests for it; it leaves some slugs difficult to change). Moving toward the WP Rewrite API is a worthwhile project, because improving on these areas are worthwhile things to do.

However, it’s important not to overstate the problem. The current system works just fine for many thousands of BuddyPress sites. While there would be new efficiencies and configuration possibilities with a new system, it’s unlikely that their absence to date has ever been a dealbreaker for any BuddyPress site. @synaptic or others, I may be wrong about this, and if there are specific ways that the current router is holding you back, it would be very helpful to know more about those details.

In any case, while it will require a large amount of work to build a new system that’s compatible with the old, it’s not doing any active harm to existing (or new) sites to use the current (perfectly functional) system. So let’s not get too carried away with the idea of forking our own project 🙂

This is what I did, ignoring the bit above:

The function bp_displayed_user_mentionname is declared in /plugins/buddypress/bp-activity/bp-activity-template.php:1027

As this function is a filter, we can simply remove it to remove the @username from the template. But because the hardcoded @ sign before the username, we have to add a CSS rule with the remove_filter function. The function above will do all that.

Add these snippet to your bp-custom.php (read here if you don’t know this file)

/* remove @username from the profile header */

function bpfr_remove_mention_from_profile() {

echo ‘<style> h2.user-nicename { display:none; } </style>’; // hide the h2 containing the @

if( bp_is_user() && ! bp_get_member_user_id() ) { // be sure we get the right user_id
$user_id = ‘displayed: ‘. bp_displayed_user_id();
} else {
$user_id = ‘get_member_user: ‘. bp_get_member_user_id();
}

remove_filter( ‘bp_get_displayed_user_mentionname’, bp_activity_get_user_mentionname( bp_displayed_user_id() ) );

}
add_filter( ‘bp_get_displayed_user_mentionname’, ‘bpfr_remove_mention_from_profile’ );

I would totally not recommend to disable it. You should spend more time to figure the problem out. In my BuddyPress test installations (local and live), it sends the emails just fine, so there is a problem, maybe in your server, template, I don’t know, somewhere.

But, if you really wanna disable this, after a quick search here and in Google, I found some possible solutions.

Obs.: I haven’t tested it, so use it at your own risk.

https://buddypress.trac.wordpress.org/ticket/3443
https://buddypress.org/support/topic/i-would-like-to-disable-email-activation/#post-43483

I am having this exact issue. I am a developer and I know how to run through the steps mentioned here..

What I have tried is to find a user that is stuck in not being activated and running putting this on one of my pages:

<?php                                                                                                        $user = get_userdatabylogin('busaany'); echo $user->ID;                                                                                                    echo get_user_meta( $user->id , 'activation_key', true );
?>

This yeilded an activation key:
2429b4ee92830f6557b5b5be271b5078defe

So I tried to plug that into the activation key url as such:

http://bounty.co.nz/activate-account/?key=2429b4ee92830f6557b5b5be271b5078defe

This brought me to the invalid key page as mentioned by others… This is a major issue and I am getting all sorts of stress/grief from my client. I am 100% committed to fixing this issue myself if that is what has to be done. But I was hoping that my putting this here could give the buddy press devs some more info on what is going on. This use HAS signed up, this use HAS tried to go to this link and it failed first time.

I have used a plugin called buddypress pending activations to try and remedy this and trouble shoot it. It allows me to figure out who is being caught and it is a non-trivial amount of users. The user remains in the pending regardless of visiting that link or entering the code into the box on the page…

Any leads? I will be getting this locally set up and try and debug buddypress as I am certain this is buddypress thing now not a server issue. But if you can get me any help or direction that would be great. If I can fix this I will let you guys know and we can get this resolved in the core.

Regards,
Justsayno1

BuddyPress doesn’t have an API, what are you using to get json?

https://buddypress.org/support/topic/auto-add-friends/
https://wordpress.org/plugins/bp-automatic-friends/

What exactly in BuddyPress is the problem? Have you tried the 2.0 beta?

BuddyPress 2.0 Beta 1 is now available

@halo-diehard
The Group Forums component in BuddyPress has been retired and it is indeed advised to use bbPress (version 2.x).