Changes between Version 6 and Version 7 of faq/drupal/upgrade
- Timestamp:
- Mar 23, 2008, 9:25:36 PM (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
faq/drupal/upgrade
v6 v7 1 == Upgrade Drupal == 1 [[PageOutline]] 2 = Upgrading your Drupal installation at May First/People Link = 2 3 3 4 May First/People Link will ''update'' your Drupal installation for you, however, we cannot ''upgrade'' your Drupal installation. The difference between update and upgrade is: 4 5 5 * ''update'' - changing minor versions. Updates represent small changes, usually to fix bugs and security holes. In the Drupal 4 branch, examples of minor version changes are: 4.7.4 to 4.7.5. In the Drupal 5 branch, examples of minor version changes are 5.1 to 5.2. 6 7 * ''upgrade'' - an upgrade means changing between major Drupal versions. That means going from 4.6 to 4.7. Or from 4.7 to 5. Or from 5 to 6. 6 update:: 7 changing minor versions. Updates represent small changes, usually to fix bugs and security holes. In the Drupal 4 branch, examples of minor version changes are: 4.7.4 to 4.7.5. In the Drupal 5 branch, examples of minor version changes are 5.1 to 5.2. 8 upgrade:: 9 an upgrade means changing between major Drupal versions. That means going from 4.6 to 4.7. Or from 4.7 to 5. Or from 5 to 6. 8 10 9 11 Why doesn't May First/People Link do major upgrades? We would love to! However, it is a complicated process that is different for each site. In other words, we cannot automate the process, like we can for minor updates. If we upgraded everyone's Drupal web site we would have no time to do anything else! 10 12 11 If you would like to upgrade your site, here are directions for how to do that. If you are not comfortable doing this, and you are able to hire a developer to help, please [/newticket post a ticket] of the type "Project/Need to hire someone" and we will try to match you with a techie. 13 == How to upgrade == 12 14 13 ''Please note:'' If you primary host is viewsic.mayfirst.org, please add a support ticket. Upgrading Drupal on viewsic.mayfirst.org is a different process than upgrading on our other servers. In addition, these directions are for upgrading from 4.7 to 5.2. If you are running Drupal 4.6, you will first need to upgrade to 4.7 before you can follow these directions. 15 If you would like to upgrade your site, here are directions for how to do that. If you are not comfortable doing this, and you are able to hire a developer to help, please [/newticket?type=Project/Need+to+hire+someone post a ticket of the type "Project/Need to hire someone"] and we will try to match you with a techie. 16 17 ''Please note:'' If you primary host is `viewsic.mayfirst.org`, please add a support ticket. Upgrading Drupal on viewsic.mayfirst.org is a different process than upgrading on our other servers. In addition, these directions are for upgrading from 4.7 to 5.2. If you are running Drupal 4.6, you will first need to upgrade to 4.7 before you can follow these directions. 14 18 15 19 * Assemble your team. To upgrade Drupal, you will need someone who is comfortable using the command line and using secure shell (ssh). If that is not you, you may want to recruit some helpers. … … 51 55 * Test your site. Remember - your third party modules will not yet be working! 52 56 53 * One by one, add the drupal 5 version of each third party module to your modules directory ( web/sites/default/modues) and enable it via Drupal. After enabling each module, return to the update.php script to run any needed database updates.57 * One by one, add the drupal 5 version of each third party module to your modules directory (`web/sites/default/modules`) and enable it via Drupal. After enabling each module, return to the update.php script to run any needed database updates. 54 58 55 59 When you are done - report your results! Let us know how it goes. Edit this page to add new lessons learned. 56 60 61 == Gotchas == 62 === Rebuilding Permissions === 57 63 * Just learned a lesson about the upgrade process and wanted to share it. When you upgrade, you may find that "normal" users can't access your site's content even though the permissions appear to be correct. The solution is to rebuild the permissions cache, which you can find via Adminster > Content Management > Post Settings. At the top of that page, you'll see an option to rebuild permissions. Hit the button to rebuild permissions and you should find that your site content is now accessible.
