Good note. http://www.example1.com is an online book store and it uses the WooCommerce plugin. http://www.example2.com is a website for prayer leaders, specific to a denomination of religion and http://www.example3.com (this one has buddy press) is a website for prayer leaders, that is not specific to a denomination.
The idea is that the user will have one login – so that when they check their orders on http://www.example1.com (online book store) they have the same login as http://www.example2.com and http://www.example3.com. The other idea, and the main one of all, is that http://www.example2.com (a website for prayer leaders, specific to a denomination of religion) and http://www.example3.com (this one has buddy press) [website for prayer leaders, that is not specific to a denomination] – these two, when a user logs in, would both feed into the website that has BuddyPress. So, one login overall on the entire network and one BuddyPress location. I don’t need any separation on the websites like, accounts or separate forums, BuddyPress profiles, etc.
I’m looking for one login. I’m looking also for a way that if a user logs into http://www.example1.com (online book store) or http://www.example2.com and they are trying to access anything involving BuddyPress (which is on http://www.example3.com), that they are sent to that site. Right now when if I network activate BuddyPress they can use the same login no matter what website they are on, but if they click on their profile or anything like that they stay on the current website and BuddyPress takes the face of that website. However, If they do that on mine I want them taken from one of the sites and sent to http://www.example3.com (this one has buddy press).
Well, here is a question on top of that. What if I only have BuddyPress activated on one website within the network (it is NOT network activated right now). Do I need to network activate it for the steps your proposed to work?
The reason I haven’t network activated it is because when people would log in to their account on http://www.example1.com that site would then have BuddyPress on it (BuddyPress would use the face of that website to display content). I don’t want that happening. I want them led to http://www.example3.com (this one has buddy press) for anything involving BuddyPress because the theme is formatted to work well with BuddyPress.
The codex page worked great. I used this bit of code: define( ‘BP_ENABLE_MULTIBLOG’, true );
That allows people to do things within their profile on each site. So, it won’t lead them to the primary domain each time – it will keep them on the site they are currently on. Perfect.
