• Enable dynamic publishing
• Linked templates
• Output file
• Rebuild with indexes
• Template body
• Template name

Choosing this option causes Movable Type to dynamically publish this index template insetad of writing the output to the filsystem. This option is only present when using a SQL database. (i.e. MySQL, SQLite or PostgreSQL).

Back to top | Permalink | Comments (0)

This field contains the path to the linked file for a particular template.

Some users will find it easier to edit the template layouts in a text editor like BBEdit or a web page editor like Adobe Go Live instead of the Movable Type browser interface. You can optionally link a Movable Type template to an external file. This allows you to edit your templates while keeping the copy that is inside Movable Type synchronized with the external file.

In the field labeled "Link this template to a file" on the New/Edit Template screen, enter either a full path to your external file, or a path relative to the Local Site Path. For security purposes, the file extension cannot be .cgi, .pm, .pl, or .cfg. This is to avoid the potential of overwriting Movable Type program files and corrupting the system. When you save the template the files will be linked.

The synchronization process works in both directions. When you load a template for editing, the date of the linked file is checked, and the template is updated if the linked file date is more recent. When you save a template through the Movable Type CMS, the linked file is updated with your changes.

When you create a new template without specifying a template body, and link it to a file that already exists, the contents of that file will be pulled in to the template. If you do specify a template body, however, and the linked file already exists, that linked file will be overwritten with the template body you specified.

For instance, if you would like to maintain your Main Index template with an external editor, you would first set the linked file field to something like index.html.tmpl and click the "Save" action button. You can then edit this file externally. The next time you rebuild, Movable Type will read in the latest version of the linked file index.html.tmpl and use that as the template body. During this process it will also update the copy of the template in the Movable Type database, so that the next time it needs the template it can use the version in the database.

Another added benefit to linking a template to an external file is that you can synchronize templates across multiple weblogs. This is particularly helpful when you have multiple weblogs that require the same layout.

To do this, link all of the source weblog's templates to file. This creates external files of all the template you want to share. Then go into the other weblogs and link their templates to the files created by the first one. When you rebuild those weblogs they will now have the same templates.

For relative file paths, the root is typically the MT directory, but this can vary in particular server environments so we recommend specifying a full path (i.e. starting with a slash '/') for this field.

Back to top | Permalink | Comments (0)

This field contains the filename and, optionally, the filesystem path to which Movable Type should publish an index template. If a relative path is used, it is relative to the blog's Site Root directory.

Examples

In the following examples, SITE_ROOT represents the blog's site root directory:

In the third example above, the '..' is geekspeak for the parent directory. So in English, that output file value means:

"Write the published file for this index template out to blog.inc.php in the directory otherblog which is two directory levels above SITE_ROOT"

Represented visually, it would be:

grandparent/
    otherblog/
        blog.inc.php
    parent/
        SITE_ROOT/

Related

• Site root

Back to top | Permalink | Comments (0)

When this box is checked, the index template will be rebuilt any time all index templates are rebuilt. Otherwise, it is only rebuilt when this specific template is rebuilt.

Back to top | Permalink | Comments (0)

This textarea contains the template code that is used to compile the page(s) which the template is responsible for producing.

Back to top | Permalink | Comments (0)

This field contains the name of the template as shown in the template listing. Although the field is free-form, you should avoid non-alphanumeric characters (spaces are fine) and redundant template names within a particular weblog.

Back to top | Permalink | Comments (0)