I think you cover this in all the literature, but I just need to double check…

If I have a current install/license already at EngineHosting and I want to add a second, totally separate weblog - I can use MSM instead of buying another license and separate hosting install. Correct?

Hi, andculture - as long as you own both Sites, then yes, you could use the Multiple Site Manager.  If all you want is a second weblog, that may not be needed.  It depends on your particular project.

Lisa Wess - 07 May 2008 01:35 PM

Hi, andculture - as long as you own both Sites, then yes, you could use the Multiple Site Manager.  If all you want is a second weblog, that may not be needed.  It depends on your particular project.

Lisa, well it’s more then just another weblog. It’s a completely different weblog for a different entity that we own, with its own content, user registration base, and editor. Could we execute this using a single install?

With the Multiple Site Manager, membership is installation-wide.  You can set permissions, and even the member-list, per site and per group; however the member accounts will work on all Sites.  If you need a fully separate user-base, then two installations (and therefore licenses) would be more appropriate.

The MSM is intended for related internet properties, that share a membership base, and share the same owner.  It’s also important to bear in mind that there is no way to split a site out of the MSM, so if you did eventually want to separate these sites, starting separate is best.

Make sense?

Yeah. That answers my question. Thanks.

Lisa Wess - 07 May 2008 01:44 PM

The MSM is intended for related internet properties, that share a membership base, and share the same owner.  It’s also important to bear in mind that there is no way to split a site out of the MSM, so if you did eventually want to separate these sites, starting separate is best.

I’m in the planning phase of a local network of sites.  EE is absolutely at the top of my list for many reasons, especially MSM and our need to maintain a single member base across all sites. One of my top concerns however is the possibly of selling or spinning off one or more sites in the future.

If I have Server-A with five sites (#1, #2, etc) in MSM and I want to move site #1 to Server-B with the full member base, can I….
- duplicate the database from Server-A to Server-B with a new installation,
- delete the four unwanted sites from Server-B
- delete site #1 from Server-A
and end up with both having full user base intact?

Hi Iomondmedia,

Something along those lines should work just fine. Depending on how interrelated the sites were you might have to do some clean up. For example, if you were sharing templates or posting weblogs cross-site you’d have to be careful about moving some things manually.  But as an approach it would be a good start.

I’d just like to add a technical note to the thread.  While there is no “master” Site in the MSM - The “first” Site can not be removed.  It can be renamed, and you can delete everything inside of it - but it will remain there unless you do some direct database manipulation (changing Site IDs, essentially).  So, if you know a Site may get spun off - don’t make it the first site.  Make the first site one that you’ll continue to keep there. =)