BuddyPress.org

https://wordpress.org/extend/plugins/unconfirmed/

jpeg_quality is deprecated since WP 3.5

use wp_editor_set_quality or WP_Image_Editor::set_quality() instead
source: codex.wordpress.org/Plugin_API/Filter_Reference

Hi,

If i understand well, i only need to add the code below (where 3 is the secondary blog ID) in wp-config.php, right?

`define ( ‘BP_ROOT_BLOG’, 3 );`

But where exactly? Does it make any difference if i place it one line or the other? Where should i put it? Before and after which line?

By the way, i guess i will, but could someone please confirm i can have a different and independent buddypress install for each of the blogs in the wordpress multisite network?

I got this site after my predecessor, so I wasn’t involved in the decision process.

Who cares !

Latest stable BP is version  1.6.3 and yes combining slightly different things is not the best practice.

Recommandation is to use it on WP 3.5
Read here in the sidebar:
https://wordpress.org/extend/plugins/buddypress/

BP 1.5.2 required at least WP 3.3 (déc. 2011)
changelog https://codex.wordpress.org/Version_3.3
changelog https://codex.wordpress.org/Version_3.4
changelog https://codex.wordpress.org/Version_3.5

Also what theme do you use and have you deactivated all plugins while debugging ?
Passwword management is done by WP

Anyway, you need to fix WP registering first on twenty10, than together with BP on the bp-default theme

What does it mean to be BuddyPress compatible anyway? Why is it that the best plugins, SocialAuth-WordPress, WordPress Social Login, AddThis Social Sign In aren’t ‘BuddyPress optimized’?

I’m having a developer implement one of these for our site, and I’d be glad to share what we needed to do to ensure that we have a registration form with a few required fields, and existing users can use this service as well.

Unfortunately none of these really stand out for a Facebook/Google/Twitter option:

BuddyPress compatible
LoginRadius – External service. Customizing registration page requires $49/mo. option.
WP-FB-AutoConnect – Facebook only. Creates duplicate users?
BuddyPress Facebook Connect+ – Facebook only. $30 (3-months) to $99 (year) to update plugin.
OneAll Social Login – Not customizable. Free up to 2500 users.

Not designed to be BuddyPress compatible
SocialAuth-WordPress
WordPress Social Login
AddThis Social Sign In

Hi @djpaul , @mercime , @chouf1

Finally, i made 2 versions tonight the 1.0.3-beta1 is taking in account Paul’s review. Then i thought, what about filtering the topic by support status in the backend Topics list ?

So i made 1.1-beta1, here’s an illustration
https://github.com/imath/buddy-bbPress-Support-Topic/blob/master/screenshot-5.png

Master is latest.
https://github.com/imath/buddy-bbPress-Support-Topic

If everything is ok, then i’ll publish 1.1 to WordPress repo.

Good night.

@backyardmech Check out http://wpmu.org/how-to-build-a-facebook-style-members-only-wordpress-buddypress-site/

Last BuddyPress Groupblog here:
https://wordpress.org/extend/plugins/bp-groupblog/

There are role level plugins but as @hnla has stated they do not work with registration. You would need to set levels yourself or create custom registration screens.

https://wordpress.org/extend/plugins/role-scoper/

I did find this one: Tagged User Notification It seems to be working so far.

@mercime

http://bpsocialnetwork.wordpress.com//?s=buddypress&search=Go

Very nice, imo, should be a sticky in the How-To forum.

Still has no idea how to create these subdomains

Before you can use Group Blogs plugin, you need to create a network first (go multisite) https://codex.wordpress.org/Create_A_Network

Something like this may help though that version is not the most recent.

https://wordpress.org/extend/plugins/buddypress-group-blog/

there IS a version 1.8 that has been tested up to Tested up to: WP 3.4.1 / BP 1.6. its out there somewhere

hi mblanco,

Be aware that BuddyPress does not work on installations where you give WP it’s own directory
https://codex.buddypress.org/user/before-installing/

But on a network install you can do this
https://codex.buddypress.org/user/install-buddypress-on-a-secondary-blog/

Please also post at https://wordpress.org/support/plugin/buddypress-activity-plus

https://wordpress.org/extend/plugins/remove-dashboard-access-for-non-admins/

The link that was stripped from my last post is (hopefully):

https://make.wordpress.org/core/2012/12/12/php-warning-missing-argument-2-for-wpdb-prepare/

BuddyPress Pending Activations has not been updated for quite a while now – back in 2011 I think – and it is not ‘officially’ compatible with WordPress 3.5 or BuddyPress 6.

I have just tried it on a test site with these latest versions and it does seem to be working for me.

It does however create Warning errors (which will show up in admin if you have display_errors turned on) because it still uses the prepare() function with one argument. See for an explanation.

The warnings I get are like
Warning: Missing argument 2 for wpdb::prepare(), called in /xxx/wp-content/plugins/buddypress-pending-activations/bp-pending-activations.php on line 18 and defined in /xxx/wp-includes/wp-db.php on line 990
Warning: Missing argument 2 for wpdb::prepare(), called in /xxx/wp-content/plugins/buddypress-pending-activations/admin/bp-pending-activations-admin.php on line 6 and defined in /xxx/wp-includes/wp-db.php on line 990

If you want to hack the plugin to stop the errors I think there is one instance in bp-pending-activations.php and several in bp-pending-activations-admin.php.

@miskostanisic,

if you have no particular reason, it would be better that you install wordpress at the site root (example.com/)
What php and mysql version are installed on your host ?
Check also phpinfo(); and look how much php_memory_limit is attributed to your site

once activated: https://codex.buddypress.org/user/setting-up-a-new-installation/installation-wizard/

Make sure WordPress is up and running by making a post, a page, a comment and adding media via media upload. Then activate BP.

yes, i checked it. But now you did the changes, we’re sure (for the moment) that the bug is elsewhere.

If you want answers from the dev i suggest you to open a ticket on the trac with as much details as possible and a link to this discussion, too.

https://buddypress.trac.wordpress.org/report

you can login with same credentials as here.