[Summary view] [Print] [Text view]

   1  $Id: UPGRADE.txt,v 1.4 2007/11/13 01:28:13 dww Exp $
   2  
   3  ======================================================================
   4  This file contains specific instructions for upgrading your site's
   5  version of project_issue.module to a new release.  You should always
   6  check this file when you download a new version to see if there are
   7  any specific things you need to know about a certain upgrade.
   8  ======================================================================
   9  
  10  
  11  --------------------------------------------------
  12  Upgrading to 4.7.x-2.* (from the 4.7.x-1.* series)
  13  --------------------------------------------------
  14  
  15    The 4.7.x-2.* versions of project and project_issue must be upgraded
  16  at the same time.  For example, you cannot run project_issue version
  17  4.7.x-2.* with project version 4.7.x-1.*.  Therefore, if you are
  18  considering upgrading a 4.7.x-1.* installation of project_issue to
  19  4.7.x-2.*, please consult modules/project/UPGRADE.txt.
  20  
  21  
  22  ------------------------------------------------------------
  23  Upgrading to 5.x-2.* (from the 4.7.x-2.* and 5.x-1.* series)
  24  ------------------------------------------------------------
  25  
  26    The 5.x-2.* version of project_issue has three new module depencencies:
  27      1. Drupal core's Comment module
  28      2. Drupal core's Upload module.
  29      3. Comment upload module -- http://drupal.org/project/comment_upload
  30  
  31    These modules must be installed and enabled BEFORE you attempt to
  32    upgrade to 5.x-2.*.
  33  
  34    Unfortunately, Drupal core currently has a bug that prevents you from
  35    enabling a module when another module adds new module dependencies. So,
  36    if any of the three modules above were not already installed and
  37    enabled on your site prior to this upgrade, there's a bit of extra work
  38    involved:
  39  
  40      1. Go to the module administration page. If Comment module is not
  41         enabled, then uncheck the 'Enabled' checkbox for any modules on 
  42         which Comment module depends (this is listed in the 'Depends on:'
  43         section -- Project issue tracker will be one of these).
  44      2. Repeat step #1 for the Upload and Comment upload modules.
  45      3. Submit the module administration form.
  46      4. Check the 'Enabled' checkbox for all the modules that you disabled,
  47         and for the Comment/Upload/Comment upload modules.
  48      5. Submit the module administration form.
  49  
  50    If you try to upgrade without the new dependencies enabled, the
  51    upgrade will fail gracefully.  If this happens to you:
  52  
  53      1. Follow the instructions above to get the dependencies resolved.
  54      2. Go back to http://yoursite.com/update.php
  55      3. Click on 'run the database upgrade script'.
  56      4. Click on 'Select versions'.
  57      5. For the 'project_issue module' select box, select update 5200.
  58      6. Click on 'Update'.
  59  
  60    NEW SETUP FOR ISSUE EMAILS
  61  
  62    In the past, the "From" address of all project issue e-mail
  63    notifications was the address entered by the project owner in the
  64    "Project e-mail" field on the project's settings page. This created
  65    a privacy problem, because unbeknownst to them, their e-mail address
  66    was being revealed to other users subscribed to their issue queue
  67    e-mails.
  68  
  69    To correct this issue, all project issue e-mails now have a global
  70    "From" address.  This defaults to the global site e-mail, but can be
  71    customized using the "Reply-to address on e-mail notifications"
  72    setting on the Project issue settings page
  73    (admin/project/project-issue-settings).
  74