I'm doing a large redesign on an OLD EE1 site. It was built in a way that doesn't make sense to try converting. It is also going to a subdomain flow. Originally I was going to just keep all of the subdomain segments as separate sites since it is operating under the DEV -> QA -> PROD server flow and will be released live in waves. However, I don't want to rely on a third party search engine to crawl the site and return data. I also have needs for the native search in EE.

What is the best way of expanding a site to include new subdomains as they are developed while keeping them from being visible during development? I know I could keep the subdomain/msm site turned off while everything is being worked on and then turn it on when it is ready to go live, but this doesn't allow for the requested flow mentioned above with DEV -> QA -> PROD. To my knowledge there isn't any way to properly import a new site into an msm build. (Anyone?) If so, I could keep them separate and then import it when ready. This would at least allow me to fulfill the flow request.

Does anyone else have any nuggets of hope they could provide from doing anything similar?

1 Answer 1


You could use template permissions to redirect users to where they can't see the page if they do not belong to the correct member group. Design > Template Manager then select template and edit preferences - see screenshot.

Once there disable access to all but the super admin group and another group if necessary. Now no one can see that template. Select the redirect template that you want non-logged in members to view.

Here you could either set up a splash page, i.e. coming soon, or put in a {redirect="http://domain2.com"} and send them to a completely different site.

Now you can view the site while it's being built, but no one else can.

As for importing a new site into an MSM build it's not possible unless you copy existing templates/preferences when initially creating a new site.

Hope this helps.

enter image description here

  • Sean,Thanks. I like that solution. I didn't think about that. I think that will help accomplish this. Quick question though... I know about importing templates, etc., but that can only be done on an existing site in that MSM build right? This wouldn't help me if the site was a stand-alone site in another build right?
    – W3bGuy
    Jul 11, 2013 at 17:29
  • Brian - you are correct. Can only work with existing site. However if you save your templates as file and place them in the templates directory for site2 they should be auto picked up by the CP. You'll still have to create channels and custom fields though.
    – CreateSean
    Jul 11, 2013 at 17:37
  • That's what I've always done in the past. Just wanted to make sure I wasn't missing out on the party... ;)
    – W3bGuy
    Jul 11, 2013 at 17:41

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.