Movable Type Documentation

Back to docs index

Chapter D: Configuration Directives

In this section:


This configuration directive specifies the maximum number of recent items in any activity feed.

Default: 50

This configuration directive specifies the name of the script used to pull activity feeds.

Default: mt-feeds.cgi

This configuration directive specifies whether activity feed requests should trigger the scheduled tasks framework. The default is enabled (1). To disable this trigger, add this to your configuration file:

ActivityFeedsRunTasks 0

This will revert back to the legacy behavior where the scheduled task framework is only triggered through use of run-periodic-tasks.

Note: Regardless of the use of the above methods of scheduled task framework execution, the junk feedback expiration task is always executed when junk feedback is received.

The AdminCGIPath configuration directive is the administrative analog to the CGIPath directive and allows for a distinct URL path to be used for access to the administrative interface and scripts (e.g. mt.cgi).

Its use is optional since the CGIPath setting is used in its absence. However, for added security, Six Apart recommends use of this directive in combination with SSL (via https) in order to provide encryption/authentication of all administrative requests.

The value of this setting can be included in a template via the MTAdminCGIPath template tag.

Examples

In your mt-config.cgi, the following (without AdminCGIPath) would be used for all links to Movable Type scripts, public or private:

CGIPath http://www.example.com/path/to/mt/

The following, in addition to the CGIPath setting above, would preferentially use the admin subdomain of example.com for accessing the administrative scripts. All public scripts would still use the CGIPath setting.

AdminCGIPath http://admin.example.com/path/to/mt/

The following, in addition to the CGIPath setting above, would use HTTP protocol for the public interface scripts and HTTPS for the administrative scripts. You would, of course, need to enable SSL on your server before this will work.

AdminCGIPath https://www.example.com/path/to/mt/

In this case, you will also need to set your StaticWebPath to a relative value in order to avoid insecure content browser warnings. For example, instead of:

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

You can use:

StaticWebPath /path/to/mt-static/

Or even:

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

Related

By default, the script that Movable Type uses for the administrative interface is called mt.cgi. In some situations--for example, if you are running MT under mod_perl, or if your server requires that your Perl scripts have the extension .pl--you may need different names for these scripts. You can set the names that will be used throughout the default templates and Movable Type code by changing these values.

Default value: mt.cgi

Example:

AdminScript mt.pl

See also:

Default is 1. System-wide comment control switch. MT controls this through the mt_config table.

Default is 1. System-wide TrackBack ping control switch. MT controls this through the mt_config table.

If you have multiple weblogs, or if you provide several different versions of your site, you may wish to use alternate templates to provide different versions of your search results, as well. See Alternate Templates in the manual for more details. You can define as many alternate templates as you want.

By default, the following alternate template is set up:

    AltTemplate comments comments.tmpl

This sets up the alternate template for the "new comment search."

Example:

    AltTemplate work work.tmpl

This configuration directive specifies to use the alternate search template which is responsible for feed format and content.

The path to a directory where application override templates are found. For more information about override templates, and how template searching is done in general, see How does build_page find a template? in the MT::App documentation. Example:

    AltTemplatePath  /home/ezra/mt-overrides/tmpl

By default, the script that Movable Type uses for Atom is called mt-atom.cgi. In some situations--for example, if you are running MT under mod_perl, or if your server requires that your Perl scripts have the extension .pl--you may need different names for these scripts. You can set the names that will be used throughout the default templates and Movable Type code by changing these values.

Default value: mt-atom.cgi

Example:

AtomScript mt-atom.pl

See also:

The AuthLDAPBindDN configuration setting is an optional DN used to bind to the LDAP directory when searching for a user.

Default value: not defined

Note: If unspecified, MT will attempt to do an anonymous bind for LDAP lookups.

This directive is used for setting the password of the LDAP DN used in AuthLDAPBindDN.

Default value: not defined

The name of SASL Mechanism to use for both binding and authentication.

Values:

  • PLAIN (Default value)
  • DIGEST-MD5

Note: Using anything other than "PLAIN" for AuthLDAPSASLMechanism requires the Perl Authen::SASL package to be installed.

For more information, see http://www.melnikov.ca/mel/devel/SASL_info.html.

This configuration directive specifies the URL to access for LDAP authentication.

Default value: none

For possible values please see:

This configuration directive is only available in Movable Type Enterprise.

This configuration directive specifies the authentication type that will be used for user logins. The default, MT, indicates that Movable Type Enterprise's author database is authoritative. The alternate option, LDAP, specifies that an LDAP directory will be used as the authoritative authentication source.

If LDAP is specified, the following configuration directives are also relevant and in some cases required:

The URL used to send the XML-RPC blo.gs ping.

Default value: http://ping.blo.gs/

Example:

    BlogsPingURL http://some.alternate.blo.gs.server/path/

When uploading files through Movable Type's upload mechanism, a ceiling is put on the size of the files that can be uploaded, to prevent denial-of-service attacks.

Default value: 1000000 (1MB)

Example:

    CGIMaxUpload 500000

The CGIPath configuration directive is a required setting which defines the URL path to your Movable Type directory and is used in the construction of links to any of the various scripts which handle the system's public interfaces (e.g. comments, TrackBacks, search, etc).

This value can be output through your templates using the MTCGIPath template tag. You will see it used in the default templates in the comment and search forms, the RSD index template and others. The system also uses it internally in a number of ways.

Example

If you normally access Movable Type with the following URL:

http://www.example.com/cgi-bin/mt/mt.cgi

Then you would put this in your mt-config.cgi:

CGIPath http://www.example.com/cgi-bin/mt/

IMPORTANT:

For added security, Six Apart recommends the use of the AdminCGIPath configuration directive for defining the URL prefix to Movable Type's administrative scripts such as mt.cgi.

This value supplies the path to your CSS file, if it's in a different place from your other static files.

