Open leeomara opened 1 week ago
As a workaround, I'll try to rollback the yukon_migrate_url_alias_node
migration and re-run it again.
As a workaround, running this on UAT:
drush migrate:rollback yukon_migrate_url_alias_node
and then
drush migrate:import --group=legacy_url_alias --continue-on-failure
created 52997 items.
w3creatives suggested that d10-queries.sql should truncate the migrate_map_yukon_migrate_url_alias_node
table.
TRUNCATE migrate_map_yukon_migrate_url_alias_node;
Tested this on dev and it worked well.
When going through the steps defined in the README, the
migration_complete_w3.sh
script migration doesn't migrate (this runs theyukon_migrate_url_alias_node
migration).When run (either on it's own, as part of a group, or through
migration_complete_w3.sh
), it doesn't create or update any records.Output typically looks like:
When I compare with
migrate:status
, the same migration shows many records to process.