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