BuddyPress.org

Yep, like @hnla said. BuddyPress’ DB requirements are the same as WordPress’.

An aspect like DB is really A WP one rather than BP one. BP as a plugin running under WP uses the DB as created initially by WP so if WP is running or able to run on … then BP will.

https://wordpress.org/about/requirements/

It is recommended that 5.6.0 be used but WP will run on older versions.

@jek-fdrv,

we’ve discussing about this “tab” issue on this ticket:
https://buddypress.trac.wordpress.org/ticket/7304

I invite you to jump in if you have any comments. You might also find a solution for your use case.

This page has my own suggestions to try to avoid spammers, this combo dramatically cut down on the number of spam registrations and those that get through I hold them in a queue with BP Registration options a ban then based on discrepencies in their registration information.

http://buddyuser.com/setting-up-wordpress-ready-for-buddypress

It relate to this filter bp_get_profile_field_data

This example will hide tabs and fields to all except admin

function bpfr_hide_profile_field_group( $retval ) {
	if ( bp_is_active( 'xprofile' ) ) :	
	
	// hide profile group/field to all except admin	
	if ( !is_super_admin() ) {		
		//exlude fields, separated by comma
		$retval['exclude_fields'] = '1';  
		//exlude groups, separated by comma
		$retval['exclude_groups'] = '3'; 			
	} 
	return $retval;		
	
	endif;
}
add_filter( 'bp_after_has_profile_parse_args', 'bpfr_hide_profile_field_group' );

These tricks hide the tab content, not the tab itself. (it seems that it doesn’t work for groups at the moment…i asked devs for information) Use CSS display:none to hide the tab or consider this plugin.

Once registered you have no other choice as to remove them manually.
To retain spammers, there many plugins and methods. Afaik none is the perfect solution and in many situation, you’ll need to use a mixed protection.

There many topics on the forum about spam… Search them and make your opinion.
That said, you might follow some basics to harden WordPress, which is a good debut (table renaming, ban “admin” as username, etc). After that, a bunch of anti-spam plugins will calm down their activity on the site. (ban-hammer, buddypress honeypot, etc) Also keep in mind that you won’t probably never avoid spammers. But there is a big difference between 2 spam/day and 1000/per day. 😉

As site admin you can create new users and give same a low strength password. This is basic WP management. You already have a link for this part of the work.
If you have “hundreds” of friends to add it is of course a bit different – meaning it will not be done in 5mn. But it is not to me to tell you how to do this and where to find any knowledge document to achieve it. Codex are made for this – but sorry, i can’t sytematically lead any question asked on this forum to the appropriate page. My brain is not a codex summary ! Hope you understand. 😉

You have to search on WP Codex and eventually on BP Codex. Essentially because of the phone number field, which is a custom field. You can do that with or without BP – and that’s why i said it’s not a BP question.

If you want to take the BP route, you might check the code from BP Default Data, to understand how this plugin insert fake content to BuddyPress.

Did you try this? https://wordpress.org/plugins/simple-terms-and-conditions-for-buddypress/

Does the server has the minimum requirements to run WP and BP ?
What about the htaccess file ? When you moved the site directory, have you regenerate this file ?

About blank pages

We asked around a few people on Friday and no-one has any ideas how this might have happened unless you – or your host – has edited the WordPress PHP files. I haven’t seen other reports yet, so it’s probably related to your install somehow.

The issues here are being tracked in https://buddypress.trac.wordpress.org/ticket/7298 and https://buddypress.trac.wordpress.org/ticket/7300

dbDelta is a WordPress function, @danbp, it’s not bbPress specific. It’s used to update the schema of a MySQL database. The bigger question is how did something trigger the BuddyPress installation methods yet not make sure the relevant WordPress function was loaded.

@nhatnnt1 What version number of WordPress are you using?

I think with multisite, WordPress user registrations only occur on the main/root site. I don’t know how BP_ENABLE_MULTIBLOG works with this (i.e. I can’t remember if the registration redirect happens). It’s been a while since I’ve used it.

If you’re a little technical, you could test it, and then look in the database afterwards — probably the wp_x_users, wp_x_usermeta, wp_x_signups tables, and see if there’s any field such as a blog ID or blog URL set somewhere for the new users that you could use.

Otherwise, I think you’d have to code something up.

So… you CAN log into WordPress with your email address and password. On example.com/wp-login.php, it even says “Username or Email” and “Password”. Is this the main log in that you are talking about?

I have just tested the BuddyPress log in widget and I can log in using the email address.

I am a bit baffled why this doesn’t work for you. Please can you remove any relevant code customisations, and just test it again?

If you can’t log into /wp-login.php using an email address and password, you should try the WordPress.org support forums first and get that fixed, because that’s how it should be working.

Hi @romanreignempire

You need to change a WordPress settings — you need to enable permalinks. Your WordPress blog URLs look like: example.com/index.php/roman-reigns/ and we need to have them look like example.com/romain-reigns/. This is required to have BuddyPress work.

If we’re lucky, you can go into wp-admin and Settings > Permalinks, then pick anything other than “Default”. Then save, and check if your blog post links have changed, and if they still work.

If they DON’T work, you need to fix that first. There is lots of information on the web about enabling WordPress permalinks, and if you have a good web host, oftentimes they will know how to enable them if they are disabled by default for some reason.

I guess that means that when a user registers on one of the multi-sites he can use his account on all the other websites of the Multi-site installation, right ?

Yes, but understand that you have to give that user access to those other sites (in wp-admin) to write blog posts, for example. If a user does not have explicit permissions to a specific multisite site, they won’t have any special access; they’ll only be able to read the content as if they were another normal visitor. You can test this right now, without BuddyPress, and see how it works.

meaning it takes him out of the French Website to put him onto the English on

You seem to be using multisite to have your content localised into different languages. This is a common approach for WordPress multisite, but BuddyPress does not work the way you want it to in this situation.

You can activate BuddyPress in a few different ways. Simply, on multisite, you can activate the plugin on a specific site, or network-wide. There is lots more detail at https://codex.buddypress.org/getting-started/installation-in-wordpress-multisite/ but if BuddyPress is activated network-wide, all the BuddyPress content will only appear on one site (we call this the “root blog”). We use redirects to support this, exactly as you’ve found.

You can’t have BuddyPress active on a multisite that uses the sub-sites as different languages, and have the BuddyPress social network appear on all of them and work in the same way, except with different translations. It doesn’t work that way out the box…

…however here is an advanced setting you can use to make BuddyPress behave like this: BP_ENABLE_MULTIBLOG

See https://codex.buddypress.org/getting-started/customizing/bp_enable_multiblog/
I would encourage you fully test this setting out if you enable it, before you start building the rest of your site, just to understand and confirm its behaviour.

🙂

@dioniq Did this work with a previous version of BuddyPress? If so, what version?

While the developers of that plugin are contributors to BuddyPress, you’re best to try requesting support via that plugin’s forums: https://wordpress.org/support/plugin/buddypress-docs