Ask the Readers: Multiple Site Manager
The Latest EE Podcast about Multiple Site Manager got me thinking that MSM would make a great topic for an “Ask the Readers” feature. I remember when EllisLab debuted MSM and it kind of blew my mind. What a wild idea, being able to run lots of websites from the same installation. What a dream! Over time, though, I have only had the opportunity to use it once or twice.
My questions to you the reader: Do you use Multiple Site Manager? How is it working out for you? Anything in particular EllisLab could do to make it better?
Share your thoughts in the comments.
Posted on Nov 03, 2010 by Brian Warren
Share on Twitter
Thomas Sausen — 09:27 on 11.03.2010
MSM was one of my top 3 selling points. I’m using EE since for about 1,5 years now. Because I’m a designer and not a php guru, I like EllisLabs’ concept. But I’m a guy who always had multiple sites and EE simply costs a lot of money. I didn’t want to pay for every of my projects a licence, so MSM was a great - and money-saving -choice. I’m going use it for a new client-project, too.
Unfortunately my MSM didn’t work since EE2.1.1. I’m not able to switch my sites. Hopefully EllisLab will fix it soon, because I want config and edit my sites.
I’m gonna use MSM for 3-4 sites this year:
1. My blog/portfolio
2. My english blog/portfolio
3. MY webcomic
4. eembed, something like a german EEinsider
Michael C. — 09:27 on 11.03.2010
MSM is awesome indeed, especially the ability to pull templates and data from any site into any site.
A few wishes I have (based on using EE 1.x, not 2.x):
1) Sometimes while actively developing a site, I add a tab that goes directly to the primary CSS template. If it’s an MSM install, however, it only works for that specific site, despite the tab showing up across all sites. Wish there was a way to define individual tabs to only show on specific sites.
2) I don’t know how complicated this will actually end up being, but right now I fear the day when the time comes for an MSM site to graduate, and I have to split it off into its own separate EE install. I figure the easiest way will probably be duplicating the entire EE install and then pruning out the unneeded sites, but there’s a whole bunch of complications to go along with that (shared data/templates, problems with MSM’s site license code being temporarily used in 2 installs, etc).
3)
Michael C. — 09:28 on 11.03.2010
...there is no #3. :p
Steven Hambleton — 09:53 on 11.03.2010
When pulling in entries from another site, being able to automatically build the correct URL.
Mason Kessinger — 09:58 on 11.03.2010
We too have only had a few chances to use MSM but we’ve had no complaints on the client end. They’re thrilled with their EE setup.
http://www.genderhealth.org/
http://www.pepfarwatch.org/
http://www.preventionnow.net/
It was a breeze to setup and very logical to maintain for the client.
Michael C. — 10:11 on 11.03.2010
@Steven Hambleton: If you go to Admin > Weblog Administration > Weblog Management > Edit Weblog Preferences > Path Settings, you can fill out the Comment Page URL (use something like http://www.example.com/blog/post/ - whatever the URL is to your single-entry page) and then reference that as {comment_url_title_auto_path} inside the {exp:weblog:entries} tags (not {path=”{comment_url_title_auto_path}”}, just plain <a href=”{comment_url_title_auto_path}”>{title}</a>.
(Fingers crossed that the code above comes out readable and visible…)
Steven Hambleton — 10:14 on 11.03.2010
@Michael - My last MSM site was a while ago so I’ll have to go back and give that a go. Thanks
Nevsie — 12:15 on 11.03.2010
MSM Corporate? one install to run multiple sites for different clients. Separating out members, etc.
But MSM is still buggy, and needs to be re-polished and tested heavily for each update before release.
Simon — 20:49 on 11.03.2010
I’m a maths teacher, I’ve set up a network of maths sites and love the ability to pull data in from each site, have membership across the sites and login to one control panel to manage all sites:
http://mathsclass.net
http://mathskit.net
http://mathslinks.net
Jacob — 15:18 on 11.04.2010
Have used it, not a fan. Too many ways to bring the whole network of sites down with one mistake/error/bug. Now avoid it almost entirely.
Paula — 18:20 on 11.04.2010
@Jacob am curious what kinds of experiences you’ve had where something would bring down all the sites.
Bud Parr — 20:03 on 11.04.2010
I’ve built at least 10 EE sites in an MSM context, both in 1.x and 2.x and sometimes in weird and complicated settings. I’ve had no problems with it in either version.
Steven Hambleton — 20:10 on 11.04.2010
The ability to split off sites or even import them would be handy.
Also the ability to have a global *and* individual site membership list.
Sean Smith — 21:30 on 11.04.2010
I’m using it on a personal family site. One thing that MSM seriously needs is the ability to export a single site to a new installation of EE. I’ve got my family site and my daughters blog running on MSM - eventually my daughter will want to move her domain, blog, photos, entries and other content to a separate installation. Not so important now, but once she’s older and moves on…
Bud Parr — 21:40 on 11.04.2010
I’d add the export function too, but I ‘think’ that would be a pretty complicated endeavor.
One option would be to export the content only and import it into a new site using one of the available plugins. Another would be to copy the entire site to a new server, and delete the other sites from the new server. Would love to hear how anyone else has handled this.
Chip Lay — 13:47 on 11.06.2010
It would be really nice to have a separate set of control panel menu tabs for each site (MSM Tab Manager). As we use some modules on some sites and not on others.