- Issue created by @awasson
I' am straggling with the same issue for weeks now and have no clue how to proceed :-(
Anny progress on this issue?- 🇨🇦Canada awasson
@thorsch, Unfortunately, I've had to move on and am migrating the long-hand way with drush migrate tools.
Acquia Migrate: Accelerate really looked great when it arrived last year but now, it seems to me that there are two issues:
1) Drupal 9 modules that Acquia Migrate: Accelerate tries to map to the Drupal 7 modules in the source site are no longer available via composer.2) Something in Context changed to make Acquia Migrate: Accelerate delete 90% of my site.
Beyond that, none of the maintainers seem to be paying attention to the issue queue. I maintain a couple of much less complex Drupal modules, so I understand the overhead of the issue queue but I can't wait so I've moved on. DrupalCon is in December this year so maybe there will be some announcements. If you can wait, it might be worthwhile.
In the meantime, there is another module to look at: https://www.drupal.org/project/migrate_wizard →
Cheers,
Andrew - 🇬🇧United Kingdom entropea
Same error. Sad to say this was a massive rabbit hole wasted two days diving into this module and sure enough this error caused the majority of content to be deleted! Even though the very pretty UI says it has imported X thousands of items, there's just 4 pieces of content showing now!
The cynic in me would be justified in thinking that releasing this module as open source, spamming the net with how to's celebrating the fact, then not maintaining the code, was simply another hook to trap users into moving to the commercial Acquia platform once they've messed up their destination sites.
Please Dries, this is not what we've come to expect from a well financed sponsor.
I am finding the same error thousands of times. The migration worked well when testing in July, I'm trying it now for real with an up-to-date source database.
I'm going to try and reproduce on an identical environment to the one I used in July. If the error is because "Something in Context changed" then hopefully by going back to the old Drupal 9 server it has a chance of working.