. 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. # # CommentScript mt-comments.pl # TrackbackScript mt-tb.pl # SearchScript mt-search.pl # XMLRPCScript mt-xmlrpc.pl # ViewScript mt-view.pl # # # 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 blog in this MT installation. An example encoding might be # "Shift_JIS". # # PublishCharset Shift_JIS # # # "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. # # SafeMode 0 # # # By default, Movable Type cleans up ("sanitizes") any data submitted by # visitors to your site. This is done to remove any code (HTML or otherwise) # that could compromise the security of your site. The sanitization code works # by only allowing certain HTML tags--any other tags, and all processing # instructions (PHP, for example) are stripped. The GlobalSanitizeSpec # setting, then, specifies the tags and attributes that are allowed. The # default setting is "a href,b,br/,p,strong,em,ul,li,blockquote". # # GlobalSanitizeSpec br/,p # # # 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. # # GenerateTrackBackRSS 0   ## ## Search configuration ##  # 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. # # SearchTemplatePath ./search_templates/ # # # 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. The default value is 'default.tmpl'. # # DefaultTemplate default.tmpl # # # If you have multiple blogs, 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.  AltTemplate comments comments.tmpl # AltTemplate work work.tmpl # AltTemplate play play.tmpl # # # To restrict the blogs included in a search on your site, you can use the # IncludeBlogs and ExcludeBlogs settings. IncludeBlogs lists the blogs that # will be included in the search, and ExcludeBlogs lists blogs that will be # excluded from the search. Do not try to use both--IncludeBlogs will # override ExcludeBlogs. The default is to search all blogs. Separate blog # IDs with commas. # # ExcludeBlogs 1,3,4 # IncludeBlogs 2 # # # 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. The default value for # each of these settings is 0. # # RegexSearch 1 # CaseSearch 1 # # # 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 blog (all of your # entries), and the default for CommentSearchCutoff is the last month of # comments. # # SearchCutoff 7 # CommentSearchCutoff 7 # # # The maximum number of results to return in a search. If this is a straight # search, the number of results is per-blog--if you set MaxResults to 5, # for example, that would mean a maximum of 5 results for each blog in your # system. In a new comment search, this is the maximum number of entries # with new comments. # # MaxResults 5 # # # 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). # The default is 'descend'. # # ResultDisplay ascend # # # 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 blog # configuration, because this setting is just used for excerpts in your # search results. The default is 40 words. # # ExcerptWords 100 # # # By default, a search will search only through the entries in your blog, # 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'. # # SearchElement both # # # 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.cfg will be used. # # NoOverride IncludeBlogs,ExcludeBlogs/images/mt-logo.gif" align="top" width="233" height="68" border="0">