Help - Search - Members - Calendar
Full Version: Multiple-domain Install Failes Static Files?
Movable Type Community Forum > Installing and Upgrading > Upgrading
Roelant
Hi,

I'm running a setup with multiple full qualified domain names. I used to manage all these blogs from my primairy domain, but since upgrading to movable type pro every site seems to be expecting an MT-install of it's own.

E.g., my primairy install is here

/www/root/domain1.net/mt4/ - using www.domain1.net

My secondairy blogs are here:

/www/root/domain2.com/ - using www.domain2.com
/www/root/domain3.org/ - using www.domain3.org

MT used to handle things fine, publish to respective siteroots and use full-path for items requiring the cgi-engine (e.g. trackback URL's allways started with the primairy domain, search was managed on the primairy domain, etc).

Since upgrading this goes wrong. Probably somewhere in MT something's changed to using relative paths, creating nonexistent URL's like and looking in paths like www.domain3.org/mt/mt-static for the stylesheet - wich isn't there.

Is this a setting, a template issue, of something else? I'd hate to have to copy MT to all three webroots but want to be able to keep usinga different FQN for every domain?
jimwalczak
QUOTE (Roelant @ Aug 19 2008, 01:49 PM) *
Hi,

I'm running a setup with multiple full qualified domain names. I used to manage all these blogs from my primairy domain, but since upgrading to movable type pro every site seems to be expecting an MT-install of it's own.

E.g., my primairy install is here

/www/root/domain1.net/mt4/ - using www.domain1.net

My secondairy blogs are here:

/www/root/domain2.com/ - using www.domain2.com
/www/root/domain3.org/ - using www.domain3.org

MT used to handle things fine, publish to respective siteroots and use full-path for items requiring the cgi-engine (e.g. trackback URL's allways started with the primairy domain, search was managed on the primairy domain, etc).

Since upgrading this goes wrong. Probably somewhere in MT something's changed to using relative paths, creating nonexistent URL's like and looking in paths like www.domain3.org/mt/mt-static for the stylesheet - wich isn't there.

Is this a setting, a template issue, of something else? I'd hate to have to copy MT to all three webroots but want to be able to keep usinga different FQN for every domain?


I had something like that with subdomains. I seemed to recall I set up the config file with mt:admincgi (or something like that) where admincgi pointed to the install with the entire URL (http://mydomain.com/path/to/cgi/).

Then you need to change it in a few places - or at least the header where it looks for path/to/cgi/ and replace it with mt:admincgi (or something like that).

Hope that at least points you in the right direction
Roelant
Hmm, indeed. I allready noticed this part of the configuration file:

CODE
#======== REQUIRED SETTINGS ==========

CGIPath        /mt4/
StaticWebPath  /mt4/mt-static/


But thought those where supposed to be internal paths (and couldn't find documentation confirming that). Just tried adjusting it to full URL's and it it indeed did the trick! Thanks. wink.gif
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2009 Invision Power Services, Inc.