Version 26 (modified by slam, 9 years ago) (diff)


Upgrading your Drupal installation at May First/People Link

May First/People Link will automatically update your Drupal installation for you, however, we cannot upgrade your Drupal installation. The difference between update and upgrade is:

changing minor versions. Updates represent small changes, usually to fix bugs and security holes. In the Drupal 4 branch, examples of minor version changes are: 4.7.4 to 4.7.5. In the Drupal 5, 6, and 7 branches, examples of minor version changes are 5.1 to 5.2 or 6.5 to 6.6. Updates are automatic and occur sometime shortly after a Drupal minor version release.
an upgrade means changing between major Drupal versions. That means going from 4.6 to 4.7. Or from 4.7 to 5. Or from 5 to 6. Or from 6 to 7.

Why doesn't May First/People Link do major upgrades? We would love to! However, it is a complicated process that is different for each site. In other words, we cannot automate the process, like we can for minor updates. If we upgraded everyone's Drupal web site we would have no time to do anything else!

How to upgrade

If you would like to upgrade your site, here are directions for how to do that. If you are not comfortable doing this, and you are able to hire a developer to help, please post a ticket of the type "Project/Need to hire someone" and we will try to match you with a techie.

In addition, these directions are for upgrading from 5 to 6, however, they also apply if you are upgrading from 6 to 7 (or, roughly, if you are going from 4.7 to 5). Please remember - you must upgrade incrementally. In other words, you can't go directly from 4.7 to 7. You must first upgrade from 4.6 to 4.7, and then upgrade from 4.7 to 5 and then from 5 to 6, etc.

  • Assemble your team. To upgrade Drupal, you will need someone who is comfortable using the command line and using secure shell (ssh). If that is not you, you may want to recruit some helpers.
  • Plan the upgrade. You should be prepared to spend several hours upgrading your site. If all goes smoothly you won't need that time, however, it's better to be prepared. Before beginning, review all of the third party modules that you have installed. You can review these modules by looking in your web/sites/default/modules or web/sites/all/modules directory. For each module installed, search the web site to find the Drupal version of the module corresponding to the Drupal version you are upgrading to. If you can't find an appropriate version (this happens often) you will not be able to use it! For each module, download the new version to your local computer.
  • Make a list of custom scripts and other special templates you may have in your theme's directory. If you are using Drupal without any customization ("out of the box") with a standard theme (e.g. Bluemarine), your upgrade will go very smoothly. If you have customized scripts and pages, these may break after the upgrade (requiring you to tweak them). If you do have a heavily customized theme, you may consider switching to a core theme before the upgrade. Then, upgrade your theme (there are notes for doing this on, and finally try switching back to your custom theme.
  • Upgrade all your third party modules to the most recent version. If you are running Drupal 5 or later, ensure all third party modules are at the most recent Drupal 5 version first. You can do this easily with drush. From the command line, in your web directory, type:
    drush pm-update
    NOTE: When prompted to upgrade Drupal core, answer no. You will do this later.

If you are upgrading from a version prior to 5, you will need to do these module upgrades manually.

  • Test to make sure your site is still functioning properly before you continue.
  • Make a backup! You will want to backup both your directories and your database. To backup these up, ssh into your server and run the following commands (replacing YOURDOMAIN with your actual domain name and YOURDATABASE with the name of your database):
    cp -r -p YOURDOMAIN/web web.backup
    mysqldump YOURDATABASE  > drupal_db.backup.sql
  • Login to your Drupal site as the user with User ID 1. If that user is mayfirst, then change the mayfirst user's password and log in as the mayfirst user. You must be logged in with user id 1 for the upgrade to work properly. If you are not sure what user id you are logged in as, click the My Account link in your menu and look at the web address you are sent to. It will say: /user/3 if you are user id 3. Or /user/1 if you are user id 1.
  • Go to your admin/settings page and check the box to indicate that your site is down for maintenance.
  • Disable all third party modules. Go to the modules admin section of your web site. Compare the enabled modules with your list of third party modules. You can find a list of your third party modules by looking in your web/sites/default/modules directory. Uncheck each third party module that is checked.
  • Using secure FTP or ssh, rename the modules directory your sites/default/modules directory to modules.d5 (or d6, etc.). Create a new, empty modules directory.
  • Use the members control panel to update the symbolic links in your Drupal root: From your member control panel, select the hosting order you want to upgrade, choose the "Web App (Drupal)" tab, and click "edit" next to the Drupal installation you're upgrading. Select the version of Drupal you're upgrading to, and click Submit. Note: if you don't see an entry under Web Apps, it means your existing installation is prior to Drupal 5 or was not originally installed as a part of the May First/People Link Drupal system.

In this case - you will need to remove all the files in your web directory except the sites directory and, if you have them, files or images directories. Be sure to remove the .htaccess file as well. Once you have removed these files and directories, then use the Members Control panel to install Drupal. If you previously were running a version of Drupal that is installable by the control panel, install that version to ensure everything is still working smoothly. Then, edit your installation to change from your current version to the next available version. If you are running a version older than version 5, then install version 5.

  • Now - your site is using code for the upgraded Drupal version you just selected. Next, go to the update.php script on your site. The should be something like:
  • Follow the directions for updating your database. Copy and paste all the output in case you run into problems later - it will be useful to reference it.
  • Test your site. Remember - your third party modules will not yet be working!
  • One by one, download and enable the new, upgraded version of each third party module to your modules directory (web/sites/default/modules). After enabling each module, return to the update.php script to run any needed database updates.

When you are done - report your results! Let us know how it goes. Edit this page to add new lessons learned.


Rebuilding Permissions

  • Just learned a lesson about the upgrade process and wanted to share it. When you upgrade, you may find that "normal" users can't access your site's content even though the permissions appear to be correct. The solution is to rebuild the permissions cache, which you can find via Adminster > Content Management > Post Settings. At the top of that page, you'll see an option to rebuild permissions. Hit the button to rebuild permissions and you should find that your site content is now accessible.

CCK and Drupal 6

  • For people already upgrading from Drupal 5 to 6 who have the module Content Construction Kit installed, here's an important reminder:

Before upgrading your site to Drupal 6, you must upgrade CCK to version 5.x-1.9 and run all updates. Updating to 5.x-1.9 is especially important before an upgrade because that version includes a fix to ensure you don't lose data when you disable modules in preparation for the upgrade.

So you upgrade to the latest CCK and then run the update script in Drupal 5, before doing the Drupal upgrade.

CCK and Drupal 7

If you are upgrading from Drupal 6 to 7, CCK is now core but you will need to run the migration for those fields. Instructions for doing that are here: - the specific instruction says:

Upgrade fields If you were using CCK (and perhaps additional modules) to create fields for your content types, you will need to upgrade the data in those fields as a separate step. Download the Drupal 7 CCK module, and turn on Content Migration. Go to Structure > Migrate Fields or http://example/com/admin/structure/content_migrate for a page to walk you through the migration process. There are now several types of fields in core, but not every type. You might need to download Drupal 7 versions of contributed modules to support other types of fields. Learn more about migrating content from CCK to Core Fields.