Adding migrate module support to this module can be very useful in our daily work with migration projects that want to use video embed fields.

#1 migrate-support-2007194-1.patch1.84 KBrvilar
Members fund testing for the Drupal project. Drupal Association Learn more


rvilar’s picture

Status: Active » Needs review
1.84 KB

I wrote the code to enable support and is working in some of our projects.

daveparrish’s picture

Status: Needs review » Reviewed & tested by the community

Patch applied cleanly and works fine.

I also went ahead and created a module for anyone needing this functionality but not wanting to apply the patch.

plopesc’s picture

Issue summary: View changes
Status: Reviewed & tested by the community » Fixed

Patch committed! 8f6de9e

Thank you very much rvilar!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

wonder95’s picture

I can second @tannerjfco's experience in #2318077: Issues with Migrate Field Handler, in that mapping to the :video_url subfield imports nothing, but if I import to my video field without the subfield:

$this->addFieldMapping('field_video', 'my_video_url');

as compared to

$this->addFieldMapping('field_video:video_url', 'my_video_url');

where the my_video_url source field is a custom value generated in prepareRow(), is it works just fine.

In running through the prepare() function for the handler, my mapped value comes in in $values['arguments'], and once that gets unset, there's nothing left in $values, so FALSE is returned. Any chance someone could give an example of how this is supposed to be used, if not just as a straight mapping like I showed above?


wonder95’s picture

Status: Closed (fixed) » Active