Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Using UI to create D6 to D7 migration. Files migrated in batch. So did terms. But, when I select a node (content type) migration group to Import and click "Execute", only one node is processed at a time. Even if I enter a # in the "Limit to" field, it still only processes one record then returns to migration tasks list screen. I can't think of anything about my configuration that would casue this. Help!
Comments
Comment #1
SomebodySysop CreditAttribution: SomebodySysop commentedComment #2
mikeryanI haven't heard of this before, it's hard to picture what might be causing this - can you try running the node migration in drush and see how that behaves? Any modifications to the node query?
How long does it run before returning with only one processed? This is entirely speculative, but if there's some contrib module doing something ridulously slow on node_save(), it might be that there's only time to do one item before the batch times out.
Comment #3
SomebodySysop CreditAttribution: SomebodySysop commentedYes, I did modify the node query. I added left joins and that seems to have caused the problem, as you explained in post regarding file migration here, due to multiple primary keys.
However, so far I seem to have been able to resolve the problem by adding this to the query:
$query->groupBy('n.nid');So, for the time being, the issue is fixed. At least I know the problem is caused by the query itself.
Sorry to have so many issues, but this migration thing has been quite difficult to get my arms around. But, I seem to have figured out all the major problems from my first migration attempt, so the next attempt should be a lot smoother.
Thanks!