- Issue created by @xurizaemon
- 🇳🇿New Zealand ericgsmith
I support introducing a
no_prophecize
configuration option for the media_wysiwyg_filter process plugin.
If a D7 source DB contains a content reference to a file (eg [[{"fid": "549","view_mode": "wysiwyg","fields": {"format": "wysiwyg","field_whatever[und][0][value]": "whatever"},"link_text": null,"type": "media"}]]
) where the file has been deleted from the source DB, Media Migration may "prophecise" a UUID for a Media entity which will never exist, and output a <drupal-media>
embed which points to a UUID which will never be created.
This can be complicated to debug as the Media ID and UUID are unlikely to match the D7 File ID.
A better behaviour might be to signal to the migration developer or content reviewer that the content reference points to an invalid file.
[[{"fid": "549","type":"media"}]]
or similarWhen executed, the migrated content will contain <drupal-media>
with a UUID which does not relate to any Media in the destination system.
Provide configuration to Media Migrate processing which makes it optional to either:
I confess I haven't fully wrapped my head around the purpose of the oracle prophecising UUIDs here, so my proposed solution is a bit speculative!
Active
1.0
Documentation
I support introducing a no_prophecize
configuration option for the media_wysiwyg_filter process plugin.