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.
Greetings,
I can't get the Migrate_d2d UI to work. I've currently got migrate 7.x-2.6-rc1 enabled (also tried the latest dev releases of Migrate and Migrate D2D) and I can get the "Import from Drupal" button to display, but clicking on it gives the above error message.
Am I using the correct versions of Migrate and Migrate D2D, or is there something I'm missing in the setup?
Comments
Comment #1
reikiman CreditAttribution: reikiman commentedDitto
I simply installed the above modules, and simply clicking on the Import From Drupal button gives me the fatal error.
Comment #2
azuledu CreditAttribution: azuledu commentedSame problem here.
Comment #3
d13n CreditAttribution: d13n commentedI had the same problem, but it simply went away, when I switched the database (of the new D7 installation) from SQLite to MySQL. May be you should try this out.
HTH, Dietmar.
Comment #4
widukind CreditAttribution: widukind commentedCan't reproduce this, works for me. I'm running Drupal 7.26 with MySQL 5.5 and PHP 5.5 on Linux.
The following migrate* modules are enabled
$ drush pml --status=Enabled | grep migrate
Development UI for Drupal-to-Drupal migration (migrate_d2d_ui) Module 7.x-2.1-beta1
Migration Drupal-to-Drupal migration (migrate_d2d) Module 7.x-2.1-beta1
Migration Migrate (migrate) Module 7.x-2.6-rc1
Migration Migrate UI (migrate_ui) Module 7.x-2.6-rc1
I would start by checking that the modules listed above are enabled, and then see if and with what path the "MigrateD2DWizard" is registered in your Drupal database.
SELECT * FROM registry WHERE name = 'MigrateD2DWizard';
If the class is missing from the registry, or if the file path is not correct then I would recommend rebuilding the registry.
https://drupal.org/project/registry_rebuild
Hope this helps.
Comment #5
azuledu CreditAttribution: azuledu commentedI've found this problem using PostgreSQL database.
Comment #6
mikeryanI was able to reproduce this on a fresh Drupal install with sqlite (using drush qd). Doing either a "drush cc all" or "drush rr" fixes it, suggesting that somehow the initial module install is not resulting in the class being properly registered. But - I've verified the registry and registry_file tables are correct initially, and are not changed by the drush commands. So, somehow there's a failure to cache the registry entry for the MigrateD2DWizard class on initial install.
I can't imagine what migrate_d2d might be doing to foment this behavior - it feels like a core bug. I'm reluctant to move this to the core issue queue without digging deeper to understand why this is happening, though.
Comment #7
mikeryanComment #8
nevergone CreditAttribution: nevergone commentedThe bug is present, Drupal 7 and SQLite.
Comment #9
nevergone CreditAttribution: nevergone commentedRelated issue: #2286547: Lowercase Migrate wizard class name in hook_menu breaks Migrate UI with SQLite & PostgreSQL
Comment #10
GoldJust struck this on postgres 9.1 too. I can confirm that the suggestion to drush cc all fixes it.
Once working it can be forced back into the same broken state by clicking the Register Statically Defined Classes button on the configuration screen.
The fix nevergone mentions works for postgres too. I'm going to close this and mark as a duplicate as #2286547 has a working patch.