[177a560] | 1 | |
---|
| 2 | ================================================================ |
---|
| 3 | UPDATING FROM VERSION 4.7 to 6.x |
---|
| 4 | ================================================================ |
---|
| 5 | |
---|
| 6 | THERE IS NO DIRECT UPGRADE PATH FROM 4.7 TO 6.x!! FIRST UPGRADE |
---|
| 7 | YOUR DATABASE FROM 4.7 TO THE LATEST 5.x VERSION, THEN UPGRADE |
---|
| 8 | TO 6.x. |
---|
| 9 | |
---|
| 10 | ALWAYS BACKUP YOUR DATABASE BEFORE UPGRADING! |
---|
| 11 | |
---|
| 12 | 1) While 4.7 is still installed, upload the latest 4.7 version of |
---|
| 13 | all the CCK files, go to update.php, and run all possible |
---|
| 14 | updates for the Content module and all field modules. |
---|
| 15 | |
---|
| 16 | 2) Install Drupal version 5. Once it is running, upload and install |
---|
| 17 | the latest 5.x versions of all CCK modules, go to update.php and |
---|
| 18 | run all possible updates. |
---|
| 19 | |
---|
| 20 | Jump to the instructions for updating from version 5.x to 6.x. |
---|
| 21 | |
---|
| 22 | ================================================================ |
---|
| 23 | UPDATING FROM VERSION 5.x to 6.x |
---|
| 24 | ================================================================ |
---|
| 25 | |
---|
| 26 | YOU MUST RUN ALL POSSIBLE UPDATES TO YOUR DATABASE IN 5.x USING |
---|
| 27 | THE LATEST 5.x CODE, BEFORE UPGRADING FROM 5.x to 6.x. |
---|
| 28 | |
---|
| 29 | ALWAYS BACKUP YOUR DATABASE BEFORE UPGRADING! |
---|
| 30 | |
---|
| 31 | 1) Before upgrading to 6.x, upload the latest 5.x versions of all |
---|
| 32 | CCK modules, go to update.php and run all possible updates. |
---|
| 33 | |
---|
| 34 | 2) Disable all CCK modules and remove them from the modules folder |
---|
| 35 | before upgrading. |
---|
| 36 | |
---|
| 37 | 3) Install Drupal version 6. Leave all contributed modules out of |
---|
| 38 | the modules folder until core modules are up and running. |
---|
| 39 | Set your administration theme to a core theme like Garland until |
---|
| 40 | everything has been updated to help ensure you don't encounter |
---|
| 41 | theme-related problems accessing the administration area. |
---|
| 42 | |
---|
| 43 | 4) Once core is running, upload and install the latest 6.x versions |
---|
| 44 | of ONLY CCK CORE FILES (the ones in the tarball on the CCK |
---|
| 45 | project page). Enable them, then go to update.php and run all |
---|
| 46 | possible updates. DO NOT add any other CCK modules to the |
---|
| 47 | modules folder until the core CCK files are updated and working |
---|
| 48 | correctly. |
---|
| 49 | |
---|
| 50 | 5) After updating CCK core modules, you may get messages saying that |
---|
| 51 | some updates failed and that you need to run update.php again. |
---|
| 52 | If you get messages like that, keep re-running update.php until |
---|
| 53 | you get no more messages. |
---|
| 54 | |
---|
| 55 | 6) Once the core CCK modules are updated and working correctly, |
---|
| 56 | add other CCK modules to the modules folder, enable them, |
---|
| 57 | and run update.php. For best results, do this one module at a |
---|
| 58 | time so you can tell immediately if any of them create problems |
---|
| 59 | without letting those problems interfere with other updates. |
---|
| 60 | |
---|
| 61 | |
---|
| 62 | Your database should now be ready to run in CCK version 6.x |
---|
| 63 | |
---|
| 64 | ================================================================ |
---|
| 65 | |
---|
| 66 | The 4.7 to 5.x steps are necessary because of significant changes |
---|
| 67 | in the database structure between the 4.7 and 6.x versions. These changes |
---|
| 68 | make it extremely difficult to create an automatic upgrade path that |
---|
| 69 | will work reliably in every possible situation. |
---|
| 70 | |
---|
| 71 | The extra steps in the 5.x to 6.x upgrade are because all modules |
---|
| 72 | in the modules folder are automatically updated in Drupal 6, even if they |
---|
| 73 | are not enabled. That means that modules that rely on core CCK may try |
---|
| 74 | to run their updates even if core CCK is not enabled, and contributed |
---|
| 75 | CCK modules that have broken updates will have their broken updates |
---|
| 76 | run even if they are not enabled. |
---|
| 77 | |
---|
| 78 | A number of updates are dependent on other updates and won't work |
---|
| 79 | until previous updates are finished or specific modules are enabled, |
---|
| 80 | so you may get messages that other modules need to be enabled or that |
---|
| 81 | update.php needs to be re-run, and you need to follow those instructions |
---|
| 82 | until all the updates complete. |
---|
| 83 | |
---|
| 84 | Taking extra time during the upgrade by leaving modules out of the |
---|
| 85 | modules folder altogether until you are ready to enable and update them |
---|
| 86 | should reduce or eliminate update problems. |
---|