If you are migrating filefield or imagefield fields from drupal 6 to drupal 8, the migration doesn't require that the d6_file migration is completed in advance. The impact of this is that file references create random file stubs due to the file entity not being found as it hasn't yet been migrated, or hasn't been fully completed.
Suggested solution
Clearly the d6_node builder needs to inject a required dependency into the migration configuration if the migration contains a File or Image field. This could easily be hardcoded, but may be better to add new method to the cckPluginBase class called getDependencies which could then be used by cck plugins to define additional dependencies. This method would then be called by d6_node builder to dynamically add the required dependencies. This would then allow custom cck plugins to define their own dependencies.
Alternatively, you could use the existing processCckFieldValues method on the d6_cck_file cck plugin, and inject the dependencies here, however this method is a little less elegant,
Comments
Comment #2
quietone commentedComment #3
quietone commentedComment #9
heddnI think this is now resolved.
d6_field_filenow listsd6_fileas a dependency. And core's migrate drupal ui runs things in the right order. Also, I'm pretty sure migrate_upgrade adds dependencies for all migration lookups. So the drush side of things should also be resolved.