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.I was playing with Migration using the Migration Extras Profile2 example. To register the the example, I have to click the Register button on /admin/content/migrate/registration. The following log error occured:
MigrateException: Failure to sort migration list - most likely due to circular dependencies involving OgMigrateContent,OgMigrateUser,OgUiMigrateAddField,OgUiSetRoles in migrate_migrations() (line 80 of E:\Robert\My Documents\MyWork\drupaldesigns.dev\public_html\sites\all\modules\migrate\migrate.module).
The only way to get the Migration UI working again is to delete the entries in the migrate_status database table.
I then simply disabled the Profile2 migration example, and clicked the Register button again. OG is the only module in my install that is using Migration.
This issue makes it impossible to Register other migration modules.
Comments
Comment #1
adiatisSame problem here! Also in rc3!
This is critical to migrate module.
Comment #2
amitaibuUsing the "Register" button is wrong. OG is compatible with Migrate 2.5, and will auto-register the migrations needed for your installation.
Comment #3
rbruhn CreditAttribution: rbruhn commented@Amitaibu - I think you misunderstand. I was NOT trying to register OG, this error happens when trying to register other modules. Basically, you can't because something is wrong in OG.
Comment #4
amitaibuYes, I understood you. The "other modules" seem not to be Migrate 2.5 compatible forcing you to manually register it. I consider it to be a wrong behavior -- your modules should be updated to work Migrate 2.5.
How about adding this info in OG's docs? :)
Comment #5
rbruhn CreditAttribution: rbruhn commented@Amitaibu - I see. So Profile2 actually needs to update their module. As posted on the Migrate project:
IMPORTANT: Automatic registration of new migration classes is no longer done on a cache clear. Depending on automatic registration is now deprecated, and you are encouraged to implement your migrations as DynamicMigration and explicitly register them via hook_migrate_api() or MigrationBase::registerMigration().I added a reference on the OG Docs page to point here if people are looking for the reason.
Thanks :)