After updating from Migrate Plus v4.0 to v4.1 the migration group list /admin/structure/migrate/manage/GROUPNAME/migrations is broken and shows a WSOD.
The log shows this error message:
Error: Call to a member function id() on boolean in .../web/modules/contrib/migrate_tools/src/Controller/MigrationListBuilder.php on line 151
#0 .../web/core/lib/Drupal/Core/Entity/EntityListBuilder.php(235): Drupal\\migrate_tools\\Controller\\MigrationListBuilder->buildRow(Object(Drupal\\migrate_plus\\Entity\\Migration)), referer: .../admin/structure/migrate
I'm using the same migration on several projects, all updated sites throw the same error. All not yet updated sites still running v4.0 do not show this error.
Comments
Comment #2
hudriPS: Downgrading back to v4.0 did not help. Drupal core was updated from v8.6.5 to v8.6.7 same time as MT upgrade v4.0 -> v4.1
Comment #3
hudriSome more tests: updated another site to core v8.6.7 and staying at Migrate Tools v4.0 --> UI still works, so I'm quite certain the issue is caused by the updade.
On the broken sites:
correctly works
results in
The "--group" option does not accept a value., but running it without the group name naturally doesn't do anything.The group parameter works on other projects still running v4.0 with the same migration.
Comment #4
hudriComment #5
hudriSorry for spamming, but confusion keeps rising: Issue is NOT caused by Migrate Tools, but by upgrading Migrate Plus v4.0 to v4.1
Downgrading Migrate Plus to v4.0 solves the issue, for both Migrate Tools v4.0 and v4.1
Not really certain how to go on now, I thought "groups" is a part of Tools and not of Plus.
Comment #6
hudriComment #7
tjpope commentedHaving the same issue with --groups
I downgraded both migrate_tools and migrate_plus and the migrations worked. Not sure exactly which one is the culprit.
Comment #8
b_sharpe commentedSame problem, with --idlist, --group, and --tag. Adding verbose doesn't provide any further information but seems like some sort of caching/discovery issue as running the command several times will make it work, but a drush cache:rebuild has no effect so not really sure where this would be coming from.
Comment #9
arnested commentedThis is a duplicate of #3024399. I added a patch for this in that issue.