StaticWebPath
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.
Warning: If using
AdminCGIPathto specify a different url or protocol for accessing admin scripts, the value forStaticWebPathmust be a relative url to allow JavaScript to execute with same origin access for bothAdminCGIPathandCGIPathURLs.
Value ¶
Full or relative URL. Required if mt-static files are moved outside MT directory.
Examples ¶
Full URL:
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
Niall Kennedy
November 25, 2007 5:02 PM | Reply
StaticWebPath should be set to the same protocol and domain as your weblog's admin interface to allow JavaScript to execute with same origin access inside your pages.
Maarten Schenk
December 19, 2007 5:08 AM | Reply
To elaborate on what can happen if you don't follow Niall's advice: the Edit Entry screen breaks and you will not be able to click in the text editor field nor will old entries load into it. So keep it on the same domain :-)