BuddyPress.org

This seems to be part of the way Buddypress works, you can’t change your login name and this is the name it uses for messaging, hence the @name issue you mention. it means that users can get pretty confused if people change their display name.

I’m not aware of anyway to change this.

Try using the Buddypress Registration Options plug in, I use this and it sends me an email once when they first register and then another once they have activated their account.

Thank you for that, Venutius. After a good night’s sleep and some more playing around, it dawned on me that I don’t have to put all of the BuddyPress links in the main menu, especially since they are linked to from profiles. However, all those links I mentioned are still visible by logged out viewers, ie, .com/members/ .com/activity/ etc. Is there a way to block these pages from public view?

BuddyPress uses a Template Hierarchy, just as WordPress does. If you have a copy of activate.php in your theme, BuddyPress will look for it and load that in place of the core template file. See the article for more info.

In the Buddypress pages setting, try setting the activity stream to point to your “Activity” page, that should work, you should then see all the activity on that page.

How does MediaPress compare to rtMedia?

I haven’t used Mediapress myself but I know it’s quite popular here in the BuddyPress community.

How does MediaPress compare to rtMedia? Does it also work with bbPress? I’m surprised I’ve never heard of it, but I’m getting curious.

And @jrunfitpro, rtMedia is another option. I believe it also used to be referred to as BuddyPress Media.

Check out the Customizing Labels, Messages, and URLs article. You can use a language file to “localise” BuddyPress strings.

Yes you sure can use multisite + buddypress( network activated ) to achieve this.
But merging two existing sites under one multisite will need shuffling things here and there. And as you are saying both websites use multiple themes, things might get tricky 🙂

BuddyPress was released in 2009. Custom Post Types were introduced into WordPress in mid-June 2010 so there was no way the original BuddyPress crew could have used them.

Also, the use of custom tables isn’t always a bad thing. If the situation calls for them after careful consideration then you should use them.

In the case of BP, the database schema is sound, queries are optimised and everything is generally done “the WordPress way”. Personally, I don’t think of BP tables as “custom”. I think of them as an extended set of WordPress tables that get activated if you want social features with WordPress.

You should post this question on the plugin’s support forum as this related to the buddypress-activity-privacy plugin.

Can BuddyPress be re-coded to use custom post types?

Yes, but not very easily. An almost complete re-write of the project would be needed.

I ran into the same or similar issue. From my debug logs it appears to be an issue when login with ajax is also an active plugin…these are the two errors that repeat endlessly until there’s a server timeout:

