Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.I'm trying to migrate a site in Drupal 6 to Drupal 7. I have installed Migrate, Migrate Extras and Drupal to Drupal Migrate modules. I use the UI wizard to mapping the fields. All is ok, but the multivalue fields (text fields with mutlivalue, link fields with multivalue, nodereference fields with multivalue and image fields with multivalue) don't work. Never. When try to migrate the nodes, the multivalue fields don's pass. I search in the Migrate Issues the solution but without luck, i try to install a lot of patchs, but nothing…
I've tried everything and no way ...
Does anyone know how to migrate multivalue fields?
What I have to do to make it work?
Barry Collins
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | single-image-migrate.png | 40.7 KB | dcine |
| #4 | multivalue-images.png | 45.35 KB | dcine |
Comments
Comment #1
dcine CreditAttribution: dcine commentedComment #2
dcine CreditAttribution: dcine commentedOk, the error is solved by installing the latest version of the module (Migrate 2.8 beta 1) but only partially. Let me explain:
The "Multi-valued text fields" now migrate smoothly, but the "image multivalued fields" does not, are still not working. I get only migrate the image fields that contain a single value.
Can someone help me out?
Comment #3
mikeryanHow did you set up the image field mappings in the UI? Maybe a screenshot of those mappings would help...
Comment #4
dcine CreditAttribution: dcine commentedOk, thanks for your help. This is a screenshot of my mappings.
In the picture you can see what I have set. Basically I'm using "MigrateFileFid" to migrate images:
I can migrate the image fields when the field is single image field, when is a multivalued field, not.
Could you help me (Please!)?
Comment #5
mikeryanI'm not sure why it would have this effect, but you shouldn't set the source migration on the file_class mapping.
This may seem obvious, but just to double-check - the image field on the destination side is configured to have multiple values, right?
Comment #6
dcine CreditAttribution: dcine commentedYes It is an exact copy of the field, it is a multivalue field.
This is an example of how I set up another field image of a single image that works:
Do you know why it might be failing?
Could you help me (Please!)?
Comment #7
mikeryanWhen replying to an issue marked "Postponed (maintainer needs more info)" be sure to reset the status to Active for more visibility.
Comment #8
dcine CreditAttribution: dcine commentedOk, sorry I did not know very well the functioning of issues.
Comment #9
mikeryanWell, this used to work for me but doesn't now - wondering if #2466405: Illegal string offset 'alt' broke it. @dcine, what version of migrate_d2d are you using - the last supported release, or the -dev?
Comment #11
mikeryanOK, committed a fix. @dcine, once the -dev is updated you can try it out (or if you can't wait, downgrade to migrate_d2d 2.1).
Comment #12
dcine CreditAttribution: dcine commentedSorry, I installed the new version of the module (7.x-2.1 + 6-dev) and it does not work (for my setup). Still the same.
I only need migrate this field to finish the migration.
Could you help me (please!)?
Comment #13
mikeryanSorry, I have no other ideas (other than downgrading to the 2.1 release?).
Comment #14
dcine CreditAttribution: dcine commentedI downgraded to 2.1 and…nothing, it fails again…
Does anyone know how to fix this (Please!)?
Comment #15
dcine CreditAttribution: dcine commentedOk, After trying again and again, at the end I reinstalled all modules of "Migrate" in its latest version, and now it works. I can migrate smoothly and all images. The problem now is different, but I've already made the question in another message ...
Thanks! for the help and I hope that my issue can help others to find solutions.