The following settings specify the defaults for searches on your site; they can be overridden either through hidden form inputs, or in form inputs set by your users. You should probably leave these settings at the defaults and allow your users to override them. RegexSearch is a regular-expression search, and CaseSearch is a case-sensitive search.

Default value: 0 for each setting

Examples:

    RegexSearch 1
    CaseSearch 1

By default, the script that Movable Type uses for comments is called mt-comments.cgi. In some situations--for example, if you are running MT under mod_perl, or if your server requires that your Perl scripts have the extension .pl--you may need different names for these scripts. You can set the names that will be used throughout the default templates and Movable Type code by changing these values.

Default value: mt-comments.cgi

Example:

CommentScript mt-comments.pl

See also:

The default number of days to search on a regular search (SearchCutoff) or on a new comment search (CommentSearchCutoff).

The default for SearchCutoff is to search from the beginning of your weblog (all of your entries), and the default for CommentSearchCutoff is the last month of comments.

Examples:

    SearchCutoff 7
    CommentSearchCutoff 7

The number of seconds until a registered commenter's session will expire. Defaults to 1 hour.

Specifies the exact domain for which MT cookies are set.

Specifies the exact path for which MT cookies are set.

The ObjectDriver, Database, DBUser, DBPassword, DBHost, DBSocket and DBPort directives tell Movable Type where to find its database. For instructions on how to configure Movable Type for your database environment, see Installing Movable Type.

The ObjectDriver, Database, DBUser, DBPassword, DBHost, DBSocket and DBPort directives tell Movable Type where to find its database. For instructions on how to configure Movable Type for your database environment, see Installing Movable Type.

The ObjectDriver, Database, DBUser, DBPassword, DBHost, DBSocket and DBPort directives tell Movable Type where to find its database. For instructions on how to configure Movable Type for your database environment, see Installing Movable Type.

The ObjectDriver, Database, DBUser, DBPassword, DBHost, DBSocket and DBPort directives tell Movable Type where to find its database. For instructions on how to configure Movable Type for your database environment, see Installing Movable Type.

When creating files and directories, Movable Type uses umask settings to control the permissions set on the files. If you are running under cgiwrap or suexec, you should use a value of 0022 for all of these settings.

Default values: 0111 (DBUmask, HTMLUmask, UploadUmask), 0000 (DirUmask)

Example:

    DBUmask 0022

The ObjectDriver, Database, DBUser, DBPassword, DBHost, DBSocket and DBPort directives tell Movable Type where to find its database. For instructions on how to configure Movable Type for your database environment, see Installing Movable Type.

The filesystem path to the db directory, where your MT database files are stored, if you're using the Berkeley DB data storage option.

Default value: ./db

Example:

    DataSource ./db

The ObjectDriver, Database, DBUser, DBPassword, DBHost, DBSocket and DBPort directives tell Movable Type where to find its database. For instructions on how to configure Movable Type for your database environment, see Installing Movable Type.

When this value is set to an email address, MT will send all outgoing mail to this address instead of the usual recipient.

If you're developing applications that use MT's mailer (MT::Mail) then you might find this option a useful alternative to the MailTransfer debug option while debugging.

The DebugMode option controls whether MT displays or suppresses messages that are useful for debugging purposes. By default, this option is set to 0, or disabled. Set to 1 to prevent the suppression of these messages.

This configuration directive specifies the initial values for the blog's entry screen display options setting at the time of creation. The options for this directive are as follows:

Button: The position of the action bar relative to the listing table.

Values:

  • Below - Below the listing table (Default value).
  • Above - Above the listing table.
  • Both - Both above and below the listing table.

Type: The type of entry screen to display

Values:

  • Basic - Title, status, date and body (Default value).
  • All - All possible fields.
  • Custom - A custom combination of fields.

In addition, if the Type is set to Custom[1], the following keys are also configurable and take values of 1 or 0 (the default):

  • Category
  • ExtendedEntry
  • Excerpt
  • Keywords
  • Tags
  • TextFormatting
  • AllowComments
  • AllowTrackBacks
  • Date
  • Basename
  • TrackBackURLs

In each case except for Date[2] the setting controls whether the corresponding field on the entry editing screen is displayed or suppressed.

[1] - If Type is not Custom, the settings are simply ignored.

[2] - The Date field is always displayed on the entry editing screen, so the setting instead controls whether the date is editable or not.

DefaultEntryPrefs Example

The following specifies a blog default setting for displaying all fields:

DefaultEntryPrefs Type=All

The following sets the Basic setting as the blog's default. The second option is ignored.

DefaultEntryPrefs Type=Basic

DefaultEntryPrefs AllowComments=1

The following sets the default for new blogs to display the Excerpt and Keywords fields in addition to the ones already provided by the Basic setting (Title, status, date and body):

DefaultEntryPrefs Type=Custom

DefaultEntryPrefs Excerpt=1

DefaultEntryPrefs Keywords=1

Specifying only the following (with no additional fields) would set the default for new weblog to "Custom" but without any additional fields checked:

DefaultEntryPrefs Type=Custom

Note: Custom with no extra fields checked is equivalent to Basic on the entry editing screen.

Determines the language which will apply to the Movable Type interface when no user is logged in.

The value should be the name of a "localization module" installed on your server. Localization modules should be placed in the directory lib/MT/L10N/ within the Movable Type directory. For more information on how to get a localization module for your language, see http://www.sixapart.com/movabletype/ and http://www.movabletype.org/l10n/

When a user is logged in to Movable Type, the interface will be presented in the language specified by the user's profile settings.

Default value: en_us

This configuration directive specifies the initial values for the blog's listing screen display options setting at the time of creation. The options for this directive are listed below with descriptions, their default and possible values. The options only apply to those listing screens which contain the option in their display settings.

Rows: The maximum number of table rows that are displayed per page.

Values:

  • An integer larger than 0 - Number of rows to display (Default 20)
  • none - No limit. Show all rows.

