- πΊπΈUnited States mortona2k Seattle
The default Article content type has field_image, which is an image file field. You need to delete that before generating the migration config or else it will get confused since the field storage already exists as the wrong type.
- π«π·France erwangel
My request is a bit different but concerns the same issue: is it possible to have field_image migration to media entity as an option ? In other words, is it possible to leave image_field as image (and migrate associated items without changing the field type) and only change file(image) field to media file ?
- π³π±Netherlands ndf Amsterdam
We have a similar (or same issue) on a migration from Drupal 7 to Drupal 9.5 with media_migration 1.x-dev (of today d369908a)
Problem/Motivation
- Media entities are successfully created for image fields.
- On the node level, the
image
field remains as animage
field (typefile
) instead of being converted to amedia reference
field (typeentity_reference
). - The
image
field on the node is empty and does not reference the migrated media entities.
Expected Behavior
- The
image
field should be transformed into amedia reference
field. - The field should reference the corresponding media entities.
Steps to Reproduce
- Migrate nodes with
image
fields usingmedia_migration
. - Check the destination node fields after migration.
Proposed Resolution
Update the migration process to properly transform
image
fields intomedia reference
fields and link them to migrated media entities. - π³π±Netherlands ndf Amsterdam
Just now I tested the media_migration with a standard drupal 7 installation; and then the image field is migrated to a media field.
As expected because of the media_migration module description: "Image and file fields of the Drupal 7 source instance are migrated as media reference fields in Drupal 8|9|10."
So my case above in [3302125#comment-15866766] is a bug that happens is certain cases.