Upgrading from Drupal Commons 2.x

We strongly recommend that you test the upgrade procedure on a clone or copy of your Drupal Commons site in a test server environment before you upgrade your production server. For more information about how to import a copy of your site into Acquia Dev Desktop for testing, see Importing existing sites and Drupal codebases.

To upgrade your server's Drupal Commons installation from Drupal Commons 2.x, select from following sections procedures based on the version of Drupal Commons you're upgrading to.

Current upgrade procedure (Drupal Commons 2.9 - 2.13)

To upgrade your server to Drupal Commons 2.9 - 2.13 from a previous version of Drupal Commons 2.x:

Preparing for the upgrade

  1. Download Drupal Commons from the Acquia Downloads page.
  2. Back up your code (everything in your Drupal root directory) and your database.
  3. Open a web browser, and then log in to your site as the main administrator account.
  4. Place the site in "Off-line" mode. This allows database updates to run without interruption, and without displaying errors to visitors of your site. To change the mode:
    1. In your web browser, open http://[site_URL]/admin/settings/site-maintenance, where [site_URL] is the URL of your Drupal Commons server.
    2. Select the Off-line option.
    3. Click Save configuration.

Installing the upgrade

  1. Extract the new Drupal Commons tarball and copy the contents into your document root.
  2. In your web browser, open http://[site_URL]/update.php.
  3. In your web browser, open the Performance page at http://[site_URL]/admin/settings/performance, and then click Clear cached data.
  4. Open the Features page at http://[site_URL]/admin/build/features.
  5. Examine the list of Features, and for each feature with a State of Overridden, revert the feature. To revert a feature:
    1. Click the Overridden link for the feature.
    2. Select all of the check boxes relating to overridden components on the page.
    3. Click Revert components.

Completing the upgrade and restarting your website

  1. If you're upgrading to Drupal Commons 2.14 or higher from Drupal Commons 2.13 or lower, and your server environment uses Apache (including Acquia Cloud), you must modify your files directories' .htaccess files to resolve a security vulnerability. For information about how to modify your .htaccess files, see Modifying .htaccess for Security announcement SA-CORE-2013-003.
  2. Allow your visitors to access your web site by returning your site to "Online" mode:
    1. In your web browser, open http://[site_URL]/admin/settings/site-maintenance.
    2. Select the Online option.
    3. Click Save configuration.

Previous versions of Drupal Commons

Drupal Commons 2.6 & 2.7

To upgrade your server to Drupal Commons 2.6 or 2.7 from Drupal Commons 2.x:

Preparing for the upgrade

  1. Download Drupal Commons from the Acquia Downloads page.
  2. Back up your code (everything in your Drupal root directory) and your database.
  3. Open a web browser, and then log in to your site as the main administrator account.
  4. Place the site in "Off-line" mode. This allows database updates to run without interruption, and without displaying errors to visitors of your site. To change the mode:
    1. In your web browser, open http://site_URL/admin/settings/site-maintenance, where site_URL is the URL of your Drupal Commons server.
    2. Select the Off-line option.
    3. Click Save configuration.

Installing the upgrade

  1. Extract the new Drupal Commons tarball and copy the contents into your document root.
  2. In your web browser, open http://site_URL/update.php.
  3. In your web browser, open the Performance page at http://site_URL/admin/settings/performance, and then click Clear cached data.
  4. Open the Features page at http://site_URL/admin/build/features.
  5. Examine the list of Features, and for each feature with a State of Overridden, revert the feature. To revert a feature:
    1. Click the Overridden link for the feature.
    2. Select all of the check boxes relating to overridden components on the page.
    3. Click Revert components.

Completing the upgrade and restarting your website

Allow your visitors to access your web site by returning your site to "Online" mode:

  1. In your web browser, open http://site_URL/admin/settings/site-maintenance.
  2. Select the Online option.
  3. Click Save configuration.

Note: If you use the Commons Origins theme and it displays with errors:

  1. Clear the site cache at http://site_URL/admin/settings/performance.
  2. Reset your local browser cache with a hard refresh. For most browsers, you can do this by pressing the Shift key while selecting Refresh.

Drupal Commons 2.5

To upgrade your server to Drupal Commons 2.5 from Drupal Commons 2.x:

