After migrating a site from 5.16 to 6.10, I had to run update.php manually. The task log shows that some of the update code did run, but only some db schema changes.
Here is what was done:
ALTER TABLE {cache} ADD `serialized` SMALLINT NOT NULL DEFAULT 0
ALTER TABLE {cache_filter} ADD `serialized` SMALLINT NOT NULL DEFAULT 0
ALTER TABLE {cache_page} ADD `serialized` SMALLINT NOT NULL DEFAULT 0
ALTER TABLE {cache_menu} ADD `serialized` SMALLINT NOT NULL DEFAULT 0
ALTER TABLE {system} ADD `info` TEXT DEFAULT NULL
ALTER TABLE {system} ADD `owner` VARCHAR(255) NOT NULL DEFAULT ''
ALTER TABLE {locales_target} ADD `language` VARCHAR(12) NOT NULL DEFAULT ''
ALTER TABLE {locales_source} ADD `textgroup` VARCHAR(255) NOT NULL DEFAULT 'default'
ALTER TABLE {locales_source} ADD `version` VARCHAR(20) NOT NULL DEFAULT 'none'
CREATE TABLE {cache_block} ( `cid` VARCHAR(255) NOT NULL DEFAULT '... (Expand)CREATE TABLE {cache_block} ( `cid` VARCHAR(255) NOT NULL DEFAULT '', `data` LONGBLOB DEFAULT NULL, `expire` INT NOT NULL DEFAULT 0, `created` INT NOT NULL DEFAULT 0, `headers` TEXT DEFAULT NULL, `serialized` SMALLINT NOT NULL DEFAULT 0, PRIMARY KEY (cid), INDEX expire (expire) ) /*!40100 DEFAULT CHARACTER SET UTF8 */
UPDATE {system} SET status = 0 WHERE name IN ('watchdog')
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | possible_update_fix.diff | 2.36 KB | adrian |
| #2 | possible_update_fix.diff | 205 bytes | adrian |
Comments
Comment #1
anarcat commentedComment #2
adrian commentedHeres a possible fix.
Please test.
Comment #3
adrian commentedoops
Comment #4
mathieu commented(after irc chat involving adrian & anarcat) ... Problem appears to be that 'batch' isn't installed (not part of the $modules array) and is necessary for the rest to happen.
The batch table is not created as part of the system module update - we need to call update_create_batch_table(); (after including update.php) to do it. Doing this, though, is not sufficient to fix this bug. :-(
Comment #5
adrian commentedI fixed this in the patches here : http://drupal.org/node/411822
it's all part of the crazy bootstrap issues with drush and drupal, so once the drush patch is in, the fix will go into provision/hosting.
this is also a duplicate of http://drupal.org/node/408810