[Summary view] [Print] [Text view]

   1  $Id: UPGRADE.txt,v 1.5 2009/01/12 20:07:19 dww Exp $
   2  
   3  ======================================================================
   4  This file contains specific instructions for upgrading your site's
   5  version of project.module to a new release.  You should always check
   6  this file when you download a new version to see if there are any
   7  specific things you need to know about a certain upgrade.
   8  ======================================================================
   9  
  10  --------------------------------------------------
  11  Upgrading to 6.x-1.* (from 5.x)
  12  --------------------------------------------------
  13    Before upgrading to the Drupal 6 version of the project and/or project
  14  release modules, you *must* first upgrade to the most recent official release
  15  of the project module.
  16  
  17    The Drupal 6 version of the project module now uses the Views module for
  18  project browsing.  To use Views, many aspects of how the project browsing
  19  works had to be changed.
  20  
  21    * Access to the project browsing views is based on a new permission
  22      called 'browse project listing'.  You will likely want to give this
  23      permission to all roles that currently have one or more of the following
  24      permissions:
  25        'access projects', 'access own projects', 'administer projects'.
  26  
  27  --------------------------------------------------
  28  Upgrading to 5.x-1.1 (from 5.x-1.0)
  29  --------------------------------------------------
  30  
  31    The 'Project e-mail' setting on the project edit page has been
  32  removed due to a number of problems.  This setting was only used for
  33  Project issue tracking, so it didn't belong here in any case.
  34  Therefore, database update #5001 drops this column from the
  35  {project_projects} database table where it is stored.  If you happen
  36  to want to save this data for some reason, you should save it into a
  37  separate table before you upgrade to 5.x-1.1 and run update.php.  For
  38  more information, please see the UPGRADE.txt file in the project_issue
  39  directory, and read the following issues:
  40  - http://drupal.org/node/36619
  41  - http://drupal.org/node/189210
  42  
  43  
  44  --------------------------------------------------
  45  Upgrading to 5.x-1.* (from 4.7.x-*)
  46  --------------------------------------------------
  47  
  48    If your site is currently running 4.7.x-1.*, you will have the same
  49  complications upgrading directly to 5.x-1.* as you would upgrading to
  50  4.7.x-2.*.  Therefore, please read the instructions for upgrading to
  51  4.7.x-2.* below.  You can still upgrade directly from 4.7.x-1.* to
  52  5.x-1.*, but if your site makes use of releases, you will have to
  53  follow the instructions at http://drupal.org/node/163616.
  54  
  55    If your site is currently running 4.7.x-2.*, upgrading to 5.x-1.* is
  56  very simple.  In this case, the normal upgrade procedure should be
  57  followed, see http://drupal.org/upgrade for details instructions.
  58  Basically:
  59  
  60    1) Backup your site and database.
  61    2) Disable all of your project-related modules (project,
  62       project_issue, project_release, etc) -- in fact, it's safest to
  63       disable all contrib modules before upgrading to a new core series.
  64    3) Upgrade core to the latest 5.* release.
  65    4) Install the latest 5.x-1.* release of project and project_issue.
  66    5) Re-enable project, project_issue (and optionally, project_release).
  67    6) Re-run update.php for changes to the project-related DB schema.
  68  
  69  
  70  --------------------------------------------------
  71  Upgrading to 4.7.x-2.* (from the 4.7.x-1.* series)
  72  --------------------------------------------------
  73  
  74    During the 4.7.x development of the project modules, a fundamental
  75  change was made to the code, which resulted in the split between the
  76  4.7.x-1.* and 4.7.x-2.* versions.  Previously, project releases were
  77  represented via a special table in the database, and all of their
  78  behavior was hard-coded into the project.module.  Starting with the
  79  4.7.x-2.* series, project releases are now represented by release
  80  nodes (see http://drupal.org/node/94000 for more information).
  81  
  82    To see if your site is affected, you should run the following query:
  83  
  84       "SELECT COUNT(*) FROM project_releases;"
  85  
  86       (This assumes your site is not using any table prefixing, alter
  87       the table name with your site's table prefix if needed).
  88  
  89    If your {project_releases} table is empty, your 4.7.x-1.* or earlier
  90  site does not use releases and upgrading to the 4.7.x-2.* series is
  91  quite easy.  In this case, the normal upgrade procedure should be
  92  followed, see http://drupal.org/upgrade for details instructions.
  93  Basically:
  94  
  95    1) Backup your site and database.
  96    2) Install the latest 4.7.x-2.* release of project and project_issue.
  97    3) Run update.php.
  98  
  99    (Please note that the 4.7.x-2.* versions of project and project_issue
 100  must be upgraded at the same time.  For example, you cannot run
 101  project version 4.7.x-2.* with project_issue version 4.7.x-1.*).
 102  
 103    However, if your {project_releases} table has records, you are using
 104  the old releases system, and upgrading your site will be a somewhat
 105  difficult process.  In that case, you should view the following
 106  handbook page on drupal.org *BEFORE* you start upgrading:
 107  
 108    http://drupal.org/node/163616
 109