Why have a separate install? Is it because you want it to look different? You can style BP pages differently. Multi site opens a spam can if not completely locked down.
The purpose would be to completely eliminate all Buddypress functionality from the root site. The client wants to link to the /community subdirectory from the root, but does not want admin bars or any of the associated features in the root.
Ideally, Buddypress would be entirely contained in the /community subdirectory. The admin bar and all its functionality would be here. It’s almost as if they were two completely different websites that were associated with one another, but also share a userbase.
Sorry, I’m just trying to explain this clearly. Before I commit the time to the project, I’d like to have a clear idea of what I’m doing and the best way to do it.
Let me know if you need more information.
What’s in the main site? Blog posts?
The only real reason to use multi site is if you want each user to have a blog/site
What you want is easily done with template changes. BP only takes over a site if you allow it.
The main site is being used primarily as an organization website. There is a blog page, but for the most part, they are just pages filled with information utilizing WordPress so that the client does not need to use code to manage their website.
So what you’re saying is follow the steps that will allow the organization theme to play nicely with Buddypress?
Ok, what’s the purpose of the community side? I’m not seeing a reason to have a connection between sites if main site is just informational
@StSmith – we use exactly this setup on one of our client builds.
They have a standard WP install on the root domain for their corporate front end, with a BuddyPress install on a subdomain for their members to access social elements, book events and so on.
They share the same database, and we even ‘share’ some stories from the corporate site direct in the member domain, and vice versa with some photo uploads.
Basically the purpose would be exactly what Roger is describing. The main site contains information about a non-profit organization. They would like to have an area for the members of the organization to discuss events and make connections. They want two very different experiences.
That is why I was inquiring about the WordPress Network/Multisite for this project.
Did this work well for you Roger? If so, I believe that this will be the approach I take for the project.
Thanks!
Yes, it works really well for this organisation – their build has been running for over two years now, and we add new features on a fairly continual basis.
There are some added twists that the shared user base lets us introduce – e.g. as well the main domain being the corporate home, we are able to offer personalised versions of the main site that the members can ‘present’ to their colleagues and connections.
Meanwhile, the member area (BuddyPress based) remains hidden away, and only visible to logged in members.
Great, that sounds perfect. Thanks a lot for the information. It’s definitely confirmed the direction that I’d like to take when approaching this project!