Preparing for the upgrade

  1. Back up your code (everything in your Drupal root directory) and your database.
  2. Open a web browser, and then log in to your site as the main administrator account.
  3. Place the site in "Off-line" mode. This allows database updates to run without interruption, and without displaying errors to visitors of your site. To change the mode:
    1. In your web browser, open http://site_URL/admin/settings/site-maintenance, where site_URL is the URL of your Drupal Commons server.
    2. Select the Off-line option.
    3. Click Save configuration.

Installing the upgrade

  1. Extract the new Drupal Commons tarball and copy the contents into your document root.
  2. In your web browser, open http://site_URL/update.php.
  3. Follow the prompts to "Update" your server.
    You may see the following failed update from the OG module: ALTER TABLE og_uid ADD INDEX uid (uid)
    You can safely ignore this warning.
  4. In your web browser, open the Performance page at http://site_URL/admin/settings/performance, and then click Clear cached data.
  5. Open the Features page at http://site_URL/admin/build/features.
  6. Examine the list of Features, and for each feature with a State of Overridden, revert the feature. To revert a feature:
    1. Click the Overridden link for the feature.
    2. Select all of the check boxes relating to overridden components on the page.
    3. Click Revert components.

Completing the upgrade and restarting your website

Allow your visitors to access your web site by returning your site to "Online" mode:

  1. In your web browser, open http://site_URL/admin/settings/site-maintenance.
  2. Select the Online option.
  3. Click Save configuration.

Note: If you use the Commons Origins theme and it displays with errors:

  1. Clear the site cache at http://site_URL/admin/settings/performance.
  2. Reset your local browser cache with a hard refresh. For most browsers, you can do this by pressing the Shift key while selecting Refresh.

Drupal Commons 2.4

To upgrade your server to Drupal Commons 2.4 from Drupal Commons 2.x, complete the following steps:

Preparing for the upgrade

  1. Back up your code (everything in your Drupal root directory) and your database.
  2. Open a web browser, and then log in to your site as the main administrator account.
  3. Place the site in "Off-line" mode. This allows database updates to run without interruption, and without displaying errors to visitors of your site. To change the mode:
    1. In your web browser, open http://site_URL/admin/settings/site-maintenance, where site_URL is the URL of your Drupal Commons server.
    2. Select the Off-line option.
    3. Click Save configuration.