Format: The format or view which is used to display the listing.

Values:

  • Compact - A single row is used for the display of item metadata (Default Value)
  • Expanded - Multiple rows are used, the first containing the item metadata and the second containing the item's primary content

SortOrder: Order of items displayed in the listing table. This is always used solely in conjunction with the sort by option.

Values:

  • Ascend (Default Value)
  • Descend

Button: The position of the action bar relative to the listing table.

Values:

  • Below - Below the listing table.
  • Above - Above the listing table. Default Value.
  • Both - Both above and below the listing table.

DateFormat: The date format used in the listing table.

Values:

  • Relative The date and time relative to now like "6 days, 8 hours ago". After one week, this reverts to a full date. Default Value.
  • Full - A full date like "2006.04.05"".

DefaultListPrefs Example

DefaultListPrefs Rows=none

DefaultListPrefs Format=Expanded

This configuration directive specifies to restrict the blog publishing paths to the DefaultSiteRoot.

The specified settings are used on the "Create new weblog" screen as the initial suggested values for the Site Root options.

A trailing slash and the string WEBLOG-NAME is appended to indicate which part should be edited to specify the desired publishing location for the blog being created.

If DefaultSiteRoot is not specified in the mt-config.cgi, the system attempts to guess the correct values as in previous versions.

This configuration directive specifies to restrict the blog publishing paths to the DefaultSiteURL.

The specified settings are used on the "Create new weblog" screen as the initial suggested values for the Site URL options.

A trailing slash and the string WEBLOG-NAME is appended to indicate which part should be edited to specify the desired publishing location for the blog being created.

If DefaultSiteURL is not specified in the mt-config.cgi, the system attempts to guess the correct values as in previous versions.

The filename of the default search template, located inside of your search_templates directory (see the SearchTemplatePath directive). If you define and use alternate templates (see below), you don't need to use the default template.

Default value: default.tmpl.

Example:

    DefaultTemplate my-template.tmpl

This configuration directive specifies the default timezone for all weblogs. When creating a new weblog from the admin screen, the default timezone will be set (as a default) from the DefaultTimezone value.

Below is a table of each timezone and the value that you would use for DefaultTimezone.

ValueCommon timezone name
13New Zealand Daylight Savings Time
12International Date Line East
11 No label
10East Australian Time
9.5Central Australian Time
9Japan Time
8China Coast Time
7West Australian Time
6.5North Sumatra
6Russian Federation Zone 5
5.5Indian
5Russian Federation Zone 4
4Russian Federation Zone 3
3.5Iran
3Baghdad Time/Moscow Time
2Eastern Europe Time
1Central European Time
0Universal Time Coordinated
-1West Africa Time
-2Azores Time
-3Atlantic Time
-3.5Newfoundland
-4Atlantic Time
-5Eastern Time
-6Central Time
-7Mountain Time
-8Pacific Time
-9Alaskan Time
-10Aleutians-Hawaii Time
-11Nome Time

This configuration directive specifies to ...

Values:

  • 0 (disabled)
  • 1 (enabled)

When creating files and directories, Movable Type uses umask settings to control the permissions set on the files. If you are running under cgiwrap or suexec, you should use a value of 0022 for all of these settings.

Default values: 0111 (DBUmask, HTMLUmask, UploadUmask), 0000 (DirUmask)

Example:

    DirUmask 0022

The email address of an administrator of the Movable Type installation. This is used as the "From" address on some outgoing emails, when no other email address is at hand.

This directive must be set in order to use the the subscription form for readers who wish to be notified of new entries to your weblog. Failure to set the EmailAddressMain directive will cause an error when a subscriber tries to use the form to be added to your notification list.

This configuration directive specifies to send email notifications in BCC. When EmailNotificationBcc=0, the entry notification email will be sent to recipients whose addresses are in TO email header. For example, if a notification list has 100 recipients listed, one hundred notification emails will be sent.

For compatibility sake, the default value of this directive is 1 (emails are sent in BCC).

Values

  • 0
  • 1 (default)

A value of true (1) enables use of the Reply-To email header for notification emails. This will prevent MT from using the commenter's email address as the from address and will put it in the reply-to header instead.

If you are exposing the mt-add-notify.cgi interface to users, allowing them to sign up for site update notifications, you should set this value to something that outsiders would not be able to guess. This allows Movable Type to secure the notification signup process so that visitors have to verify their email addresses.

This is a switch for whether the extra archive fields are enabled in MT. These fields are deprecated; but this setting is turned on in the mt_config table if the upgrade process can't reliably deprecate the fields. An example of this would be an existing weblog that uses two separate domains for site url and archive url, or where the archive url is not a subpath of the site url.

When rebuilding individual archives, Movable Type splits up the rebuilding process into segments, where each segment consists of rebuilding N entries. The default value for N is 40, so by default, MT will rebuild 40 entries at a time, then move on to the next 40, etc. You can change that value globally here; for example, if you have a very stable server, you might wish to just get it all done in one batch.

Default value: 40

Example:

    EntriesPerRebuild 100

The number of words in the excerpt displayed when you use the <$MTEntryExcerpt$> tag inside of your search results. This setting is distinct from the "Number of words in excerpt" setting in your weblog configuration, because this setting is just used for excerpts in your search results.

Default value: 40

Example:

    ExcerptWords 100

To restrict the weblogs included in a search on your site, you can use the IncludeBlogs and ExcludeBlogs settings. IncludeBlogs lists the weblogs that will be included in the search, and ExcludeBlogs lists weblogs that will be excluded from the search. Do not try to use both--IncludeBlogs will override ExcludeBlogs. The default is to search all weblogs. Separate weblog IDs with commas.

Default value: none

Examples:

    ExcludeBlogs 1,3,4
    IncludeBlogs 2

This configuration directive specifies the name of the character encoding when exporting an activity log.

Default Value: ISO-8859-1

