BuddyPress.org

I’m trialling Flyzoo chat… it uses buddy press logins as username and users can upload avatars, and they have told me that within a week they should have update to restrict guests, so chat does not show up on front page unless user logged on. Its hosted on the cloud, so no load on your host..It is not free but for what you gets its cheap..starts at 1.90 per month. I’m new to WordPress, but it seems good. Support responds really fast which is always a bonus..
Hope that helps..
http://www.flyzoo.co/

Is there an easy way to do this?

Yes. You can do this quite easily.

1. Choose a Facebook login plugin from the WP plugin repo:

https://wordpress.org/plugins/

Maybe try searching for 'social login'

2. Hide the BuddyPress registration form

Just bypass the login page with something like wp_set_auth_cookie( 1, false, true ).

Where 1 is the user ID of your admin account.

https://codex.wordpress.org/Function_Reference/wp_set_auth_cookie

sem101 – I use two plugins that ask questions before signup

Buddypress Humanity
and
Good Question

This prevents most of the bot sign ups that we plaguing us for some time with those group creators.

This does not stop the manual spam signups, so we have delete a few accounts each week, but it has prevented the tons that we were dealing with before.

We used to have good luck with /bp-registration-options/

but we started having some issues around bp1.7 I think. Other people say it works now (https://buddypress.org/support/topic/feature-request-new-user-moderation/ ) – but I don’t have time to play with half baked / half working solutions. Your experience with it may be fine.

We do not use si captcha any longer as we had issues with some multisite problems. I do think it slowed down some of the spammers, and certainly cost them time and a little money to get around it – so it’s cool.

I use one of the blog defaults type plugins to auto set new blogs/(sites) to have settings like ‘users must be logged in to comment’ – and “discourage search engines from indexing” – this has helped a bunch for us.

Of course the manual spammers will still need to be manually deleted – you will never stop the manual spammers, if you did, then you would stop regular people from signing up. Unless of course you went for one of those “invite only” buddypress setups.

I recently donated to a plugin author to create a new plugin that allows superadmins to force certain settings on sub-site/sub-blog users.. like forcing only allowing registered / logged in users to comment. That plugin is working, but it is not quite polished enough for wp repository release I think – but that is another kind of spam blocking issue.

Hope these tips help you, they have made a huge difference for me.

arg – tried to post a reply and I think it got akistmetted for having two links…
/wonders why they do not whitelist links to wordpress org / buddypress org here for that setting somehow.. sheesh

sem101 – I use two plugins that ask questions before signup

Buddypress Humanity
and
Good Question

This prevents most of the bot sign ups that we plaguing us for some time with those group creators.

This does not stop the manual spam signups, so we have delete a few accounts each week, but it has prevented the tons that we were dealing with before.

We used to have good luck with https://wordpress.org/plugins/bp-registration-options/screenshots/

but we started having some issues around bp1.7 I think. Other people say it works now (https://buddypress.org/support/topic/feature-request-new-user-moderation/ ) – but I don’t have time to play with half baked / half working solutions. Your experience with it may be fine.

We do not use si captcha any longer as we had issues with some multisite problems. I do think it slowed down some of the spammers, and certainly cost them time and a little money to get around it – so it’s cool.

I use one of the blog defaults type plugins to auto set new blogs/(sites) to have settings like ‘users must be logged in to comment’ – and “discourage search engines from indexing” – this has helped a bunch for us.

Of course the manual spammers will still need to be manually deleted – you will never stop the manual spammers, if you did, then you would stop regular people from signing up. Unless of course you went for one of those “invite only” buddypress setups.

I recently donated to a plugin author to create a new plugin that allows superadmins to force certain settings on sub-site/sub-blog users.. like forcing only allowing registered / logged in users to comment. That plugin is working, but it is not quite polished enough for wp repository release I think – but that is another kind of spam blocking issue.

Hope these tips help you, they have made a huge difference for me.

Roles (and responsibilities) are handled by WordPress. See here for more info:
https://codex.wordpress.org/Roles_and_Capabilities

@okamiokami
You can test some of the solutions in this ticket that simply stops the activation email from being sent then use BP’s new build in activation to manually activate the users. Of coarse I haven’t tested this but its worth a shot.
https://buddypress.trac.wordpress.org/ticket/3443

https://wordpress.org/plugins/stop-spammer-registrations-plugin/

Above plugin is the only plugin you will ever require to stop spam. Donate to plugin author if it stops spam on your site to keep the plugin alive

https://wordpress.org/plugins/stop-spammer-registrations-plugin/

Above plugin is the only plugin you will ever require to stop spam. Donate to plugin author if it stops spam on your site to keep the plugin alive

https://wordpress.org/plugins/stop-spammer-registrations-plugin/

Above plugin is the only plugin you will ever require to stop spam. Donate to plugin author if it stops spam on your site to keep the plugin alive

Of course you can change these tab labels.
Read here and here for general information.

It’s possible that the problem comes from your theme or a plugin. You have to debug…:evil:
First thing to check is the content of your language folder.
Normally buddypress-xx_XX.mo/po files are in wp-content/languages/
See also if you have a “plugin” folder in “languages”. Maybe you have a second buddypress-xx_XX.mo in it. In this case, it is this file who has priority over the other. If you have a custom translation, you have to place it in this folder anyway.

Second thing to check are the theme/(possible)plugin translation vs. BP translation.

FYI, since BP 2.0, WP/BP/bbP translations are automatically updated from Translate WordPress (Glotpress), but you have to ensure that you have the correct version. Simply open the .po file with a text editor like notepad++ and read the header content.

If the above debuging process have no result, here’s a good solution by Alex (@viper007bond) to “force” a translation or customizing an existing.
Successfully tested on BP 2.01 ! 😉

https://wordpress.org/plugins/activate-users-in-buddypress

basically you need to get the Last Activity field set for this users manually.

@robertnorcross Just to let you know I am just learning to figure so of these out. So this is what I think I understand it works:

multisite install by default allows users to login with same info.

you may also want to post over on wordpress support forum for multisite.

I was reading so article & now don’t remember that subscriber on multisite don’t automatically become members which confuse me know.

I am pretty sure there is probably login redirect plugin but haven’t used any to recommend.

I am also unfamiliar with commerce sites but do you want to redirect someone before they complete their purchase to buddypress.

I think multisite forum may be could more helpful and to be honest I thinking of just going back to single installs & migrate later. I have multiple sites like you too with various focused it has been challenge wrapping my head around it all.

This plugin, though not updated for a very LONG time, still works.

Might be a LITTLE help in the ongoing battle against spam!

https://wordpress.org/support/plugin/buddypress-humanity

Security question/answer can produce a text-string, not just a sum, answer.

Yes, the above is a rather awkward solution.

Just occurred to me that you could extract the info you need from the $settings_link arg passed by the $email_content filter hook to further query the database and/or rebuild $email_content – and so avoid filtering wp_mail

I think it would be a reasonable request that the
$email_content filter hook in messages_notification_new_message include $ud.

It’s a simple change, so please submit an enhancement ticket:
https://buddypress.trac.wordpress.org/

[ We may find out that there is an existing and simple solution ! ]