Installing the upgrade

  1. Extract the new Drupal Commons tarball and copy the contents into your document root.
  2. In your web browser, open http://site_URL/update.php
  3. Follow the prompts to "Update" your server.
    You may see the following failed update from the OG module: ALTER TABLE og_uid ADD INDEX uid (uid)
    You can safely ignore this warning.
  4. In your web browser, open the Performance page at http://site_URL/admin/settings/performance, and then click Clear cached data.
  5. Open the Features page at http://site_URL/admin/build/features.
  6. Examine the list of Features, and for each feature with a State of Overridden, revert the feature. To revert a feature:
    1. Click the Overridden link for the feature.
    2. Select all of the check boxes relating to overridden components on the page.
    3. Click Revert components.
  7. Open the Triggered rules page at http://site_URL/admin/rules/trigger.
  8. Examine the list of Active rules, and for each rule with a Status of Modified, note their customized rules messages to allow you to re-enter them after the upgrade is complete.
  9. After you note each of the customized rules messages, click the revert link to the right of the Modified status entry for each rule. Note: It should not be necessary to revert your customized rules messages during future Drupal Commons releases.
  10. Open the Activity Log page at http://site_URL/admin/settings/activity_log, and then click Clear all message caches.
  11. Select the Regenerate Activity tab (http://site_URL/admin/settings/activity_log/regenerate), and then click Regenerate.
  12. Re-enter any customized rules messages you reverted as part of this upgrade procedure on the Triggered rules page (http://site_URL/admin/rules/trigger).

Completing the upgrade and restarting your website

Allow your visitors to access your web site by returning your site to "Online" mode:

  1. In your web browser, open http://site_URL/admin/settings/site-maintenance.
  2. Select the Online option.
  3. Click Save configuration.

Drupal Commons 2.3

Upgrading from Drupal Commons 2.2

To upgrade your server to Drupal Commons 2.3 from Drupal Commons 2.2:

  1. Back up your code (everything in your Drupal root directory) and your database.
  2. Open a web browser, and then log in to your site as the main administrator account.
  3. Place the site in "Off-line" mode. To change the mode:
    1. In your web browser, open http://[example]/admin/settings/site-maintenance, where [example] is the URL of your Drupal Commons server.
    2. Select the Off-line option.
    3. Click Save configuration.
  4. Extract the new Drupal Commons tarball and copy the contents into your document root.
  5. Allow your visitors to access your web site by returning your site to "Online" mode:
    1. In your web browser, open http://[example]/admin/settings/site-maintenance.
    2. Select the Online option.
    3. Click Save configuration.

Upgrading from Drupal Commons 2.0 or 2.1

To upgrade your server to Drupal Commons 2.3 from Drupal Commons 2.0 or 2.1:

  1. Back up your code (everything in your Drupal root directory) and your database.
  2. Open a web browser, and then log in to your site as the main administrator account.
  3. Place the site in "Off-line" mode. This allows database updates to run without interruption, and without displaying errors to visitors of your site. To change the mode, complete the following steps:
    1. In your web browser, open http://[example]/admin/settings/site-maintenance, where [example] is the URL of your Drupal Commons server.
    2. Select the Off-line option.
    3. Click Save configuration.
  4. Extract the new Drupal Commons tarball and copy the contents into your document root.
  5. In your web browser, open http://[example]/update.php.
  6. Follow the prompts to "Update" your server.
  7. In your web browser, open http://[example]/admin/settings/performance.
  8. Click Clear cached data.
  9. Allow your visitors to access your web site by returning your site to "Online" mode:
    1. In your web browser, open http://[example]/admin/settings/site-maintenance.
    2. Select the Online option.
    3. Click Save configuration.

Drupal Commons 2.2

To upgrade your server to Drupal Commons 2.2 from an earlier version of Drupal Commons 2.x:

  1. Back up your code (everything in your Drupal root directory) and your database.
  2. Open a web browser, and then log in to your site as the main administrator account.
  3. Place the site in "Off-line" mode. This allows database updates to run without interruption, and without displaying errors to visitors of your site. To change the mode:
    1. In your web browser, open http://[example]/admin/settings/site-maintenance, where [example] is the URL of your Drupal Commons server.
    2. Select the Off-line option.
    3. Click Save configuration.
  4. Extract the new Drupal Commons tarball and copy the contents into your document root.
  5. In your web browser, open http://[example]/update.php.
  6. Follow the prompts to "Update" your server.
  7. In your web browser, open http://[example]/admin/settings/performance.
  8. Click Clear cached data.
  9. Allow your visitors to access your web site by returning your site to "Online" mode:
    1. In your web browser, open http://[example]/admin/settings/site-maintenance.
    2. Select the Online option.
    3. Click Save configuration.

Drupal Commons 2.1

To upgrade your server to Drupal Commons 2.1 from Drupal Commons 2.0:

  1. Back up your code (everything in your Drupal root directory) and your database.
  2. Open a web browser, and then log in to your site as the main administrator account.
  3. Place the site in "Off-line" mode. This allows database updates to run without interruption, and without displaying errors to visitors of your site. To change the mode:
    1. In your web browser, open http://[example]/admin/settings/site-maintenance, where [example] is the URL of your Drupal Commons server.
    2. Select the Off-line option.
    3. Click Save configuration.
  4. Extract the new Drupal Commons tarball and copy the contents into your document root.
  5. In your web browser, open http://[example]/update.php.
  6. Follow the prompts to "Update" your server.
  7. In your web browser, open http://[example]/admin/build/features/commons_core.
  8. In the list of modules to the right of the page, select the Views check box, and then click Revert components.
  9. Allow your visitors to access your web site by returning your site to "Online" mode:
    1. In your web browser, open http://[example]/admin/settings/site-maintenance.
    2. Select the Online option.
    3. Click Save configuration.

Drupal Commons 2.0

You can only upgrade to Drupal Commons 2.0 from Drupal Commons 1.7. While there were Drupal Commons beta releases and release candidates, these pre-release products do not have a developed and supported upgrade procedure.