Upgrade Typo from sources

Before you get started, make sure you meet the minimum requirements.

Three Step Upgrade

For these instructions, it is assumed that your blog's URL is http://example.com. Note that during the upgrade process access to your blog may not work for your visitors.

Step 0: Before You Get Started

Just in case something goes wrong, make sure you have a backup. Backup your mysql database and your files.

Make sure the database user name registered to Typo has permission to create, modify, and delete database tables. If you installed Typo in the standard way, and nothing has changed since then, you are fine.

Deactivate your sidebar plugins. A plugin might not be compatible with the new version, so it's nice to check for new versions of them and deactivate any that may cause problems. You can reactivate plugins one-by-one after the upgrade.

Backup your public/ and your themes/ directories. If you're using one of the defaults themes, they will be overriden with files from your new Typo version.

Step 1: Replace Typo files

Get the latest Typo. Either download and extract it to your computer or download it directly to the server.

As a reminder, to extract a tar.gz to a folder use this command, replacing (folder name) with the name of your folder:

  tar -xvzf typo-version.tgz -C ./(folder name)

Copy the new Typo files to your server, overwriting old files in the root. You may use FTP or shell commands to do so. Note that this means all the files, including all the files in the root directory as well. If you use one of the default themes and have customized it, then you can skip that theme.

Also take care to preserve the content of the database.yml file in the config/ directory. This file contains current settings for your existing installation, e.g. database sign-in information.

Step 2: Upgrade your installation

If you're upgrading from a version prior to 5.0.4b

Adding Typo profiles and roles has brocken the classic upgrade way, so you'll need to do it manually.

If you're running in production mode (the most frequent):

  rake RAILS_ENV=production db:migrate

If you're running in development mode:

  rake RAILS_ENV=development db:migrate

If you're upgrading from a version more recent than 5.0.4b

Go to your blog administration. At login time, will be automatically redirected to an upgrade page. Just click on the Upgrade schema button and you're done!

Step 3: Set things back to normal

Enable your plugins back.

If you have caching enabled, your changes will appear to users more immediately if you clear the cache at this point (and if you don't, you may get confused when you see the old version number in page footers when you check to see if the upgrade worked).

Your Typo installation is successfully upgraded. That's as simple as we can make it.

Consider rewarding yourself with a blog post about the upgrade, reading that book or article you've been putting off, or simply sitting back for a few moments and let the world pass you by.