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/


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 ....


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

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

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 ...


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