Not a developer? Go to MovableType.com

MovableType.org
Documentation
Home / Documentation / Developer

Using this Guide

Often this guide needs to refer to a path on the file system that is relative to Movable Type’s home directory. Movable Type’s home directory, also known or referred to by the phrase “MT_HOME” or “$MT_HOME,” is where Movable Type is installed. Because Movable Type can be installed in numerous locations depending upon personal preference, operating system conventions, this guide (as well as most examples online) utilizes the following conventions to refer to the path where you can find Movable Type’s files:

  • /path/to/mt

Example

Let’s assume for a moment that you have installed Movable Type into the following directory on your web server:

/var/www/vhosts/www.somedomain.com/cgi-bin/mt

If this is true, then you should find the following files on your filesystem:

  • /var/www/vhosts/www.somedomain.com/cgi-bin/mt/mt.cgi
  • /var/www/vhosts/www.somedomain.com/cgi-bin/mt/mt-config.cgi
  • /var/www/vhosts/www.somedomain.com/cgi-bin/mt/lib/MT.pm
  • And many more…

So using, that as the basis for this example, if this guide refers to the path:

/path/to/mt/lib/MT/App/CMS.pm

Then that path can be translated into the following path on your filesystem:

/var/www/vhosts/www.somedomain.com/cgi-bin/mt/lib/MT/App/CMS.pm

Also, this guide makes frequent reference to your Plugin.pm file. The Plugin.pm file refers to the main library file (located in /path/to/mt/lib/PluginName/) that contains all of the application logic and Perl code for your plugin. Technically this file can be named whatever you want provided that it is a valid Perl module. For the purposes of consistency and the integrity of the examples in this guide, we use and refer to this file as “Plugin.pm”.

Back