Closed (fixed)
Project:
Drupal core
Version:
8.3.x-dev
Component:
migration system
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
6 Mar 2015 at 22:49 UTC
Updated:
19 Jun 2017 at 15:05 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
claudiu.cristeaTake this too as I started with node reference.
Comment #2
claudiu.cristeaClosing in favour of #2447727: Add base class for migrating reference fields.
Comment #3
phenaproximaIn the name of sanity and scope control, we're splitting #2447727: Add base class for migrating reference fields back out into smaller issues. This is now resurrected and postponed on that.
Comment #4
phenaproximaComment #6
phenaproximaUsers must migrate
For completeness of Migrate
Gentlefolk...BEHOLD!
Comment #7
heddnSeems a re-title would be in order.
Comment #8
heddnWhat's this from?
Seems like a few stray lines here.
Comment #9
phenaproximaWell, when I manipulate the fixture, I install Drupal 6 and do what I would normally do to make the necessary modifications (i.e., standard procedure for manipulating the fixture). Whatever changes that causes, I just roll into the patch -- I try to let them come through as untouched as possible. So I'm not sure those lines are any cause for concern.
This should fix the broken tests.
Comment #10
heddnAssigning to myself to review this week.
Comment #11
heddnAll my concerns are addressed. RTBC.
Comment #12
catchDo we need to worry about the additional $original_field_type argument? Can it default to NULL - looks like it's actually optional.
Comment #13
phenaproximaNice find. This oughta do the trick!
Comment #14
heddnThis looks good. I wondered what happened with list() if there weren't enough values passed to it and if the count stuff was necessary. It is, otherwise you result in
Notice: Undefined index: 2.Comment #17
catchCommitted/pushed to 8.4.x and cherry-picked to 8.3.x. Thanks!