Planning Movable Type hosting and a supported migration

Movable Type uses a different architecture from an ordinary PHP-only CMS. Its publishing application depends on a supported Perl/CGI or PSGI environment, and optional dynamic publishing has additional requirements. Confirm the exact current edition and its vendor documentation before choosing a hosting plan or replacing an older installation.

01 Check the environment and edition

  1. Identify the Movable Type release, license and publishing mode you intend to run. Use the requirements for that release, not old instructions for Movable Type 5 or 6.
  2. Confirm that the hosting environment supports the required execution model, Perl modules, database and scheduled publishing. Ask us to review these requirements if they are not exposed in the plan details.
  3. Inventory existing blogs, templates, uploaded assets, plugins and published output. Back up the database and all application/content files before a version change.

02 Install or migrate through the supported process

Use the publisher's current package and installation or upgrade instructions. Configure the application URL, static assets, database and publishing directories with narrowly scoped permissions. Do not enable obsolete runtime versions or install an old Softaculous bundle merely because it is listed. A fresh installation and a migration of existing publishing data are separate tasks.

03 Verify publishing end to end

  1. Run the vendor's supplied requirements check in the intended environment and remove or restrict diagnostic tools afterward.
  2. Create a test entry, publish it and inspect the generated output, media and archive links. Test scheduled publishing if used.
  3. Check an editor account, comments or forms where enabled, and any PHP dynamic publishing separately. Confirm the recovery backup contains both data and templates.

A common question

Will changing the PHP selector fix every Movable Type requirement?

No. The publishing application also depends on its Perl execution environment and modules. Diagnose the actual component and follow the requirements of the selected release.

Sources and further reading

  • 0 Users Found This Useful
  • development
Was this answer helpful?

Related Articles

Installing Joomla and checking the first setup

Joomla is a CMS with articles, menus, templates and extension-based features. This guide helps...

Installing Open Real Estate and checking the first setup

Open Real Estate is a property-listing application for estate and property websites. This guide...

Installing MODX and checking the first setup

MODX is a content platform built around resources, templates and reusable components. This...

Installing e107 and checking the first setup

e107 is a CMS with content, user and plugin management. This guide helps you check hosting...

Installing XOOPS and checking the first setup

XOOPS is a modular CMS with group permissions and content modules. This guide helps you check...