BuddyPress.org

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 🙂

Hi there Justin,

I’ve run into a similar issue but in reverse.

We’re in the process of migrating an individual WordPress site with BuddyPress to a multi-site WordPress with BuddyPress.

In my case, the normal practice would be to rename the WordPress tables from wp_ to something like wp_99_* , where 99 represents one of the site IDs.

The tool I used called “Export2 Multisite”, does a great job at fixing the table names.
However, it’s not smart enough to handle the data merge of the wp_bp_* and wp_rt_* table names.

Regardless, I’m seeing the same symptoms on the site I migrated from a single WordPress install to a multi-site WordPress.

So, any help whatsoever from this community on migrating sites with Buddypress either coming FROM or TO a multi-site would be GREATLY appreciated!

Hi

We’ve been testing against PHP7 nightly releases for a long time. It helps that our PHP is newer than most of WordPress’, so we have less really old stuff to migrate.

You can view our test coverage on https://travis-ci.org/buddypress/BuddyPress/ (“PHP: nightly” is PHP7), as you can see, there’s currently a failure with one test that we need to fix. It looks fairly straightforward to fix, and we’ll do that soon.

This one test aside, to the best of knowledge, yes, BuddyPress works with PHP 7.

Good question! This is likely to being looked at by the core team.

See this post which describes what is being done by the WordPress core team: https://make.wordpress.org/core/2015/09/10/wordpress-and-php7/

My guess is the BuddyPress core team are doing something like that. Maybe @djpaul can add something here?

Hi,

of course, in so far that php 7 will be used by WordPress. BuddyPress’s dev follow the same route.

WordPress and PHP7

https://buddypress.org/support/topic/change-name-view-in-profile-menu/

@wecreatehype Have you done any basic troubleshooting like deactivating other plugins except BuddyPress and changing to the WP default theme? Also, do provide more information about your installation so we won’t be chasing ghosts. https://buddypress.org/support/topic/when-asking-for-support-2/

I have read many stories about converting BuddyPress to BBPress format

@netentry Just to clarify that the only converting we ever did was to import content from the very old stand-alone bbPress 1.x.x versions included in very old BuddyPress installations into the bbPress 2.x.x plugin a long while back. That’s it. BuddyPress itself cannot be converted into bbPress forums.

Are there any good tools for performing a BBPress-to-BuddyPress conversion?

Another clarification here. BuddyPress is not a forum. It is a social network plugin with many components which could have Sitewide and/or Group forums if bbPress 2.x.x is installed and activated.

So in your case, if you only have the bbPress plugin activated, you could install and activate BuddyPress and set it up in the bbPress Settings screen to allow Group forums in addition to the Sitewide Forums. Take note however, that if you activate bbPress and BuddyPress at the same time, the BuddyPress member profile pages will trump (or will show up instead of) the bbPress member profile pages.

This sounds doable theoretically. But i am sure there will be implications 🙂

abc.com – table prefix wpabc_
xyz.com – table prefix wpxyz_

Now in xyz.com, if you want to use buddypress tables of abc.com, go to active theme of xyz.com > functions.php and add the following code: ( untested )

add_filter( 'bp_core_get_table_prefix', 'bporg_244943_change_table_prefix', 99 );
function bporg_244943_change_table_prefix( $prefix ) {
    return 'wpabc_';
}

I’d vote for boss theme too. It looks awesome and is specifically built for buddypress network sites.
http://www.buddyboss.com/product/boss-theme/. You might want to check its live demo.

Hey @wecreatehype

Feel free to show off your community in the Your BuddyPress forum. It’ll be great to see a live version of Boss “in the wild”.