StaticWebPath

This is documentation about a configuration directive, which can be placed within Movable Type’s core configuration file, mt-config.cgi, to customize the behavior of the system.

URL to the mt-static directory.

StaticWebPath http://www.example.com/path/to/mt-static

Required when moving the mt-static directory from the mt application directory.

If MT files are placed in a CGI executable directory which doesn’t serve non-executable files (as often the case with cgi-bin directories), the mt-static directory will need to be moved to a location. Usually the mt-static directory is moved to the web root or aliased to the web root via symlink or apache alias.

Note that the StaticWebPath should not point to your blog, and Movable Type should not be installed in the same location you want your blog to appear. For organization and clean functionality, Movable Type should be installed in its own folder; your blog can be set up anywhere outside of this folder.

Warning: If using AdminCGIPath to specify a different url or protocol for accessing admin scripts, the value for StaticWebPath must be a relative url to allow JavaScript to execute with same origin access for both AdminCGIPath and CGIPath URLs.

Value

Full or relative URL. Required if mt-static files are moved outside MT directory.

Examples

When specifying a full URL the protocol and domain must be the same as used for CGIPath.

StaticWebPath http://www.example.com/path/to/mt-static

Relative URL (use this when using AdminCGIPath with a different protocol and/or when aliasing to a different sub/domain):

StaticWebPath /path/to/mt-static

Related

• CGIPath
• AdminCGIPath