Undefined variable warnings

Let's make sure there isn't some underlying cause for what you're seeing. What were the specific undefined variables you got notices for? In particular, if $type_info was giving you notices, that would mean that the node_type row for $bundle in your D6 system was missing - is it possible you deleted the content type from D6 after defining the migrations through the wizard but before running the migrations? Can you figure out what $bundle was when you got the undefined variables?

Thanks.

I'm also getting the following PHP notice using a User D6toD7 migration using just the module-provided class with arguments:

Undefined variable: revision_id File migrate_d2d/d6/d6.inc, line 40

Patch only for the misplaced code block in DrupalVersion6::getSourceValues().

I am getting the same error message multiple times after running d6 to d7 migration (users and roles only)

Undefined variable: revision_id File ... /migrate_d2d/d6/d6.inc, line 402

The errors seem to occur after 61% of the users are processed, and I must stop the import:

Processed 21 (21 created, 0 updated, 0 failed, 0 ignored) in 0.5 sec (2555/min) - done with 'JENDevelopmentRole'
Processed 723 (722 created, 0 updated, 0 failed, 1 ignored) in 215.3 sec (201/min) - continuing with 'JENDevelopmentUser'
Processed 2 (1 created, 0 updated, 0 failed, 1 ignored) in 158.2 sec (0/min) - continuing with 'JENDevelopmentUser'
Processed 2 (1 created, 0 updated, 0 failed, 1 ignored) in 158.3 sec (0/min) - continuing with 'JENDevelopmentUser'

Will this patch fix the error?

Thanks

I am also facing this error, will this have any impact on my import ?

@thermalmusic @deepesh: The patch in comment #4 should resolve this error. If you could kindly test the patch out and confirm that it does, that would help move this issue along.

Patch #4 looks simple enough and fixes the issue.

Echoing the success of the patch in #4. RTBC for sure!

RTBC

Does the warning actually matter though? Id hate to reimport all 30,000 members

@Media Crumb: if you had nothing in your 'upload' table in the source database then it shouldn't matter.

Thanks JvE!

I have experienced the same thing as #5 mentions. The patch will prevent the error message but the migration will still stall part way through. I think these are separate issues. Unless I am wrong, I see no problem with #4. I have posted about the stalling problem.

#2174173: User import stalling

Patch in #4 works nicely here. Import goes from 2 users per minute to 1,500 users per minute :)

Patch in #4 works well, and speeds up import by around 40% for me. I am looking forward for it to get committed soon.

Confirmed.

Committed, thanks.