I added filefield as it's own "migrate type" so you can now import files directly into existing (or previously imported) nodes.

Comments

frankcarey’s picture

Title: Filefields as their own migrate type (allows multiple files per node) » Filefields as thier own migrate type (allows multiple files per node)
Status: Needs review » Active
Issue tags: -FileField, -migrate, -multiple files, -multivalue filefields
StatusFileSize
new5.77 KB

here is the patch. Note: adding files though the node should still work as before, it's just you can now skip that during node creation and add additional files to the node later (creating a files import map, and enabling the use of the migrate hooks.

frankcarey’s picture

Status: Active » Needs review
3dloco’s picture

Title: Filefields as thier own migrate type (allows multiple files per node) » Filefields as their own migrate type (allows multiple files per node)
Issue tags: +FileField, +migrate, +multiple files, +multivalue filefields
Alex Andrascu’s picture

Title: Filefields as thier own migrate type (allows multiple files per node) » Filefields as their own migrate type (allows multiple files per node)
Status: Active » Needs review
Issue tags: +FileField, +migrate, +multiple files, +multivalue filefields

Please clarify if we still have to do our own implementation of hook_migrate_prepare_node() for multivalue filefields and if so please provide a real world migrating example.

Thank you very much.
Alex

frankcarey’s picture

@alex_andrascu - No you don't have to use a hook, but note that the import is a different step. First you would import all of your nodes, and then create a new import for the filefield images. When you do the mappings in the settings, you need to know the NEW nid that you want to add each image to. To make that work you have to join a map table to you filefield table.

mikeryan’s picture

Status: Needs review » Closed (won't fix)

Migrate and Migrate Extras V1 are no longer supported. Migrate V2 natively supports files as a destination.