6

Yes. Copy the index.php from the main site and update the system path variable, and the following $assign_to_config['template_group'] = 'your-template-group'; $assign_to_config['template'] = 'your-template'; $assign_to_config['site_index'] = 'http://blog.yoursite.com/';


5

Looks like you need Multiple Site Manager. But, if all your subdomains are part of the same website, there's a technique I use on multiple language websites that can help you. You have two possible setups. On the first one, your directories need to follow this structure: /system /domain.com /domain.com/images /domain.com/themes /domain.com/index.php /...


5

This is doable with EE (assuming you get thumbs up on the legal licence side of things). You'll need to set up your domain so all (or most) subdomains resolve to a single location. You'll also need to configure apache to listen for traffic for all subdomains for your main domain. Check out the following articles for details in performing this step: http:/...


5

You should probably check that your intended use is permitted under the EE license: Restrictions Unless you have been granted prior, written consent from EllisLab, Inc., you may not: Use the Software as the basis of a hosted blogging service, or to provide hosting services to others. Reproduce, distribute, or transfer the Software, ...


5

It seems like you can set a "cookie_domain" variable to the config.php. Just figured this out by having a quick look at expressionengine/core/EE_Config.php around line 277. For cross sub domains persisting cookie, I believe your domain should be one of the seven special ones (http://wp.netscape.com/newsref/std/cookie_spec.html). In short $config['...


5

Another option is having a faux subdomain mapped to a template group in the existing site via .htaccess. For example: RewriteCond %{HTTP_HOST} ^blog.mysite.com [NC] #whatever exclusions you need for index rewrite: RewriteCond $1 !^(images|themes|assets|media\/|index\.php|([a-z0-9-]+).html) [NC] RewriteRule ^(.*)$ /index.php/blog/$1 [L] This would need to ...


4

Another option is to serve all the domains out of the same set of files. This will point the primary and subdomain at the same file set. Then all you have to do is just check the $_SERVER['SERVER_NAME'] and set the config variables based on the different subdomains. Its how I setup a mobile site in EE. Only one set of files, but I just changed a few vars (...


3

The old method of running multiple sites still works as of the latest EE 2 release. To use that, you need an index.php for each site and you'd use the assign_to_config values for anything site-specific. For example, I have this setup for one of my subsites (it runs in a subfolder rather than a subdomain, but principle should be the same I believe): $...


3

You need to enable multi-site login via the config.php file. You add a statement like: $config['multi_login_sites'] = "http://domain.org/|http://domain2.org/"; for each site/domain that they are logging into. Now the downside of this, is if you are logging them into a number of sites, the user will see a series of login flashes, from the EE successful ...


2

I understand your thinking but I can't see it working. As Travis says, the parent entries (for example /about) there's no way you could create a subfolder on the server of /about - as soon as you do that, it'll take precedence. As for the htaccess route, the browser will try route it to an actual subdomain and would fail if not found.


2

These instructions lay out in brief the considerations for setting up a subdomain site in the form available at EngineHosting, where all domain accesses go to the main domain public_html. On other hosts which use DNS to assign subdomains, you won't need the additions to the main domain .htaccess. The EE install, where you have CP themes, etc., is at the ...


2

<IfModule mod_rewrite.c> RewriteEngine On RewriteCond %{REQUEST_URI} !(calculator) [NC] RewriteCond $1 !\.(gif|jpe?g|png)$ [NC] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule ^(.*)$ /index.php/$1 [L] </IfModule> Explainations... RewriteCond %{REQUEST_URI} !calculator/ I think the problem here is that you'...


2

Well, both things are fine in the terms of MSM. You can create sub-domain as well as sub-directory also. Just you need to take care is, about path settings at the time of setting MSM website. And if you want to make SEO friendly then, yes sub-directory is the best option.


2

I've done both. The only thing you'll have to consider it making sure your cookie domains are set correctly, depending on if it's a site2.domain.com or domain.com/site2. Otherwise, the MSM sites will function exactly the same. Past that, at most you have the regular head aches that could come from migrating a site, including getting .htaccess rules set ...


2

This could be handled via .htaccess rules, as long as your sub-domain records point at your EE server. Here is an example: RewriteCond %{HTTP_HOST} ^sub.domain-1.com [NC] RewriteRule ^(.*)$ http://domain.com/post1 [L] I'm not .htaccess expert so you may need to play around a little, but that'll do it. You should place these rules in your web roots ....


2

I think it's probably doable. It may be a process of elimination to work out all the kinks as you go, but no core hack should be needed. I'd suggest you move the system directory out of the main site's document root first. You can remove admin.php from the main site. And copy it over to the admin subdomain. And you can rename it whatever you like. You'll ...


2

You just need to create subfolder msm-site-two and put inside index.php with $assign_to_config['site_name'] = 'msm-site-two'; $assign_to_config['site_url'] = 'http://000.000.000.000/msm-site-two/'; and your second site will be available by url 000.000.000.000/msm-site-two/


1

This was due to an error being triggered from the frame being used on NSM Live Look and permission settings. When I disabled the NSM Live Look add-on, everything worked smoothly. I am trying to resolve this issue further by seeing if there is something I can do with the NSM Live Look scripts, but I haven't received any responses from the developer yet.


1

You need to provide more information as to what you need, also ?do=index is not ExpressionEngine, so what are you doing to get that? Multi-language using the method you state has been documented and asked many times. Top questions: Multi Languages simple multi language site (two languages, mostly static content) View all related questions: https://...


1

Not that I'm an expert, but what I've implemented in the past has been in .htaccess, not defining privacy settings in EE, until now I've not given it much thought... This answer gives some light - what you've done is set it so cookies aren't sent back from that domain for the content generated by EE, but they will still be sent in the request, therefore ...


1

What we usually do is add a folder ee/ to the root and install everything there. The base url will then be http://yoururl.com/ee/ and ExpressionEngine will install everything accordingly and will ignore the subdirectory in segments. When you go live (switch to the root directory) you will have to update the urls in General Configuration as well as any urls ...


1

In that case you just need to change the last line of the standard .htaccess rules. (That link is worth reading in its entirety.) <IfModule mod_rewrite.c> RewriteEngine On RewriteBase / # Removes index.php from ExpressionEngine URLs RewriteCond %{THE_REQUEST} ^GET.*index\.php [NC] RewriteCond %{REQUEST_URI} !/...


1

A) What is the validity to this request I don't think having a subdomain for blog is better for SEO. Rather than, I always prefer to have SEO friendly URLs for the blogs like yoursiteurl.com/title-of-your-blog which can easily achieved by Pages module. B) Would I have to use MSM in order for this to be managed all from the same admin? Yes, you have to ...


1

I ran into the same issue. Even though I was using the same primary domain, the subdomains were causing cross domain issues with what seemed to be the CK Editor functionality due to permissions. I found out later that the issue was due to, in my case, NSM Live Look using iframes. Since the iframe was still technically being viewed even thought the tab was ...


1

Sandwich, I'm no expert here either, but looked over your problem to see if I could learn something. Here's what I could suggest. I think the basis is that cookie domain setting in EE is for the purpose of defining what domain sent cookies will be assigned to - but it isn't about whether to send cookies. Sending cookies is presumed. I thought of working ...


1

Your current .htaccess file indicates that any files or directories actually found on the server will be served as-is. So if you throw some static files (or even another application) in a folder called /foo, it should load without that request being redirected through EE's controller. These lines: RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{...


1

htaccess can be directory specific so I'd be inclined to add a separate htaccess file for that directory and have RewriteEngine off


Only top voted, non community-wiki answers of a minimum length are eligible