You are here

UPGRADE.txt in Domain Access 6.2

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

Upgrade instructions for Domain Access

File

UPGRADE.txt
View source
  1. /**
  2. * @file
  3. * Upgrade instructions for Domain Access
  4. */
  5. CONTENTS
  6. --------
  7. 1. Upgrading from Drupal 6 to Drupal 7
  8. 2. Upgrading from Domain Access 6.x.1 to 6.x.2
  9. 2.1. Who Needs to Upgrade?
  10. 2.2. How to Upgrade
  11. 2.3. Error Notices
  12. 2.4. Change Summary
  13. 3. Upgrading From Drupal 5
  14. ----
  15. 1. Upgrading from Drupal 6 to Drupal 7
  16. To upgrade Domain Access from Drupal 6 to Drupal 7, you should follow
  17. Drupal's guide (found in the core UPGRADE.txt file in Drupal's root directory.)
  18. When upgrading, follow the additional steps below to ensure that the required
  19. changes for Domain Access do not interfere with Drupal's update process.
  20. -- Remove the Domain Access include line from settings.php.
  21. /**
  22. * Add the domain module setup routine.
  23. */
  24. include './sites/all/modules/domain/settings.inc';
  25. See INSTALL.txt for more information about this code.
  26. -- Update Drupal, following the process described in the core UPGRADE.txt.
  27. This step includes disabling (but not uninstalling) all Domain Access modules
  28. before you continue.
  29. -- Download Domain Access for Drupal 7.
  30. -- Run the database update script.
  31. This step will make the necessary changes that update Domain Access for
  32. Drupal 7.
  33. -- Enable the Domain Access module.
  34. -- Add the Domain Access settings line back to settings.php. Be sure to
  35. include these lines _below_ the database configuration information. (The
  36. Drupal update may place the new $databases array at the bottom of
  37. settings.php.)
  38. /**
  39. * Add the domain module setup routine.
  40. */
  41. include DRUPAL_ROOT . './sites/all/modules/domain/settings.inc';
  42. Refer to the Domain Access INSTALL.txt for information about the new syntax
  43. for the Domain Access include.
  44. -- If prompted, rebuild content access permissions.
  45. -- Enable Domain submodules (if desired).
  46. -- If using Domain Conf, check the main menu settings
  47. (admin/structure/menu/settings) which core may not have updated.
  48. You should now be ready to use your Drupal 7 site.
  49. ----
  50. 2. Upgrading from Domain Access 6.x.1 to 6.x.2
  51. If you are using Domain Access 6.x.1, you must upgrade to 6.x.2 before
  52. migrating to Drupal 7. This section outlines that upgrade process.
  53. ----
  54. 2.1 Who Needs to Upgrade?
  55. If you are using Domain Access prior to 6.x.2.0, then you should
  56. follow these upgrade instructions.
  57. Note that if you are upgrading from 6.x.1 to 7.x.2, you must first perform this
  58. update in Drupal 6.
  59. ----
  60. 2.2 How to Upgrade
  61. In previous versions, Domain Access asked you to make several
  62. changes to your site's settings.php file. The 6.x.2.0 version
  63. has made this process easier.
  64. NOTE: You must leave the Domain Access module and its child
  65. modules turned on during the upgrade process.
  66. When you first update the source code, you may see some
  67. Drupal error messages printed on screen. These are normal and
  68. will disappear after the upgrade is complete.
  69. To upgrade, follow the steps below.
  70. STEP 1: Update the module source code
  71. Replace your existing module files with the new downloaded source.
  72. STEP 2: Add new code to settings.php
  73. Add the following code to your site's settings.php file:
  74. /**
  75. * Add the domain module setup routine.
  76. */
  77. include './sites/all/modules/domain/settings.inc';
  78. See INSTALL.txt for additional information.
  79. STEP 3: Remove old code from settings.php
  80. If you have any of the following code in settings.php from eariler
  81. versions, you should remove it:
  82. /**
  83. * Add the custom_url_rewrite_outbound function.
  84. */
  85. require_once './sites/all/modules/domain/settings_custom_url.inc';
  86. /**
  87. * Add the domain_conf settings override
  88. */
  89. require_once './sites/all/modules/domain/domain_conf/settings_domain_conf.inc';
  90. /**
  91. * Add the domain_prefix tables
  92. */
  93. require_once './sites/all/modules/domain/domain_prefix/settings_domain_prefix.inc';
  94. STEP 4: Register the module updates
  95. After you have edited settings.php, log in to your Primary Domain as user 1
  96. and run the Drupal update script.
  97. The update must be run from your primary domain.
  98. STEP 5: Rebuild node access permissions
  99. After running the update script, when you return to the administration pages
  100. you will be prompted to rebuild the node access table. Click on the link or go
  101. to Admin > Content > Post settings and click the 'Rebuild Permissions' button.
  102. STEP 6: Reset permissions for domain module
  103. The old 'Content Editing Forms' setting has been replaced by role-based
  104. permissions. Please see section 3.1 of README.txt and reset your
  105. site permissions accordingly. The upgrade does not split permissions for you.
  106. There are also new permissions documented in README.txt.
  107. ----
  108. 2.3 Error Notices
  109. If your module is not configured correctly, you should see an error notice
  110. on the top of the page -- this message is shown only to users with the
  111. 'administer domains' permission. The error is also written to your site's
  112. error logs, if any.
  113. If you encounter this error, please check that you have installed or upgraded
  114. the module correctly. If the problem persists, please file a support request
  115. at http://drupal.org/project/domain.
  116. ----
  117. 2.4 Change Summary
  118. Below are some notes about the changes to the new version.
  119. -- Pre-load functions are now handled automatically.
  120. -- Domain Alias has been added.
  121. -- The old setting for 'Content editing forms' has been made a permission,
  122. so these functions can now be set per user role.
  123. -- The Primary Domain is now stored in both the {variables} and
  124. {domain} tables. Doing so allows full integration with Views and
  125. simplifies some of the core code. However, it will also force the module
  126. to skip a domain_id in the database. This change will not cause any
  127. issues, but there will be a skipped domain_id for all sites.
  128. -- Fresh installs of Domain Access will never have a domain_id of 1.
  129. -- The 'domain editor' grant has been deprecated.
  130. -- The new function domain_get_user_domains($uid) can be used
  131. to find which domains as user is assigned to.
  132. ----
  133. 3. Upgrading from Drupal 5
  134. The upgrade process should work fine when upgrading from Drupal 5 to Drupal 6.
  135. Upgrading from Drupal 5 to Drupal 7 is not supported.
  136. Best practice is to disable contributed modules when upgrading Drupal.
  137. Be sure you disable (but do not uninstall) the Domain Access module
  138. before upgrading Drupal.
  139. When you have upgraded Drupal core, you may upgrade Domain Access.
  140. Be sure to turn the Domain Access module (and its children) back on
  141. before running any Domain Access updates.