You are here

Home » API reference » Content Construction Kit (CCK) 6

UPGRADE.txt in Content Construction Kit (CCK) 6

Same filename and directory in other branches
  1. 5 UPGRADE.txt
  2. 6.3 UPGRADE.txt
  3. 6.2 UPGRADE.txt
================================================================
UPDATING FROM VERSION 4.7 to 6.x
================================================================

THERE IS NO DIRECT UPGRADE PATH FROM 4.7 TO 6.x!! FIRST UPGRADE
YOUR DATABASE FROM 4.7 TO THE LATEST 5.x VERSION, THEN UPGRADE
TO 6.x.

ALWAYS BACKUP YOUR DATABASE BEFORE UPGRADING!

1) While 4.7 is still installed, upload the latest 4.7 version of
   all the CCK files, go to update.php, and run all possible
   updates for the Content module and all field modules.

2) Install Drupal version 5. Once it is running, upload and install
   the latest 5.x versions of all CCK modules, go to update.php and
   run all possible updates.

3) Install Drupal version 6. Once it is running, upload and install
   the latest 6.x versions of all CCK modules, go to update.php and
   run all possible updates.

Your database should now be ready to run in CCK version 6.x

================================================================
UPDATING FROM VERSION 5.x to 6.x
================================================================

YOU MUST RUN ALL POSSIBLE UPDATES TO YOUR DATABASE IN 5.x USING 
THE LATEST 5.x CODE, BEFORE UPGRADING FROM 5.x to 6.x.

ALWAYS BACKUP YOUR DATABASE BEFORE UPGRADING!

1) Before upgrading to 6.x, upload the latest 5.x versions of all 
   CCK modules, go to update.php and run all possible updates.

2) Install Drupal version 6. Once it is running, upload and install
   the latest 6.x versions of all CCK modules, go to update.php and
   run all possible updates.

Your database should now be ready to run in CCK version 6.x

================================================================

These steps are necessary because of significant changes in the 
database structure between the 4.7 and 6.x versions. These changes
make it extremely difficult to create an automatic upgrade path that 
will work reliably in every possible situation.

File

UPGRADE.txt
View source 
  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. 3) Install Drupal version 6. Once it is running, upload and install

  21.    the latest 6.x versions of all CCK modules, go to update.php and

  22.    run all possible updates.

  23. 

  24. Your database should now be ready to run in CCK version 6.x

  25. 

  26. ================================================================

  27. UPDATING FROM VERSION 5.x to 6.x

  28. ================================================================

  29. 

  30. YOU MUST RUN ALL POSSIBLE UPDATES TO YOUR DATABASE IN 5.x USING 

  31. THE LATEST 5.x CODE, BEFORE UPGRADING FROM 5.x to 6.x.

  32. 

  33. ALWAYS BACKUP YOUR DATABASE BEFORE UPGRADING!

  34. 

  35. 1) Before upgrading to 6.x, upload the latest 5.x versions of all 

  36.    CCK modules, go to update.php and run all possible updates.

  37. 

  38. 2) Install Drupal version 6. Once it is running, upload and install

  39.    the latest 6.x versions of all CCK modules, go to update.php and

  40.    run all possible updates.

  41. 

  42. Your database should now be ready to run in CCK version 6.x

  43. 

  44. ================================================================

  45. 

  46. These steps are necessary because of significant changes in the 

  47. database structure between the 4.7 and 6.x versions. These changes

  48. make it extremely difficult to create an automatic upgrade path that 

  49. will work reliably in every possible situation.