Upgrade scripts from D6 to D7 [#1072082]

As the module is already in beta, we need to complete and test upgrade scripts before we can have a release candidate.

Notes:
- As some modules have been renamed there's a variable 'i18n_drupal6_update' that is set by i18n module only when upgrading so other sub-modules can know that we are upgrading.
- For each module hook_update_7000() is reserved for D6 to D7 upgrades.
- We need to focus on needed updates affecting large datasets (i.e. all taxonomy terms.). Configuration will need to be reviewed manually anyway so no need to upgrade each variable.

Comments

Comment #1

cpelham commented 30 April 2011 at 18:18

Issue tags:

-d7upgrade

+d7upgrade cck fields

In D7 a language row is added to field tables There needs to be some logic somewhere that checks the language of each node and then adds that language value to the language row of each corresponding field attached to the node, or they do not work properly. Am I understanding this correctly?

Will this module eventually handle upgrading of multilingual nodes with cck fields? The D7 CCK module does not handle this, and Karen has said that she doesn't normally work with multi-lingual sites and is not familiar with the upgrade requirements. CCK Migrate leaves this set as 'und' for undefined which is not good. When you click edit the field form will be blank if the language value is undefined, and this seems to also screw up views calling those nodes/fields.

Comment #2

jose reyero commented 1 May 2011 at 17:43

About node/fields language, I think cck should do the same as core upgrade scripts, which is setting the field language to the node language.

Comment #3

cpelham commented 11 May 2011 at 02:19

Karen added a patch to CCK to accomplish this. I have not had a chance to test but will do so as soon as I get a chance. For those following this, download the latest CCK 7-dev and give it a shot (which means upgrading some fields from D6 to D7 with the migrate fields tool supplied by D7 CCK).