Last updated September 19, 2012. Created by andremolnar on August 15, 2009.
Edited by NonProfit, gravelpot, bekasu, arianek. Log in to edit this page.
Backup Your Current Site
It is always highly recommended to backup your site before any update or upgrade.
A full backup consists of making copies of:
- all core Drupal files and folders
- all contributed module files and folders
- all contributed theme files and folders
- all other files and assets that have been uploaded via your Drupal site (e.g. /files folder)
- the Drupal database
For more information about backing up your Drupal site see http://drupal.org/node/22281
Update Your Site to the Latest Stable Release of Drupal 6.x
It is important for your current site to be updated to the latest stable release of Drupal 6.x prior to upgrade because point releases sometime introduce minor database schema changes. These changes will be expected to be in place by Drupal 7 when you upgrade.
For detailed information about updating your Drupal 6.x site see http://drupal.org/node/390448
Update Contributed Modules as Required
As part of the upgrade planning process you will have researched whether modules currently installed on your site will be available for Drupal 7.x.
Each module will have a slightly different upgrade path to a corresponding Drupal 7 version. In many cases you will be required to update the modules on your site to their latest versions for Drupal 6.
Visit the project page for each of module installed on your site for instructions on how to update to the latest version. Drupal 5 users who have the Update Status module installed will be provided links to the project page for each installed module, helping to identify if all of the required updates are complete. This module been added to Drupal 6 core and the Available Updates page is now found at admin/reports/updates. Also useful is the Update status advanced settings module which adds some of the functionality present in contrib that was not included in core.
Test Your Current Site After Updating and Prior to Upgrading
Part of the reason for updating your site prior to upgrade is to ensure that you have a stable foundation on which to upgrade. Test to make sure your site is still working. If everything is working as expected it is a good idea to make another backup of the newly updated site to ensure that if something should go wrong during the actual site upgrade you have a known working restore point.
Optional: Document Your Experience
If you will be updating and upgrading multiple sites, documenting any hiccups or problems you have during your update will save you time in subsequent updates and upgrades.
Comments
Use Innodb
Make sure your site is using innodb tables in MySQL - or you get a lot of errors while upgrading.
Don Robertson
Christchurch, New Zealand
don@robertson.net.nz 021 294 1542
A lot of work...
Hi,
For those who are using Drupal with multiple sites, and so, multiple DB, and who are tired to go under phpmyadmin and click on each table the operation change InnoDB, I've created an iMacro :
VERSION BUILD=7300701 RECORDER=FXSET !ERRORIGNORE NO
'
'Variable de début
SET !VAR1 1
SET !VAR2 {{!VAR1}}
ADD !VAR2 {{!LOOP}}
'
'
TAB T=1
FRAME F=2
TAG POS={{!VAR2}} TYPE=IMG ATTR=SRC:http://*/img/b_props.png
'
FRAME F=2
TAG POS=1 TYPE=A ATTR=HREF:tbl_operations.php*
'
FRAME F=2
TAG POS=1 TYPE=SELECT FORM=ACTION:tbl_operations.php ATTR=NAME:new_tbl_type CONTENT=%InnoDB
TAG POS=1 TYPE=INPUT:SUBMIT FORM=ACTION:tbl_operations.php ATTR=NAME:submitoptions&&VALUE:Go
'
TAG POS=1 TYPE=A ATTR=HREF:*db_structure.php*
Use of the macro :
You can set as VAR1 a begin variable (ie if you want to begin at the row #15...)
You use the loop function.
I maintain an updated code at the page :
http://cyberafrique.com/?q=programmation-imacros
dbtuner is a simple module
dbtuner is a simple module that can convert tables to innodb automatically - http://drupal.org/project/dbtuner
Attempting to update 6.19 to 6.22 as prep to move to D7
I have done the upgrade and am completely functional on the development site I have. However, after the update to 6.22 I have 6.19 still listed in the status report. If I run the Update Report that will tell me what is up-to-date and what is not, that report says that I have 6.22 installed and no update is available for core.
I understand others have had this problem but there is no record of them either fixing the problem or if it is a phantom problem and I can go ahead and upgrade to D 7.x.
Even with this split in version in the reports, can I go ahead and upgrade to D7.x? And should this problem be identified in your procedure as one that has to be fixed before upgrading or a problem that can be ignored?
Update Sept 2012 - I actually did do the upgrade to D7 over the top of the odd install of 6.25. It took a little work but I did get it to work. Others suggested that the site was really at the 6.25 level but there was an odd entry in the database. Wither way I did install over the top of this and it did work.