Example:

Content-Type: text/plain; charset=XXXX

By default, for each TrackBack item in your Movable Type system--either entry or category TrackBack items--an individual RSS feed will be automatically created and managed, listing the TrackBack pings for that item. These pings are stored in your Local Archive Path. If you want to turn off this feature, you can set GenerateTrackBackRSS to 0. The default setting is 1, to generate RSS files for each TrackBack item.

Default value: 1

Example:

    GenerateTrackBackRSS 0

Movable Type has a sanitize function that is automatically run against all comments and TrackBacks submitted to your blog and also any content produced by a template tag with the sanitize attribute defined (see Global Filters for more details).

This is done to remove any code (HTML or otherwise) that could compromise the security of your site. The function works by only allowing certain HTML tags defined by this setting. Any other tags, and all processing instructions (PHP or Javascript, for example) are stripped.

By default, Sanitize is turned on automatically for the following tags:

  • MTCommentAuthor
  • MTCommentEmail
  • MTCommentURL
  • MTCommentBody
  • MTPingTitle
  • MTPingURL
  • MTPingBlogName
  • MTPingExcerpt

If you want to turn off sanitize for one of these tags, you can use the sanitize attribute:

<MTPingTitle sanitize="0">

In addition, the sanitization process adds closing tags for any tags left open in the sanitized text. For example, if a visitor to your site opens a <b> tag and forgets the close it, the sanitize process will add a </b> tag in the most appropriate place it can find.

This configuration setting defines the default choice for all weblogs. It can be overridden on a per-weblog basis through use of the "Limit HTML tags" option. on the weblog's General setting page. For more details on the "Limit HTML tags" option and the sanitize function, see the relevant section of Chapter 1.8 in the User and Administration Manual entitled "Default Weblog Display Settings" (you can download the User and Administration Manual here).

Default value:

a href,b,i,br/,p,strong,em,ul,ol,li,blockquote,pre

Example:

GlobalSanitizeSpec blockquote,div

Syntax:

The sanitize spec consists of HTML tag names separated by commas. For each tag, you must also list any attributes that you wish to allow, separated by spaces. Some examples:

This will allow a tags with the href attribute and b tags:

a href,b

This will allow p tags and br tags:

p,br/

Note the / in the br/ tag in this example. That is necessary because of the tag-closing feature mentioned above: if the parser sees only an opening <br> tag, it will think that it needs to close this tag at the end of the sanitized text. Adding the / after the tag name tells the parser that this tag does not need a closing tag.

Note that you must specify any allowed attributes for the tag, unless you want all of the attributes to be stripped. For example, if you allow the a tag, you would also want to allow the href attribute for that tag, or the following HTML:

<a href="http://www.example.com/">

would be turned into this:

<a>

which probably isn't what you want.

If you wish to allow a certain attribute for any HTML tag in which it might appear, use a * as the tag name, followed by the list of attributes. For example:

br/,p,blockquote,* style

This will allow any of the following:

<br style="..." />
<p style="..." />
<blockquote style="...">

Note that you must still explicitly list any tags that you want included; * just allows the attribute listed in any of those tags.

For more details see the relevant section of Chapter 1.8 in the User and Administration Manual entitled "Default Weblog Display Settings".

You can download the User and Administration Manual here.

In addition to controlling permissions via umask settings, you can also use the HTMLPerms and UploadPerms settings to control the default permissions for files created by the system (either as output files or uploaded files). The only real use of this is to turn on the executable bit of files created by the system--for example, if MT is generating PHP files that need to have the executable bit turned on, you could set HTMLPerms to 0777.

  • Default value: 0666

Example:

HTMLPerms 0777

When creating files and directories, Movable Type uses umask settings to control the permissions set on the files. If you are running under cgiwrap or suexec, you should use a value of 0022 for all of these settings.

Default values: 0111 (DBUmask, HTMLUmask, UploadUmask), 0000 (DirUmask)

Example:

    HTMLUmask 0022

By default, outgoing HTTP requests are sent to the internet using the default network interface card (NIC) on the server running Movable Type. In some rare cases, it may be necessary or desirable to have the outbound traffic sent over a different network interface card or network connection. In these situations, enter the IP address of the network interface card that should be used to send the outgoing requests.

