BuddyPress.org

Hi @kaosone1975,

add those snippets to bp-custom.php and give a try:

function bpfr_redirect() {

	if ( bp_is_current_component( 'register' ) ) {
		wp_redirect( get_option('siteurl') . '/wp-login.php?action=register' );
	} 

}
add_filter('get_header','bpfr_redirect', 1 );

function my_disable_bp_registration() {
	remove_action( 'bp_init',    'bp_core_wpsignup_redirect' );
	remove_action( 'bp_screens', 'bp_core_screen_signup' );
}
add_action( 'bp_loaded', 'my_disable_bp_registration' );

@phound1

have you tried to see if bp emails work when the other plugins are disabled?

maybe some of things we posted about in the forums long ago may offer some clues as to where the hiccup is. I stiff refer to https://buddypress.org/support/topic/not-receiving-notification-of-new-user-registration/ on occasion.

Try this (goes to bp-custom.php )

function my_disable_bp_registration() {
remove_action( 'bp_init', 'bp_core_wpsignup_redirect' );
remove_action( 'bp_screens', 'bp_core_screen_signup' );
}
add_action( 'bp_loaded', 'my_disable_bp_registration' ); 

function my_redirect_signup_page(){
	//return wp_registration_url(); 
	return bp_get_root_domain() . '/wp-signup.php';
}
add_filter( 'bp_get_signup_page', 'my_redirect_signup_page' ); 

Welcome Pack! Small world.

Can you try disabling Welcome Pack? That certainly interferes with user registration.
Please also try disabling iThemes Security.

Then, test registration again, and see what happens.

If it still doesn’t work as expected, if you can switch your theme to one of the default WordPress themes (leaving those two plugins disabled), test again. If you have a test environment (say you might be using Pantheon hosting, for example), this should be easy to do, though if it’s only one server, I appreciate you might not want to modify your production site too much.

I’m not sure what behavior you’re aiming for, but this snippet will disable the confirmation email and log the user in automatically upon successful registration.

<?php 
add_action( 'bp_core_signup_user', array( $this, 'disable_validation_of_new_users' ) );
add_filter( 'bp_registration_needs_activation', '__return_false' );
add_filter( 'bp_core_signup_send_activation_key', '__return_false' );

function disable_validation_of_new_users( $user_id ) {

	// Get the user's activation key for BP. This is the activation_key in user_meta, not the key in the user table.
	$user_key = get_user_meta( $user_id, 'activation_key', TRUE );

	// Activate the signup
	$awuser = apply_filters( 'bp_core_activate_account', bp_core_activate_signup( $user_key ) );

	// Automatically log the user in.
	// Thanks to Justin Klein's  wp-fb-autoconnect plugin for the basic code to login automatically
	$user_info = get_userdata($user_id);
	wp_set_auth_cookie($user_id);

	do_action( 'wp_signon', $user_info->user_login );

	bp_core_add_message( __( 'Your account is now active!', 'my-plugin-slug' ) );

	buddypress()->activation_complete = true;
}

I also tested BP 2.5.3 on WP 4.5.2 on a fresh install and cannot duplicate your problem, Earl_D.

I tested with the Extended Profiles component enabled.

Are you using any caching plugins? If so, try to disable it or whitelist the register and activate pages from caching.

Do you have any special extended profile registration fields? If so, can you list what they are and how they are configured?

I turned off all Plugins except WordPress and Buddypress and this issue still occurs.

Are you sure you disabled all plugins except BuddyPress? If so, check for any rogue code snippets in your theme’s functions.php or wp-content/plugins/bp-custom.php.

Once that is done, delete all registration pages you have set up in WordPress. Create a new WordPress page to be used for BuddyPress registration. Just enter a post title and hit “Publish”. Also, ensure all your pages in the “Pages” trash are deleted.

Next, go to “Settings > BuddyPress > Pages” and set the “Register” page to the page you just created.

I cannot duplicate this problem with Theme My Login.

I’m using the default Theme My Login settings untouched and was able to go to the register page and successfully submit the form with no redirections.

Make sure for BuddyPress that you selected the BuddyPress “Register” page and not TMLs.

Also disable any plugins that might be interferring with registration like New User Approve, etc.

I have similar problem. and also I can’t find anywhere here CREATE NEW TOPIC / POST link I am using this one.

When I installed buddypress our site registration option was disabled. So I enabled it now, and then used REPAIR option –> The following active BuddyPress Components do not have associated WordPress Pages: Activate, Register. Repair <– But the problem is that REPAIR does nothing. How to fix that problem and create these registration and acitvate pages?

Also I noticed from installation manual something weird –> Make sure you have pretty permalinks enabled on your WordPress install. <– WTF is that? There in wordpress does not exist option like pretty permalinks. You have plain, numeric, Post name, and other options, but not “pretty permalinks”. Anyway I am using date/postname version at the moment, it should be pretty enough, but still where is that “pretty permalinks” option and where I should find it?

> I meant how do I disable registration?
Go back to where you enabled it in Settings > General for single site or in Network Admin > Settings if you’re on multisite.

first test with default 2014 or 2015 theme – and all other plugins disabled except bp – does it work then? If not…

previous forum posts maybe helpful –
(let us know what you find works!)

With a new bp setup I usually check these things first if email are not seeming to send or go through ->https://buddypress.org/support/topic/activation-e-mail-failing-to-send/#post-241079 (From a recent similar thread)

Better to check the basics before digging into whether it’s a email header config on the server, php settings limiting functionality – need for wp to send as smtp plugin – something just with gmail blackhole filtering –

so many different things can affect wp sending, bp sending, your web serving sending email as php, or an email service accepting something that was sent, much less put in the actual inbox instead of junk mail / promotions box or whatever…

=-=- also from danbp about 8 months ago:
When encountering a registration problem, first thing to do is to test your install without any plugins and one of WP’s Twenty default theme. Ensure that your site send correctly emails. Before activating any plugin, your base WP install must work.

Once WP is OK – you can install BuddyPress and check your permalinks. Pretty permalinks must be activated to get the plugin working correctly.

This point is important, especially if you have redirection issues after BP is activated.

Second point to check is your theme installation.

Proceeding like this will help you to isolate easely the culprit. If:
– WP install: OK
– BP install: OK
– theme activation: problem

So you know here the problem comes from.

While testing your install, you can activate wp_debug (set to TRUE) in the wp-config file. This can give you a lot of information about conflict and/or errors.

Just keep in mind that these information have 2 levels of importance: notice and warning.
While notice are generally harmless, warnings should be taken seriously in account and solved.

If WP is the problem, see first the wordPress support
If it’s BuddyPress, see the BP support
If it’s the theme, see the theme support
If it’s any other plugin, see first the plugin support.

That’s strange and shouldn’t be happening. Can you activate TwentyFifteen, disable all plugins and then try a test registration?

You shouldn’t need to disable the activity stream commenting – but try it.

There are several plugins re bbPress spam, such as:
https://wordpress.org/plugins/stop-spammer-registrations-plugin/

Update: Turns out another plugin had caused this error, and it is repaied now. The name of it was Frontend or something like that, it disables access to things like the registration and such for security, and idk how I missed that, but yeah.

Thanks for the fix!