The mt-static folder
This is an archived entry from the Movable Type 3.2 beta test.
Entries from the current beta release (v3.3) can be found here.
One new change in 3.2 is that the static files are now housed in their own folder, named (appropriately) "mt-static".
When upgrading, you'll want to remove the old versions of the files from their original locations, and upload this new folder instead. Not having the static files in the right place where Movable Type can find them can cause a variety of user interface issues (that could be mistaken for bugs), so please double-check your setup today to ensure that they're properly situated on your server.
If you already have a "static" folder where you originally put images, stylesheets, Javascript, etc., upload all the files from the "mt-static" directory into that folder. Double check your mt.cfg file's "StaticWebPath" location to make sure it's pointing to the folder that contains these new files. (If you take a look at the latest mt.cfg file, you'll see we now recommend using a fully qualified URL for this setting, though it isn't required.)
If you don't have a special "static" folder, you can just upload the entire "mt-static" folder to the same location as the other Movable Type files. Just make sure you don't have a "StaticWebPath" declared in your mt.cfg file.
And remember - when using FTP to transfer the files, images should be uploaded in BINARY mode, and all the other files in ASCII.
Posted on July 14, 2005 5:37 PM in Features
Comments
Including the static files in their own folder is incredibly helpful!
I've used a folder called mt-static on my host for years now, and it was always frustrating to have to remember to split the static from the dynamic files when upgrading.
Thanks 6A!
Posted by: quack![[TypeKey Profile Page]](http://www.sixapart.com/movabletype/beta/nav-commenters.gif)
|
July 15, 2005 12:54 PM