You may specify only the IP address (xxx.xxx.xxx.xxx) or an IP address and port number (xxx.xxx.xxx.xxx:#). If no port number is specified, the outgoing request will be sent from the specified IP address using the next available port number. If a port is specified, the outgoing request will be sent from the specified IP address AND port number. This is useful when you need a consistent source IP:port address for firewall filtering of outbound connections.

Don't specify a port unless it's absolutely necessary. If the port specified is already in use, the outgoing ping will fail without error.

Default value: none

Examples:

HTTPInterface 192.168.10.5

HTTPInterface 192.168.10.5:8080

If HTTPProxy is set, Movable Type will route HTTP requests through the specified proxy EXCEPT for requests destined for the domains listed in HTTPNoProxy.

Default value: localhost, 127.0.0.1

Example:

HTTPNoProxy internal.lan, example.tld

In some cases, a proxy server must be used to gain access to the internet if the computer Movable Type is running on is behind a firewall or on an internal private network. By setting HTTPProxy to the full URL address of your proxy server, Movable Type will route all HTTP requests through the proxy server specified.

Default value: none

Example:

HTTPProxy http://192.168.10.5:3128

When sending HTTP requests, Movable Type sets a timeout on the request, so that it doesn't take too long and appear to freeze up the system. You can override the default setting of 60 seconds by setting a different value with the HTTPTimeout directive. The value is assumed to be in seconds.

Default value: 60

Example:

HTTPTimeout 5

The absolute URL to prefix all help links.

Default?

Specifies the fully-qualified domain name and path (up to the username) for the user profile URL of the TypeKey-compatible authentication service you wish to use for your weblogs. To enable an alternate authentication service, you also need to define SignOnURL and SignOffURL.

Example:

http://profile.typekey.com/

Specifies the image toolkit used to create thumbnails from uploaded images. By default, the ImageMagick library and Image::Magick Perl module are used; if your system does not have these, you can use the NetPBM tools instead (assuming that your system has these tools installed). Possible values for this setting are ImageMagick or NetPBM.

Default value: ImageMagick

Example:

    ImageDriver NetPBM

The filesystem path to the import directory, which is used when importing entries and comments into the system. import is the directory where the files to be imported are placed.

Default value: ./import

Example:

    ImportPath ./import

To restrict the weblogs included in a search on your site, you can use the IncludeBlogs and ExcludeBlogs settings. IncludeBlogs lists the weblogs that will be included in the search, and ExcludeBlogs lists weblogs that will be excluded from the search. Do not try to use both--IncludeBlogs will override ExcludeBlogs. The default is to search all weblogs. Separate weblog IDs with commas.

Default value: none

Examples:

    ExcludeBlogs 1,3,4
    IncludeBlogs 2

The IndexBasename configuration setting is used to set the 'index' portion of the index file name for pages created by Movable Type. For example, the default is 'index' so any index filenames would be index.html (or another extension like php if you've configured the system as such). IIS users may want to use 'default' instead.

This section of the appendix details all configuration directives that can be defined in mt-config.cgi. Through use of these directives, you can control numerous aspects of the system.

Except for those which define things specific to your system (e.g. CGIPath and your database settings), all of them have defaults set by Movable Type. This means that not every directive will appear in mt-config.cgi. If you wish to override the default for a setting which does not appear in the file, simply add it and the desired value to your mt-config.cgi.

Certain tasks are by default run in the background. This frees up the user or other software to continue using the application while MT does important tasks, for example rebuilding. However, this feature does not work in some hosting environments. If you find that some features are not taking effect, try setting LaunchBackgroundTasks to 0.

Note: This setting is currently incompatible in persistent environments such as mod_perl and FastCGI.

The URL used to send the XML-RPC ping to sixapart.com if you have a Recently Updated Key.

Default value: http://www.movabletype.org/update/

Example:

    MTPingURL http://some.alternate.movabletype.org.server/path/

This configuration directive specifies the character encoding to be used for email if it is to be different from the PublishCharset. It takes a string value specifying the character encoding name.

Default Value: ISO-8859-1

Example:

Content-Type: text/plain; charset=XXXX

If you would rather use SMTP than sendmail, you should set the MailTransfer config setting to 'smtp' (as below). Possible values for MailTransfer are: smtp, sendmail, and debug (which just writes out mail messages to STDERR, for debugging purposes).

Default value: sendmail

Example:

MailTransfer smtp

The maximum number of results to return in a search. If this is a straight search, the number of results is per-weblog; if you set MaxResults to 5, for example, that would mean a maximum of 5 results for each weblog in your system. In a new comment search, this is the maximum number of entries with new comments.

Default value: no maximum (that is, return as many results as possible)

Example:

    MaxResults 5

By default, Movable Type looks for the NetPBM tools in three locations: /usr/local/netpbm/bin, /usr/local/bin, and /usr/bin. If your NetPBM tools are installed in a different location, you can adjust the NetPBMPath configuration setting. Note that this path should be the path to the directory containing the NetPBM binaries; for example, if your pnmscale binary is at /home/foo/netpbm/bin/pnmscale, you should set the value of NetPBMPath to /home/foo/netpbm/bin.

Default value: any of the above three locations

Example:

    NetPBMPath /home/foo/netpbm/bin

Provides specification for which Movable Type News URL to link to.

Default value:

Possible values:

  • en_US http://www.sixapart.com/movabletype/news/
  • ja http://www.sixapart.jp/movabletype/

The news box in the upper-right-hand corner of Movable Type's main menu is pulled over the web from the URL in this value.

You can set this box to display a custom "local" news feed (for example, your organization's internal news), by changing the NewsboxURL value. The content returned at that URL should be a small amount of balanced HTML which will fit within a document object of a varying width.

Use the special value "disable" if you would prefer that MT did not fetch any news in this location.

By default, when encoding data for XML Movable Type checks whether your data looks like it contains any HTML tags or other unsafe-for-XML data, and if so, it encloses your data in CDATA tags. Some news aggregators have trouble with combinations of CDATA with other data, though, so if this is causing a problem for you, you can use NoCDATA to encode any special characters into entities.

Default value: 0 (use CDATA)

Example:

    NoCDATA 1

By default Movable Type uses the Perl module HTML::Entities to encode characters into HTML entities, provided that you have it. However, in some circumstances, even if you do, you may not wish to use it for encoding, if for example, if you are using a language that uses a different character encoding (Polish, Russian, etc). In that case, you should set the value of NoHTMLEntities to 1.

Default value: 0 (use HTML::Entities, if it's available)

Example:

    NoHTMLEntities 1

On some Windows systems, neither flock() nor link() are available, so you can't use the default flock() locking, nor can you use the NFS-safe locking. In such cases, you can turn on the NoLocking option. Note that you should ONLY do this if your system supports nothing else--it is a last resort, because it increases the likelihood of database corruption. However, if you are the only person using the system (for example, if this is your personal server), this should not be as much of an issue.

Default value: 0 (use locking)

Example:

    NoLocking 1

By default, the search engine allows most of the above configuration directives to be overridden by search templates. This has the side effect that users could also override those settings by changing values in the query string. In particular, this could be dangerous if you have some private weblogs--even if you use IncludeBlogs or ExcludeBlogs to allow/deny certain weblogs to be searched, users could override that setting to search your private weblog.

You can use NoOverride to provide a comma-separated list of configuration directives that cannot be overriden by either search templates or users. This means that only the settings made in mt-config.cgi will be used.

Default value: none

Example:

NoOverride IncludeBlogs,ExcludeBlogs

When Movable Type loads any category information from the database, by default, it pre-loads all of the data related to placement of entries within categories (i.e. placement records) into RAM. This has the effect of making rebuilding operations and some uses of the administrative interface more efficient.

However, when the number of placement records grows large (either by quantity of entries or categories), this can have a negative effect on memory usage and system performance. If you are experiencing high memory usage during rebuilds you can disable this functionality by adding the following to your mt-config.cgi file:

NoPlacementCache 1

When this is set to true, a post made through the MetaWeblog API without a "publish" flag will be kept in draft status. When it is false, any MetaWeblog post on this installation will be published as soon as it is submitted. The default is 0, indicating that all MetaWeblog posts should be published.

Most users expect the submission of an entry from a MetaWeblog client to publish the post immediately. If, on the other hand, you want to submit entries into "draft" status, and your client supports it, set this option to 1.

By default, when writing to an output file, Movable Type will first write the data to a temp file, then rename that temp file. In the case that the process writing the data dies unexpectedly, this prevents the pages on your site from being erased. If you do not like this behavior (perhaps because it requires you to set directory permissions too liberally), you can use this directive to turn it off.

Default value: 0

Example:

    NoTempFiles 1

The ObjectDriver, Database, DBUser, DBPassword, DBHost, DBSocket and DBPort directives tell Movable Type where to find its database. For instructions on how to configure Movable Type for your database environment, see Installing Movable Type.

OneHourMaxPings and OneDayMaxPings settings allow you to limit the maximum number of TrackBack pings that you will accept in the period of either one hour or one day, respectively. In fact, the latter limit applies to the period which is 4000 times as long as the ThrottleSeconds value, which defaults to 20. Thus, by adjusting the ThrottleSeconds value, you can change the amount of time during which the OneDayMaxPings setting applies.

A higher-than-usual rate of incoming TrackBack pings can be indicative of malicious behavior. These settings give you a measure of protection against such behavior.

OneHourMaxPings and OneDayMaxPings settings allow you to limit the maximum number of TrackBack pings that you will accept in the period of either one hour or one day, respectively. In fact, the latter limit applies to the period which is 4000 times as long as the ThrottleSeconds value, which defaults to 20. Thus, by adjusting the ThrottleSeconds value, you can change the amount of time during which the OneDayMaxPings setting applies.

A higher-than-usual rate of incoming TrackBack pings can be indicative of malicious behavior. These settings give you a measure of protection against such behavior.

This configuration setting control which domains the system can send trackback pings or TrackBack auto-discovery requests to if enabled in OutboundTrackbackLimit setting.

This option is the configuration file counterpart to the Outbound TrackBack Control settings found on System Overview » Settings.

Examples

Allow TrackBack traffic only to example.com and any of its subdomains:

OutboundTrackbackDomains example.com

Allow TrackBack traffic only to intranet.example.com:

OutboundTrackbackDomains intranet.example.com

Allows TrackBack traffic to three different domains

OutboundTrackbackDomains example_one.com
OutboundTrackbackDomains example_two.com
OutboundTrackbackDomains example_three.com

This can also be done on a single line:

OutboundTrackbackDomains example_one.com example_two.com example_three.com

Don't forget, OutboundTrackBackDomains must always be accompanied by the following in the config file to be enabled:

OutboundTrackbackLimit  selected

This configuration directive allows you to limit outbound TrackBacks and TrackBack auto-discovery for the purposes of keeping your installation private.

Possible values include:

  • any (default) - Allows all regardless of destination
  • off - Prevents all regardless of destination
  • local - Allows only those requests/pings sent to weblogs within the same installation as the blog which initiated the action
  • selected - Allows all to one or more domains specified by the OutboundTrackbackDomains setting.

This option is the configuration file counterpart to the settings found on System Overview » Settings.

By default, outgoing Trackback and update pings are sent to the internet using the default network interface card (NIC) on the server running Movable Type. In some rare cases, it may be necessary or desirable to have the outbound ping traffic sent over a different network interface card or network connection. In these situations, enter the IP address of the network interface card that should be used to send the outgoing ping notifications.

You may specify only the IP address (xxx.xxx.xxx.xxx) or an IP address and port number (xxx.xxx.xxx.xxx:#). If no port number is specified, the outgoing ping will be sent from the specified IP address using the next available port number. If a port is specified, the outgoing ping will be sent from the specified IP address AND port number. This is useful when you need a consistent source IP:port address for firewall filtering of outbound connections.

Don't specify a port unless it's absolutely necessary. If the port specified is already in use, the outgoing ping will fail without error.

Default value: none

Example:

    PingInterface 192.168.10.5
    PingInterface 192.168.10.5:8080

If PingProxy above is set, Movable Type will route Trackback and update pings through the specified proxy EXCEPT for pings destined for the domains listed in PingNoProxy.

Default value: localhost, 127.0.0.1

Example:

    PingNoProxy internal.lan, example.tld

In some cases, a proxy server must be used to gain access to the internet if the computer Movable Type is running on is behind a firewall or on an internal private network. By setting PingProxy to the full URL address of your proxy server, Movable Type will route all Trackback and update pings through the proxy server specified.

Default value: none

Example:

    PingProxy http://192.168.10.5:3128

When sending pings--either TrackBack pings or update pings--Movable Type sets a timeout on the ping, so that it doesn't take too long and appear to freeze up the system. You can override the default setting of 15 seconds by setting a different value with the PingTimeout directive. The value is assumed to be in seconds.

Default value: 15

Example:

    PingTimeout 5

The path, relative to the Movable Type directory, where plugins are found. Defaults to 'plugins'.

Settings for enabling/disabling particular plugins. MT controls this through the mt_config table. For example:

 PluginSwitch nofollow/nofollow.pl=0

What specifically does hash type mean? How does a user specify values? Also how does a developer support this switch or is it automatic?

By default, the character encoding sent in the HTTP headers when you are using the system corresponds to the language you have chosen as your "Preferred Language" in your user profile. If you would like to override that you can set PublishCharset to the character encoding to be used. Be aware, though, that this will override the setting for every user and every weblog in this MT installation. An example encoding might be Shift_JIS.

Default value: encoding corresponding to Preferred Language

Example:

    PublishCharset Shift_JIS

Enables the publishing of the 'nav-commenters.gif' file, which is used to indicate the authentication status of comment posts. The default setting is '1,' which enables the publication of this image file to your weblog's root directory. To disable the publishing of this file, change this setting to '0.'

This is a URL from which Movable Type will fetch the public key used to verify authentication requests. The public key itself can be overridden locally using SignOnPublicKey.

The following settings specify the defaults for searches on your site; they can be overridden either through hidden form inputs, or in form inputs set by your users. You should probably leave these settings at the defaults and allow your users to override them. RegexSearch is a regular-expression search, and CaseSearch is a case-sensitive search.

Default value: 0 for each setting

Examples:

    RegexSearch 1
    CaseSearch 1

The sort order for the search results. Using ascend will list the entries in chronological order (oldest entry at the top); using descend will list the entries in reverse chronological order (newest entry at the top).

Default value: descend

Example:

    ResultDisplay ascend

The address of your SMTP server, to be used along with MailTransfer when set to 'smtp.'

Default value: localhost

Example:

    SMTPServer smtp.example.com

This configuration directive specifies the character encodings used by the DBMS client when using MySQL and PostgreSQL. This directive is needed by individuals using character codes incompatible with Latin-1.

Values:

  • 0 (default)
  • 1

If the directive was set(1), MT Object Drivers send SET NAMES command to DBMS before any query is sent. The parameter to SET NAMES sql statement (the name of character encoding) is pulled from PublishCharset. The SET NAMES call tells DBMS which client side character encoding to be used.

"Safe mode" enables certain warnings about security and other issues, and turns off some small features and capabilities (for example, linking templates to files with .cgi and other extensions). Safe mode is on by default; you can turn it off by setting SafeMode to 0.

Default value: 1

Example:

    SafeMode 0

The default number of days to search on a regular search (SearchCutoff) or on a new comment search (CommentSearchCutoff).

The default for SearchCutoff is to search from the beginning of your weblog (all of your entries), and the default for CommentSearchCutoff is the last month of comments.

Examples:

    SearchCutoff 7
    CommentSearchCutoff 7

By default, a search will search only through the entries in your weblog, not through the comments. A comment search is slower than an entry search, because there is more text to search through. You should probably leave this set to entries, and let your visitors override that setting if they wish to. Possible values are entries, comments, or both.

Default value: entries

Example:

    SearchElement both

By default, the script that Movable Type uses for the public search is called mt-search.cgi. In some situations--for example, if you are running MT under mod_perl, or if your server requires that your Perl scripts have the extension .pl--you may need different names for these scripts. You can set the names that will be used throughout the default templates and Movable Type code by changing these values.

Default value: mt-search.cgi

Example:

SearchScript mt-search.pl

See also:

The sort column for the search results. Using created_on will sort the entries by the authored on date; using title will sort the entries by title. This can be used with ResultDisplay to sort in either ascending or descending order.

Default value: created_on

Example:

    SearchSortBy title

The filesystem path to the search_templates directory, which is where your search templates should be located. This setting defaults to ./search_templates, which means that the search_templates directory is in the same directory as the mt.cgi file; you probably don't need to change this setting, unless you have moved your search_templates directory.

Default value: ./search_templates/

Example:

    SearchTemplatePath /home/foo/my/search_templates/

The SearchThrottleIPWhitelist configuration directive allows you to create a bypass mechanism (whitelist) for the IP-address-based search throttle.

You can specify one or more addresses on the same line. Multiple addresses can be separated by space, a semi-colon, or a comma.

Partial IP addresses are acceptable to allow bypass of IP blocks. Exact match from beginning of IP address

Any search from a matching IP address is allowed with no throttle control applied. If no match, the normal throttle test (using ThrottleSeconds) is executed.

Examples:

The following translates to all IPs in the 64.232.18.* block:

SearchThrottleIPWhitelist 64.232.18.

The following translates allows throttle bypass for 10...*:

SearchThrottleIPWhitelist 10.

The following (same as above but without the period):

SearchThrottleIPWhitelist 10

...is equivalent to the following:

SearchThrottleIPWhitelist 100 101 102 103 104 105 106 107 108 109

By default, Movable Type looks for sendmail in three locations: /usr/lib/sendmail, /usr/sbin/sendmail, and /usr/ucblib/sendmail. If your sendmail is in a different location, you can adjust the SendMailPath configuration setting.

Default value: any of the above

Example:

    SendMailPath /usr/sbin/sendmail

Default is 0. Enables IP display in commenter/trackback listings. This directive also enables the IP banning panel under the weblog's Settings screen.

Specifies the fully-qualified domain name and path (up to the query paramters) for the lougout URL of the TypeKey-compatible authentication service you wish to use for your weblogs. To enable an alternate authentication service, you also need to define SignOnURL and IdentityURL.

Example:

https://www.typekey.com/t/typekey/logout?

A DSA public key, used to verify authentication information for comment registration.

Specifies the fully-qualified domain name and path (up to the query paramters) for the login URL of the TypeKey-compatible authentication service you wish to use for your weblogs. To enable an alternate authentication service, you also need to define SignOffURL and IdentityURL.

Example:

https://www.typekey.com/t/typekey/login?

If you place all of your MT files in a cgi-bin directory, you will need to situate the static files from mt-static elsewhere, so that the webserver will not try to execute them.

Default value: none

Example:

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

Provides specification for which Movable Type Technical Support URL to link to.

Default value:

Possible values:

  • en_US http://www.sixapart.com/movabletype/support/
  • ja http://www.sixapart.jp/movabletype/support/

This setting will not appear in the default mt-config.cgi file.

The URL to which the update ping is sent when blog owners have chosen "Technorati" as a target for recently updated pings.

When processing uploaded files, if Movable Type notices that the file you uploaded already exists, it will allow you to overwrite the original file by first asking for your confirmation. To do this, MT needs to write the uploaded data to a temporary file. That temporary file is stored in the directory specified by the TempDir setting.

Default value: /tmp

Example:

    TempDir /tmp/

The file system path to the tmpl directory, which contains the front-end templates used by the Movable Type application.

Default value: ./tmpl

Example:

    TemplatePath ./tmpl

Movable Type uses IP-based comment throttling to provide some protection against comment flooding. ThrottleSeconds sets the number of seconds after which a visitor has posted a comment that he/she will not be allowed to post another comment. For example, if Alice posts a comment at 30 seconds after the minute, she will not be allowed to post another comment from the same IP address for the number of seconds set in this setting. You can increase this setting if you don't get too many people commenting often on your weblog.

This setting will also affect the rate at which TrackBack pings are accepted; see OneDayMaxPings.

Default value: 20

Example:

    ThrottleSeconds 60

Specifies the default timezone (in hours from UTC). This is used when logging actions that do not pertain to a specific weblog, since each weblog has its own timezone setting.

By default, the script that Movable Type uses for TrackBacks is called mt-tb.cgi. In some situations--for example, if you are running MT under mod_perl, or if your server requires that your Perl scripts have the extension .pl--you may need different names for these scripts. You can set the names that will be used throughout the default templates and Movable Type code by changing these values.

Default value: mt-tb.cgi

Example:

TrackbackScript mt-tb.pl

See also:

If your webserver is behind an HTTP proxy, it will look as if all comments and trackback pings are coming from the same IP address, making it difficult (nay, impossible) to ban any particular sender's IP address. If TransparentProxyIPs is 1, Movable Type will ignore the first IP address it sees and try to determine the external IP from which a comment or trackback ping was received. Note that, because there could be other HTTP proxies in the chain, this is still not necessarily the IP address of the machine that sent the comment or trackback ping. Only use this option if you know that your webserver is always accessed through a proxy, since otherwise the IP address information of the remote host will be lost.

Gives the version of TypeKey which your templates are configured to use. Normally, the default setting is correct, but some older templates were hard-coded to use TypeKey Protocol version 1. To do TypeKey Protocol sign-ins with such templates, use:

    TypeKeyVersion 1

By default, the script that Movable Type uses for upgrading is called mt-upgrade.cgi. In some situations--for example, if you are running MT under mod_perl, or if your server requires that your Perl scripts have the extension .pl--you may need different names for these scripts. You can set the names that will be used throughout the default templates and Movable Type code by changing these values.

Default value: mt-upgrade.cgi

Example:

UpgradeScript mt-upgrade.pl

See also:

In addition to controlling permissions via umask settings, you can also use the HTMLPerms and UploadPerms settings to control the default permissions for files created by the system (either as output files or uploaded files). The only real use of this is to turn on the executable bit of files created by the system--for example, if MT is generating PHP files that need to have the executable bit turned on, you could set HTMLPerms to 0777.

  • Default value: 0666

Example:

UploadPerms 0777

When creating files and directories, Movable Type uses umask settings to control the permissions set on the files. If you are running under cgiwrap or suexec, you should use a value of 0022 for all of these settings.

Default values: 0111 (DBUmask, HTMLUmask, UploadUmask), 0000 (DirUmask)

Example:

    UploadUmask 0022

This configuration directive specifies to use Jcode.pm instead of Encode.pm for transcoding.

Values:

  • 0 (Use Encode.pm - Default value)
  • 1 (Use Jcode.pm)

By default Movable Type uses Perl's flock() function to lock your databases while reading and writing. On systems using NFS-mounted directories, however, Perl's flock() may fail, unless the perl executable has been built to use fnctl(2) instead of flock(2); and even then, it is not certain that the locking will truly work.

Thus, if you have problems running Movable Type on systems using NFS, you can use the UseNFSSafeLocking directive to use simpler file locking that will work over NFS.

Default value: 0 (don't use NFS-safe locking)

Example:

    UseNFSSafeLocking 1

Global plugin control switch. Default is true (1). MT controls this through the mt_config table.

Should directives marked with "MT controls this through the mt_config table" even be in here?

This configuration directive specifies whether to use SQLite2 instead of SQLite3 as the database.

Values:

  • 0 (Use SQLite. Default value)
  • 1 (Use SQLite2)

The duration of user sessions in seconds for those that are not using the "Remember Me" option. The default is 14400 seconds or 4 hours.

By default, the script that Movable Type uses for dynamic weblog view (a legacy developmental script from an early version of the software) is called mt-view.cgi. In some situations--for example, if you are running MT under mod_perl, or if your server requires that your Perl scripts have the extension .pl--you may need different names for these scripts. You can set the names that will be used throughout the default templates and Movable Type code by changing these values.

Default value: mt-view.cgi

Example:

ViewScript mt-view.pl

See also:

The URL used to send the XML-RPC weblogs.com ping.

Default value: http://rpc.weblogs.com/RPC2

Example:

    WeblogsPingURL http://some.alternate.weblogs.com.server/path/

By default, the script that Movable Type uses for XML-RPC is called mt-xmlrpc.cgi. In some situations--for example, if you are running MT under mod_perl, or if your server requires that your Perl scripts have the extension .pl--you may need different names for these scripts. You can set the names that will be used throughout the default templates and Movable Type code by changing these values.

Default value: mt-xmlrpc.cgi

Example:

XMLRPCScript mt-xmlrpc.pl

See also:

Six Apart
Makers of weblog software and services for individuals, organizations and businesses.
This website is powered by Movable Type.