[03-Oct-2015 22:00:33 UTC] PHP Warning:  current() expects parameter 1 to be array, null given in /var/www/html/_wp/wp-content/plugins/buddypress/bp-core/bp-core-template-loader.php on line 223
[03-Oct-2015 22:00:33 UTC] PHP Stack trace:
[03-Oct-2015 22:00:33 UTC] PHP   1. {main}() /var/www/html/_wp/wp-admin/plugins.php:0
[03-Oct-2015 22:00:33 UTC] PHP   2. require_once() /var/www/html/_wp/wp-admin/plugins.php:10
[03-Oct-2015 22:00:33 UTC] PHP   3. require_once() /var/www/html/_wp/wp-admin/admin.php:31
[03-Oct-2015 22:00:33 UTC] PHP   4. require_once() /var/www/html/_wp/wp-load.php:37
[03-Oct-2015 22:00:33 UTC] PHP   5. require_once() /var/www/html/_wp/wp-config.php:106
[03-Oct-2015 22:00:33 UTC] PHP   6. do_action() /var/www/html/_wp/wp-settings.php:353
[03-Oct-2015 22:00:33 UTC] PHP   7. call_user_func_array() /var/www/html/_wp/wp-includes/plugin.php:503
[03-Oct-2015 22:00:33 UTC] PHP   8. LoginWithAjax::init() /var/www/html/_wp/wp-includes/plugin.php:503
[03-Oct-2015 22:00:33 UTC] PHP   9. LoginWithAjax::getRegisterLink() /var/www/html/_wp/wp-content/plugins/login-with-ajax/login-with-ajax.php:91
[03-Oct-2015 22:00:33 UTC] PHP  10. bp_get_signup_page() /var/www/html/_wp/wp-content/plugins/login-with-ajax/login-with-ajax.php:270
[03-Oct-2015 22:00:33 UTC] PHP  11. bp_has_custom_signup_page() /var/www/html/_wp/wp-content/plugins/buddypress/bp-members/bp-members-template.php:1902
[03-Oct-2015 22:00:33 UTC] PHP  12. bp_locate_template() /var/www/html/_wp/wp-content/plugins/buddypress/bp-members/bp-members-template.php:1885
[03-Oct-2015 22:00:33 UTC] PHP  13. bp_get_template_stack() /var/www/html/_wp/wp-content/plugins/buddypress/bp-core/bp-core-template-loader.php:90
[03-Oct-2015 22:00:33 UTC] PHP  14. current() /var/www/html/_wp/wp-content/plugins/buddypress/bp-core/bp-core-template-loader.php:223
[03-Oct-2015 22:00:33 UTC] PHP Warning:  next() expects parameter 1 to be array, null given in /var/www/html/_wp/wp-content/plugins/buddypress/bp-core/bp-core-template-loader.php on line 229
[03-Oct-2015 22:00:33 UTC] PHP Stack trace:
[03-Oct-2015 22:00:33 UTC] PHP   1. {main}() /var/www/html/_wp/wp-admin/plugins.php:0
[03-Oct-2015 22:00:33 UTC] PHP   2. require_once() /var/www/html/_wp/wp-admin/plugins.php:10
[03-Oct-2015 22:00:33 UTC] PHP   3. require_once() /var/www/html/_wp/wp-admin/admin.php:31
[03-Oct-2015 22:00:33 UTC] PHP   4. require_once() /var/www/html/_wp/wp-load.php:37
[03-Oct-2015 22:00:33 UTC] PHP   5. require_once() /var/www/html/_wp/wp-config.php:106
[03-Oct-2015 22:00:33 UTC] PHP   6. do_action() /var/www/html/_wp/wp-settings.php:353
[03-Oct-2015 22:00:33 UTC] PHP   7. call_user_func_array() /var/www/html/_wp/wp-includes/plugin.php:503
[03-Oct-2015 22:00:33 UTC] PHP   8. LoginWithAjax::init() /var/www/html/_wp/wp-includes/plugin.php:503
[03-Oct-2015 22:00:33 UTC] PHP   9. LoginWithAjax::getRegisterLink() /var/www/html/_wp/wp-content/plugins/login-with-ajax/login-with-ajax.php:91
[03-Oct-2015 22:00:33 UTC] PHP  10. bp_get_signup_page() /var/www/html/_wp/wp-content/plugins/login-with-ajax/login-with-ajax.php:270
[03-Oct-2015 22:00:33 UTC] PHP  11. bp_has_custom_signup_page() /var/www/html/_wp/wp-content/plugins/buddypress/bp-members/bp-members-template.php:1902
[03-Oct-2015 22:00:33 UTC] PHP  12. bp_locate_template() /var/www/html/_wp/wp-content/plugins/buddypress/bp-members/bp-members-template.php:1885
[03-Oct-2015 22:00:33 UTC] PHP  13. bp_get_template_stack() /var/www/html/_wp/wp-content/plugins/buddypress/bp-core/bp-core-template-loader.php:90
[03-Oct-2015 22:00:33 UTC] PHP  14. next() /var/www/html/_wp/wp-content/plugins/buddypress/bp-core/bp-core-template-loader.php:229

Simple fix is to deactivate login with ajax, then deactivate buddypress, then activate login with ajax.

This error might also present itself with other plugins/themes that have custom signup pages.

Questions specific to another plugin are best asked of the plugin creators.
Try http://www.learndash.com/ or https://wordpress.org/support/plugin/buddypress-learndash

Do you have any plugins activated aside from BuddyPress?

If you can think of business pages as “groups” then BuddyPress comes with that functionality. You just need to enable the Groups component and your members will be able to create and invite more members to join the group.

Please include any links to bbPress forums that refer to these statements:

that bbPress function turns out to be riddled with bugs 🙁
(I guess JJJ’s “condemned” remarks would imply the same conclusion?)

>Is there a way to completely disconnect BuddyPress notifications from the bbpress forums?

Try changing this line:
add_action( 'bbp_new_reply', 'bbp_buddypress_add_notification', 10, 7 );
to
//add_action( 'bbp_new_reply', 'bbp_buddypress_add_notification', 10, 7 );
in bbpress\includes\extend\buddypress\notifications.php

It looks as though BuddyPress has got PHP 7 in the bag 🙂