Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.After fixing #653956: {cache_bootstrap} needs to be created in update_prepare_d7_bootstrap(), I found the following errors after upgrading a basic lorem ipsum site from D6. Attached patch fixes all but system, node, and taxonomy. system duplicates an update which was backported. node and taxonomy have field api problems. help wanted on all 3. the rest are fixed in attached patch.
There are probably more update errors lurking in modules that I did not enable in D6.
Also note that our error reporting is pretty lame. No mention of the file/line where the error occurred. Actual SQL would be helpful with SQL related errors.
And 7 theme or update.php need some better paragraph spacing on this page. hard to tell where one module ends and another begins. screenie attached
system module
Update #7031
* Failed: SQLSTATE[42000]: Syntax error or access violation: 1061 Duplicate key name 'tab_root_weight_title'
block module
Update #7000
* Failed: SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '0='weight', 1='-5' WHERE (name = 'block')' at line 1
comment module
Update #7001
* Failed: SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '0='status', 1='0' WHERE (status = '3')' at line 1
filter module
Update #7003
* Failed: SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '0='name', 1='filter_html' WHERE (module = 'filter') AND (name = '0')' at line 1
node module
Update #7006
* Failed: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'base' in 'field list'
taxonomy module
Update #7004
* Failed: Attempt to create an instance of field taxonomy_vocabulary_1 without an object type.
user module
Update #7002
* Failed: SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '0='timezone', 1=NULL WHERE (uid = '0')' at line 1
| Comment | File | Size | Author |
|---|---|---|---|
| upgrade.diff | 2.35 KB | moshe weitzman | |
| Firefox.png | 121.94 KB | moshe weitzman |
Comments
Comment #1
sunLet's commit those first.
Comment #2
webchickI committed this, but let's please not spin off yet another "fix the upgrade path" issue thread. Please coordinate at #563106: Cannot upgrade from Drupal 6 to Drupal 7 - meta issue instead.
A separate issue for "Make upgrade results more informative" though (cross-linked from the meta issue) would be great.
Comment #3
moshe weitzman commentedNow that we have have tag like 'D7 upgrade path', I'm personally less inclined to use meta issues. Views gives us an overview of all issues with same tag.
Comment #4
yched commentedIs probably caused by the node_type_get_types() or node_type_save() calls at the top of node_update_7006() (Convert body / teaser / title to fields).
For a reason I don't really get one of these stumbles on the node_type.base column.
Those calls should be removed by #553306: Make nodes have no body field by default. Remove deprecated APIs for body field, though.
Taxo error: patch in #654560: taxonomy D6 upgrade fix
Comment #5
webchick@moshe: I thought sun was suggesting using this as a meta issue to keep uploading patches to fix the upgrade path, and that makes no sense when we have a meta issue for tracking. I'm totally fine with separate issues per problem, tho. :) Makes it much easier for reviewing/committing.