I'm attaching a patch to the UPGRADE.txt file to add the following statement in the D6->D7 upgrade instructions:

"In addition to updating to the latest available version of Drupal 6.x core,
you must also upgrade all of your contributed modules for Drupal to their
latest Drupal 6.x versions."

The instructions currently explain the need to update to the latest version of Drupal 6.x but are not explicit about the need to update to the latest version for contrib modules specifically. It is especially important to point this out for D6->D7 upgrades because many module developers are not including the D6 hook_update_N() functions for their modules in their .install files. This is happening much more frequently than it was with the D5->D6 upgrades. (It's probably happening because D7 introduced a more radical change to the database API, so module developers would have to substantially rewrite their hook_update_N() functions to get them working in D7 and are (perhaps understandably) reluctant to do so.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Sheldon Rampton’s picture

jhodgdon’s picture

Version: 7.x-dev » 8.x-dev
Status: Active » Needs work
Issue tags: +Needs backport to D7

There are changes in your patch that are not related to this fix (which I think is a good idea). Please make a patch that doesn't make the other changes (such as removing the mention of the .zip format, which we would please like to keep in there). I think that's the only one...

I also think it would be helpful to mention how you go about updating the modules? Maybe not...

And when you add a patch, please set the status to "needs review" so that both the test bot and people know it's time to review it.

And finally, this technically needs to be patched against D8 and then applied to both d8 and d7. Hmmm. The D8 upgrade guide probably needs to have its numbers updated first. Sigh.

Thanks!

drupal_was_my_past’s picture

Assigned: Unassigned » drupal_was_my_past
Status: Needs work » Needs review
FileSize
4.54 KB

Re-roll patch from #1.

jhodgdon’s picture

Status: Needs review » Needs work

Looks pretty good... One mention of 6.x crept in though:

+3. In addition to updating to the latest available version of Drupal 6.x core,
drupal_was_my_past’s picture

Status: Needs work » Needs review
FileSize
4.54 KB

Good catch @jhodgdon. Fixed in the attached patch.

jhodgdon’s picture

Status: Needs review » Reviewed & tested by the community

Looks good, thanks!

Sheldon Rampton’s picture

Of course the wording will have to be changed back to 6.x when the D8 patch is backported to D7.

Dries’s picture

Version: 8.x-dev » 7.x-dev
Status: Reviewed & tested by the community » Needs work

Committed to 8.x. Moving to 7.x-dev for backporting.

drupal_was_my_past’s picture

Status: Needs work » Needs review
FileSize
4.51 KB

Patch for 7.x.

jhodgdon’s picture

Status: Needs review » Reviewed & tested by the community

Thanks, looks ready to me!

webchick’s picture

Status: Reviewed & tested by the community » Fixed

Looks great!

Committed and pushed to 7.x. Thanks!

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

BWPanda’s picture

Assigned: drupal_was_my_past » Unassigned
Status: Closed (fixed) » Needs review
FileSize
612 bytes

While upgrading a site from 6.x to 7.x, I noticed that one of the 7.x references wasn't changed to 6.x in UPGRADE.txt. The attached patch fixes this.

jhodgdon’s picture

Status: Needs review » Fixed

Thanks for finding and fixing this error! I've committed this change to 7.x.

Automatically closed -- issue fixed for 2 weeks with no activity.