[Joe]

I think I may have found a solution. I edited wp-login on line 437:

if ( is_multisite() ) {
// Multisite uses wp-signup.php
wp_redirect( apply_filters( ‘wp_signup_location’, get_bloginfo(‘wpurl’) . ‘/wp-signup.php’ ) );
exit;

I just commented out those lines so that there is no redirect, and it seems to be working. My one concern is that I am not using wp-signup, like WP 3.0 Multisite registration is intended to do. Will there be any issues down the road with users being improperly registered or anything like that? What is the real difference between “wp-signup.php” and “wp-login.php?action=register” anyway?

Thanks!

[Joe]

so there is no way to escape this? I ask because my site is not based around a user community, that is just one feature. Therefore, I don’t want every registration to be based around buddypress.

One thing that might help matters –
I have the buddypress part of my site set up on it’s own wordpress install (multisite 3.0). Maybe I can make it so the buddypress registration isn’t applied to the entire network, but just the buddypress site.

I already tried adding the following line to my wp-config:
define( ‘BP_ROOT_BLOG’, 2 );

However, it hasn’t seemed to make a difference.

Anyone?
Thanks again.

[Joe]

Yeah, I know it is a little backwards, hah. I just like the idea of using wordpress as the UI for my community. Actually, I found something that is pretty close to what I need. It is still being developed, but it looks promising:

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

[Joe]

Thanks for the reply.

I know how to disable buddypress components, my bigger question is how to display everything in the wordpress backend (which I see you asked about at the end of your reply). The reason that I want to do this is because I have several other user related tasks integrated into the backend, and I want buddypress there as well (mostly just for uniformity).

-Joe

[Joe]

Anyone? I have spent a couple days scouring the internet for someone else who has done this. Who can help?