Forgive me if this question has been asked before, but I couldn't find an answer that applies my specific situation.
Last month, I successfully installed MT 4.x to my domain.
The other day, I purchased a second domain, which is hosted by the same company.
The file structure for the first domain goes like this:
/home/user/public_html/
/home/user/public_html/cgi-bin
The file structure for the second domain goes like this:
/home/user/public_html/domain2
/home/user/public_html/domain2/cgi-bin
So my MT installation has its static files in the first domain's public_html folder and the rest of the files in the first domain's cgi-bin folder.
I want to use that same installation to publish to the second domain.
Currently, I am able to publish barebones text to the second domain, but with no styles. i tried linking the second domain's template to:
/home/user/public_html/mt-static/themes/customtheme/custom.css
custom.css is the same style sheet powering domain1, but it's not working with domain2 when I try it that way. I suppose I could create a duplicate themes folder within the domain2 folder, but I suspect there must be an easier way.
My questions are:
1). What must I do to run both domains from the same MT installation?
2). Is it a good idea to run both domains from the same MT installation?
3). What must I do to get styles/templates from said MT installation to apply to domain2?
Thanks,
Tim
Reported on Movable Type 4.2
in your mt-config.cgi either add or modily the line:
StaticWebPath
to include the url of domain 1, so instead of reading:
StaticWebPath /mt/mt-static
it reads:
StaticWebPath http://www.domain1.com/mt/mt-static
When I changed my StaticWebPath on the cgi file it messed some things up. Instead, I simply use the FULL PATH in my Stylesheet (where it uses the MT code for the mtstaticpath I remove it and enter the full path to the stylesheet that goes with the template).
The only thing you have to do is find out where it actually is and change it. If you are using StyleCatcher it will put the stylesheet into the Support folder instead of the Themes folder (no clue as to why it works that way).
So your path would be:
http://domainname.com/cgi-bin/mt-static/support/themes/theme-folder/theme-stylesheet.css
This is also helpful if you plan to make your own layouts and stylesheets. If you plan to work from the stylesheets that come with the styles it's recommended to copy and paste the blog.css from the themes-base folder into the theme folder so that you don't mess up other blogs.
each domain must its own mt-static stored it its own folder. and they be on the same ip address.
just create a new blog at the system menu, no need to upload another mt installation. tried this with 10 domain in one mt installation.
I am trying to get the same thing done. In the marketing collateral of MT 4.2x, it is clearly claimed that multiple domains can be run from the same MT installation.
Well, is this possible or not? If so, where are the official instructions? For a "seasoned blog platform" to have a commenting system that often throws silly errors, it's worth wondering if something more sophisticated such as the social network will work.
Although entirely untested, my current understanding is that you should be able to get away with one MT_HOME and multiple MT_CONFIGs, aliasing the one mt_static to a path in each of your blogs, and one distinct publishing path for each blog. But sticking with a "one blog per MTOS installation" setup is probably a fail-safe move...