3

We've done this before using categories and it's worked well for our client and for maintainability. We set it up all the domains to point to the same docroot (therefore the same EE installation). We then created a category group called "domains", and we make a category in there for each domain we're using. Then in our index.php we have this: <? switch (...


3

Multi Site Manager would work well for this. Each member group can be assigned to one or more sites in the network Super Admins can access all sites and settings. Content from other sites can be accessed by using the site parameter on any Channel Entries tag


3

The point is that sometimes you are limiting the weblog related to every template ( {exp:weblog:entries weblog="{master_weblog_name}" rdf="off"}), sometimes you aren't ({exp:weblog:entries limit="1" rdf="off" disable="pagination"}). Both your templates are loading entries from both weblogs. Add the weblogs parameter to all exp:weblog:entries variables and ...


2

Setting aside the debate of responsive vs dedicated mobile version (agreeing with Ian here), there was a good article back in the days on Erskine Design about building a separate version of your site without using MSM. That approach uses global variables to serve different templates to mobile users You could combine that approach with the RESS-ee plugin by ...


2

I have no idea! Kind of... If your RackSpace server functions essentially like a VPS or bare metal machine (just in the cloud), then you're all set! There are a couple way to go about it. I'll explain a couple of simple ways this works on a regular VPS or bare metal machine. You have your web root and an EE installation working on it. One way to go is ...


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


1

No, you should be fine. It will be a pain in the ass to manually manipulate the schema (using a GUI tool like MySQL Workbench) since you will be looking at a list of hundreds of tables, but there is no theoretical limit if your table engine is MyISAM. InnoDB has a theoretical limit of 4 billion tables. So you're fine. The only possible overhead would be if ...


1

Yes, it can be done. One way would be to turn on Save Templates as Files as in your Global Template Preferences, so your templates get saved to /system/expressionengine/templates/ and you can share between sites. You'll also need to update the Server path to site's templates accordingly. Or, even more simple, you could maintain one set of "master" templates ...


1

Perhaps you run out of number of available sites for your MSM license. Check that in your purchases section on EllisLab's site. Not sure though you'll be able to purchase more, as EE1 is not supported officially anymore.


1

So the answer to this was actually simpler than I thought. In index.php of the secondary site we set $base_path = $_SERVER['DOCUMENT_ROOT']; and then $assign_to_config['tmpl_file_basepath'] = $base_path . '/../../templates'; I also had to do the same thing with the path to snippets & Low Variables.


1

The answer is in understanding how MSM works. MSM doesn't really care what you call your sites, www.domain.com or something.domain.com so technically there are no "main" sites. If you look at a typical folder structure for an MSM setup you may have in the root folder: index.php (usually the site that EE is installed in, eg www.mysite.com) /site2/index....


1

This answer needs to be 30 characters long but the simple answer is "yes".


1

Not specifically answering the question, this is how I sometimes approach mobile development... Most of the site would just be regular templates with responsive design. For pages where a completely different mobile experience would be beneficial, ie. the checkout process, I would detect for mobile then serve a separate template. default_site/ | checkout....


1

I'm currently in a situation similar to yours. Most of my needs will be accomplished with just CSS media queries, but I found these articles of interest, while I was researching: http://www.netmagazine.com/tutorials/going-mobile-expressionengine http://www.johnfaulds.com.au/journal/responsive-layouts-with-expressionengine/


1

If you're creating a sub-domain for a mobile only site in addition to the main install then I can't see any other way than to buy MSM as they will be two different sites (refer to the EE licencing). However I'm not sure why you say a responsive website needs to be bland? There are plenty of responsive websites which work on mobile which are anything but ...


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