Closed (fixed)
Project:
Drupal core
Version:
8.2.x-dev
Component:
migration system
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
23 Feb 2016 at 16:56 UTC
Updated:
11 Oct 2016 at 11:54 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
jofitzAdd d7_field_instance to the migration dependencies of d7_user.
Comment #3
quietone commentedComment #4
benjy commentedCan we add a couple of tests here please.
Comment #6
jofitzChecked with v8.1.1.
Comment #7
jofitz@benjy I'm not sure how to add tests for this seeing as migrations and their ordering is hard-coded in functional tests. I cannot think of a test that will fail without this patch and then pass with it. Any suggestions?
(Also version corrected)
Comment #8
benjy commentedCould we add some assertions to
\Drupal\Tests\user\Kernel\Migrate\d7\MigrateUserTestfor some of the user field data?Comment #9
jofitzAdded tests to MigrateUserTest.
N.B. Test user language changed from '' (empty string) to 'en' because fields (with a language) cannot be associated with users without a language (see #2671312: No default value for User langcode when migrating D7 users with no language: No default value for User langcode when migrating D7 users with no language).
(now has a lot of code in common with #2673960: Unable to migrate D7 User cck fields, unsurprisingly)
Comment #10
hussainwebI see this issue was created 5 months ago and it might not be working then but I can't get it to reproduce right now. I downloaded the latest 8.2.x, enabled a few basic modules, and migrated from my D7 site which has two fields on user. They did get migrated the first time:
The field instance settings didn't get migrated but that's handled in another issue - #2675470: D7 field instance settings for any fields not on nodes are not migrating. The tests in here could be useful but I think there are identical tests in many other issues.
Comment #13
mikeryan@hussainweb - the OP may be a bit ambiguous - the fields and their instances do get created on migration, but after the users are migrated, thus the field *content* is not populated on users. I've reproduced this locally.
Comment #14
jofitzClarification of title and summary.
In process of re-rolling.
Comment #15
jofitzRe-rolled.
Comment #17
jofitzResolve test failure.
Comment #19
mikeryanI'm amused by this, given the actual fix is 1 line...
Anyway, looks good to me, RTBC, thanks!
Comment #22
catchCommitted/pushed to 8.3.x and 8.2.x, thanks!
Also retrospectively bumping to major and 'migrate critical' since this would result in data loss for a one-hit migration via the UI.