Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.When upgrading a site from Drupal 6, the comment module can fail on update hook 7002 because the comment table may have already been renamed from D6's 'comments' to D7's 'comment' once before, and any attempt to re-run the upgrade process will fail at the first line of this hook, essentially skipping several really important things.
The attached patch checks for the existence of an old table named 'comments' before safely attempting a table re-name to 'comment'.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | 1462144_comment_safely_rename_table.patch | 558 bytes | senpai |
Comments
Comment #1
senpai commentedAttaching the patch.
Comment #3
senpai commentedWoops. Changing from 8.x-dev to 7.x-dev.
Comment #4
senpai commented#1: 1462144_comment_safely_rename_table.patch queued for re-testing.
Comment #5
vthirteen commentedit worked for me!
Comment #6
senpai commentedI guess this isn't really a minor issue, because it prevents a D6 to D7 upgrade if *anything* else caused the update.php to need a second run-through.
Comment #7
catchUpdates aren't re-entrant, you need to start over with a fresh database every time.
Bad enough trying to get it working running them once.
Comment #8
off commentedwork correctly