As of today, 4 Nov 2014, I have latest versions of D6, D8 and Migrate Upgrade. I generated some dummy content, users, vocabularies/terms in D6 site using Devel module. D6 site is plain Drupal site with some dummy content.
Now when I am migrating D6 site to D8, using Migrate Upgrade module, I am getting following fatal error,
An AJAX HTTP error occurred.
HTTP Result Code: 200
Debugging information follows.
Path: /batch?id=2&op=do_nojs&op=do
StatusText: OK
ResponseText:
Fatal error: Call to a member function getConfigDependencyName() on a non-object in core/lib/Drupal/Core/Field/FieldConfigBase.php on line 252
I noticed that vocabularies and terms are migrated from D6 site. Any ideas?
Comments
Comment #1
Anonymous (not verified) commentedIt may be possible that the system detected something in the site that is not enabled in D8, and then tried to migrate it into something that isn't there yet. Check the "Extend" page and compare to D6 site to see if there is something obvious there. Hopefully we can get a patch in over the next few days if it is that issue...
Comment #2
amitgoyal commentedI disabled almost all of the unwanted modules in D6 site and enabled almost all the modules in D8 site. But I am still getting the same issue.
Comment #3
Anonymous (not verified) commentedI just ran it myself without any issues. Are you using the latest version of core from git? Or are you using a beta? Or the imp sandbox?
The migrate_upgrade I'm using is checked out from git. I haven't tried the nightly build but one of my other projects has a packaging error so I figured I should ask...
Comment #4
Anonymous (not verified) commentedI'm getting the same error now. I have a potential workaround that causes some different errors but it does complete, so I'm going to keep on it tomorrow while I'm at BADcamp sprinting.
Comment #5
amitgoyal commentedYes, I have latest versions from GIT D6, D8 and Migrate Upgrade.
Now I re-installed both the sites. Generated only 10 users using Devel in D6. Migration again failed with following error,
Comment #6
amitgoyal commentedRegarding #5,
When I looked into the migrate_upgrade code, I noticed that it does the migration based on migrate.config.yml and migrate.content.yml files. As 'book' plugin was disabled on default install of both the sites, it gave the error (#5).
I commented out 'd6_book' and other stuff except 'd6_user' in migrate.content.yml file and migration worked perfectly fine for 'users' as I am trying the migration for one entity at a time.
Comment #7
amitgoyal commentedComment #8
benjy commentedAll d6 to d8 migration issues should be in the core issue queue now.
Comment #9
Anonymous (not verified) commentedInteresting. I was planning to make a patch to migrate_upgrade to at least report the error but was having trouble figuring out how to fail the migration from calculateDependencies. Is it still worth catching the issue in the UI? I suspect it is... in which case I can create a new issue to deal with that.
Comment #10
benjy commentedNot sure what the exact error is here because much of the mentioned errors are related to the UI and not the migration itself but the book errors could be fixed in #2346039: Add missing migrations to MigrateDrupal6Test and fix the result
Comment #11
amitgoyal commentedNot sure why is the Fatal Error related to the UI and not the migration itself. I am still getting the same fatal error when I run it from command line,
drush migrate-manifest manifest.yml --legacy-db-url=mysql://drupaluser:@127.0.0.1:33067/d6I have taken the manifest file from https://www.drupal.org/files/issues/D6Manifest-Complete.yml.
Comment #12
amitgoyal commentedAttaching here complete migration log from the command line.
Taxonomies and users are migrated along with site settings. But I am still not able to migrate nodes.
Comment #13
chx commentedWe have seen this before when someone had forum at one point and it was disabled in D8.
Comment #14
amitgoyal commentedI updated the D8 code through GIT, reinstalled D8 site and then enabled almost al the modules in D8. Even then I am getting the same error "Fatal error: Call to a member function getConfigDependencyName() on a non-object in /d8/core/lib/Drupal/Core/Field/FieldConfigBase.php on line 252".
Comment #15
Anonymous (not verified) commentedA temporary solution to this is to completely uninstall the module in D6 that is causing the migration to fail. Simply disabling it does not stop D8 from trying to migrate the content.
Alternatively, as I suggested above, consider enabling the D8 module(s) that are missing so that the source data has a target to migrate into.
Lastly, you could use a custom manifest file to simply not run the problematic migration.
Eventually the code will deal with this situation a bit more elegantly...
Comment #16
benjy commentedWould be good if these errors could be re-tested and the IS updated now that #2374339: FieldConfigBase::calculateDependencies() fatal error is unhelpful is in. Should give us some more context.
Comment #17
amitgoyal commentedI tried it again. I updated my D8 code through GIT. Re-installed my D8 site and then enabled all the modules.
I ran the migration using Migration Upgrade module and got the following error,
Comment #18
benjy commentedHow annoying, the error is going from a difference place. I've opened a new issue: #2383079: EntityDisplayBase::calculateDependencies() fatal error is unhelpful
Comment #19
jhedstromGiven #18, is this still an issue?
Comment #20
amitgoyal commentedFinally there were no Fatal errors!
As usual, I did git pull for both D8 and Migrate Upgrade module. Reinstalled D8 site and enabled most of the modules. Performed D6 to D8 migration using Migrate Upgrade module.
During migration it reported some missing bundles but no fatal errors. I checked and found that Users / Vocabularies / Terms have been migrated successfully. Migration also created Page and Story content types but both were having just one field called Body. I think that's the reason no content and comments have been migrated.
Although there are no fatal errors now but I am still not able migrate the content.
Comment #21
benjy commentedI think this error was fixed as mentioned in #18. If you have other problems, please open a new issue.