Do you mean BuddyPress users accessing the main WP site? BuddyPress users and WordPress users are the same, perhaps with different roles and capabilities but they all live in the users table. So two-way access shouldn’t be a problem.
If you feel multisite is the way to go, then I’d suggest you set up a test install first to try it out. Creating a network will add lots of new tables to your install and rolling back won’t be easy.
Your theme not being suitable for standard pages isn’t reason enough to use multisite. It might solve your problem but it is kind of like using a sledgehammer to crack a nut. Have a read of this article, it will give you some things to think about before you go down the multisite path.
If I understand your requirements right, I wouldn’t use multisite for this. I also wouldn’t use separate installs.
Considering you just need a main site area and a BuddyPress area, I would aim to keep things as simple as possible and address this problem with a custom theme. You can add a /your-theme/buddypress/ folder which contains all of your BuddyPress templates. Then it’s just a case of styling both the main area and your BuddyPress pages to look consistent.
I suspected that might happen. The problem is here $willie = my_f();. In this particular case you can’t do that. I may have mislead you earlier so I’ve updated my reply here.
That’s usually fine to do but be careful in this case. Our my_f() function is hooked to the filter bp_core_activate_account. That particular filter executes at a given time only. So your statement $user_id = my_f(); is not useful. $user_id will be undefined.
@william_oneb technically yes. If bp_core_activate_signup( $key ) is successful then it will return a user ID. So
function my_f( $user_id ) {
// You can do something with $user_id here. Note though, the return value of
// bp_core_activate_signup() may be false. In that case,
// the value of $user_id here will be false.
return $user_id;
}
add_filter( 'bp_core_activate_account', 'my_f' );
To change the background colour, you’d use the background-color CSS property:
#element {
background-color: #000;
}
Where #element refers to the form element used in your HTML (the way to target this particular element is theme-dependent). Check out the Getting started with CSS MDN guide for more info on how to write CSS.
The @-name you see is slightly different to the “full name” displayed in user profiles. The @-name can be thought of as a username; a unique identifier for that member. The full name is just a line of text that can be anything the user likes. Two users can have the same full name, but no two users can have the same username.
If a user can log in, then they are a member who has a profile page. This is regardless of whether they have activated their account. Of course, non-activated members can’t do much as their site usage is restricted.
BuddyPress uses a Template Hierarchy, just as WordPress does. If you have a copy of activate.php in your theme, BuddyPress will look for it and load that in place of the core template file. See the article for more info.
