You are here

Home » API reference » Drupal PM (Project Management) 7.3

UPGRADE.txt in Drupal PM (Project Management) 7.3

Same filename and directory in other branches
  1. 8 UPGRADE.txt
  2. 7.2 UPGRADE.txt
UPGRADE NOTES

Currently, it is possible to upgrade directly from 7.x-1.x to 7.x-3.x.
(However, support for this may be removed in the future.)

7.x-1.x -> 7.x-2.x:

* Integration with Drupal user accounts:

  Drupal PM 7.x-2.x integrates with Drupal user accounts and no longer defines
  a PM Person content type.

* Field API:

  Drupal PM 7.x-2.x uses the Drupal Field API to define node fields, rather
  than implementing its own database storage.

* Permission changes:

  The following permissions are present in the 7.x-1.x version, but are not
  present in the 7.x-2.x version. Those permissions are obsolete because
  Drupal PM 7.x-2.x integrates with Drupal user accounts and no longer defines
  a PM Person content type.

  Project Management Person: add
  Project Management Person: delete all
  Project Management Person: delete own
  Project Management Person: delete of user organization
  Project Management Person: delete when linked to own user account
  Project Management Person: edit all
  Project Management Person: edit own
  Project Management Person: edit of user organization
  Project Management Person: view all
  Project Management Person: view own
  Project Management Person: view of user organization
  Project Management Person: view when linked to own user account

7.x-2.x - 7.x-3.x:

* Permission changes:

  The separate PM Permission module has been removed. All functionality is in
  the PM (core) module. No migration is required - permissions will be retained
  after upgrade.

File

UPGRADE.txt
View source 
  1. UPGRADE NOTES

  2. 

  3. Currently, it is possible to upgrade directly from 7.x-1.x to 7.x-3.x.

  4. (However, support for this may be removed in the future.)

  5. 

  6. 7.x-1.x -> 7.x-2.x:

  7. 

  8. * Integration with Drupal user accounts:

  9. 

  10.   Drupal PM 7.x-2.x integrates with Drupal user accounts and no longer defines

  11.   a PM Person content type.

  12. 

  13. * Field API:

  14. 

  15.   Drupal PM 7.x-2.x uses the Drupal Field API to define node fields, rather

  16.   than implementing its own database storage.

  17. 

  18. * Permission changes:

  19. 

  20.   The following permissions are present in the 7.x-1.x version, but are not

  21.   present in the 7.x-2.x version. Those permissions are obsolete because

  22.   Drupal PM 7.x-2.x integrates with Drupal user accounts and no longer defines

  23.   a PM Person content type.

  24. 

  25.   Project Management Person: add

  26.   Project Management Person: delete all

  27.   Project Management Person: delete own

  28.   Project Management Person: delete of user organization

  29.   Project Management Person: delete when linked to own user account

  30.   Project Management Person: edit all

  31.   Project Management Person: edit own

  32.   Project Management Person: edit of user organization

  33.   Project Management Person: view all

  34.   Project Management Person: view own

  35.   Project Management Person: view of user organization

  36.   Project Management Person: view when linked to own user account

  37. 

  38. 7.x-2.x - 7.x-3.x:

  39. 

  40. * Permission changes:

  41. 

  42.   The separate PM Permission module has been removed. All functionality is in

  43.   the PM (core) module. No migration is required - permissions will be retained

  44.   after upgrade.

  45.