BuddyPress.org

There is not such publicly available plugin.
But that’s an interesting idea to consider for plugins-dev.

Can BuddyPress send all other emails? Like new message, groups changes etc?
So, is the email with activation link the only email, that is not sent by BuddyPress?

Try WordPress SEO plugin AND this hack:
https://github.com/Yoast/wordpress-seo/issues/1971#issuecomment-227008322

That will fix titles. There is no solution for meta descriptions, unfortunately.

Here is related Codex page.
You will need to change in your template something like this:

<?php if ( bp_has_activities( bp_ajax_querystring( 'activity' ) ) ) : ?>

to this:

<?php if ( bp_has_activities( bp_ajax_querystring( 'activity' ) . '&per_page=10' ) ) : ?>

Check your theme /buddypress/activity/activity-loop.php file. If you don’t have it,…[Read more]

That’s definitely not a BuddyPress issue.
Make sure that you don’t have some “security” plugin activated, that might prevent the usual login process.

AFAIK, installing BuddyPress on a subdomain of WordPress MultiSite won’t give you BP widgets (and other content) on a main site, thus you won’t be able easily (without coding) display BuddyPress content on any site in the network, excerpt the BP-site.
So BuddyPress content will be available only on site where you activated BuddyPress.

I hope I’ve…[Read more]

So bp.example.com is the subdomain, that you use for BuddyPress. Does it have separate WordPress installation (not related to example.com)?
Is WordPress on your example.com MultiSite or ordinary?

Seems you have fixed the issue.
I have just registered on your site, and sent a friendship request to user “admin”. Everything seems to be ok, I can cancel it.

You definitely should try first to re-save page structure in Admin area => Pages => Members.
Users profile inherits everything related to that page (like slug and structure), BuddyPress just substitutes that page content, so all its settings should be in place.

That’s quite a lot of custom code.
All that activities are not related to BuddyPress directly. Although you can store them in activity directory when that action was performed using bp_activity_add() function.

But as everything you described is not a default WordPress and BuddyPress functionality – I strongly advice you to find some developers,…[Read more]

The only option is to use CSS (in style.css) in your child theme to modify that. Or some plugins, that give ability to apply styles without modifying files (Siteorigin CSS).

#buddypress #register-page label {
font-size:120%;
}

So far there is no such plugin.

You can try to dive into bp_get_new_group_invite_friend_list filter, and you will need to rewrite /buddypress/groups/single/send-invites.php template.

So quite a lot of work.

Actually, this setting is still there. Check this screenshot: http://take.ms/TOux7

Check that you have Extended Profiles component activated – as avatars/covers uploading is part of it.

BuddyPress registration page is quite big, it has a lot of inputs.
You can install a widget, called (BuddyPress) Log in. Here is info about it.
If you use Jetpack, there is a module there, that gives ability to define widgets visibility. Here are other plugins: one, two & etc.
Thus you will have ability to define, that this widget should be…[Read more]

Version 3.6.9 is released, pushed to WordPress repository. Soon it should be available worldwide.

Fixed in repo. Hopefully will package the release this week with some other fixes.
Meanwhile, you can download the plugin code from github.

Part of the issue is fixed, see github.
<strike>New nav API requires me to rewrite drag-n-drop nav reordering feature completely, but I’m lazy and trying to find a workaround.</strike>
WIP.

edited by slaFFik, thanks to @boonebgorges for the assistance

There is no such error on front-end (just tested).
Do you have this somewhere in wp-admin area?

I have some thoughts regarding the issue. Will try to test them this night.

messages_get_unread_count() uses info about logged in user.
bp_get_members_component_link() – about displayed user.

Logged in user – is based on cookies.
Displayed user – is based on the page user currently viewing.

That’s why messages_get_unread_count() works everywhere when user is logged in, while bp_get_members_component_link() will work…[Read more]