Problem/Motivation
Because input formats have changed between Drupal 6/7 and 8, AFAICS in all cases, you get your node/comment titles moved over, but the bodies display as blank:
The data for the fields is in the database, but getting stripped out on the front end.
#3061571: If no Drupal 8 equivalent filter is found during migration, drop transformation-only filters, so that body fields show up →
proposes setting the bodies to plain text vs. an empty string, which would be one way of dealing with this, and a fairly simple patch if the proposal is accepted.
A more complex but more comprehensive fix would be to allow developers to make this mapping themselves, both through the UI and via Drush. Then the code doesn't need to perform any guess work, and potentially get it wrong (e.g. by accidentally exposing database credentials in plain text).
Major because this represents a pretty significant usability hurdle, and harms user confidence in the system early on. However, not tagging Migrate critical because the particular solution here will likely be tricky and we don't want to hold up stability of the overall migration system over it. (If the other issue gets won't fixed by the security team, I guess we might need to revisit this.)
Proposed resolution
Thanks to
#2876085: Before upgrading, audit for potential ID conflicts →
, we now have an "audit" step in the migrations, so we could maybe piggy-back off of that. (Though sounds like that's pretty one-off, so we may instead want to do
#3061676: Create an audit plugin class/manager for migrations →
and have this be one of the plugins.)
@todo come up with mockup.
Remaining tasks
- Find a suitable design
- Find a suitable Drush equivalent
- Write a patch + tests
- Review it
- Commit it!
User interface changes
By default, migrations will now display the proper content for body fields on nodes and comments. (As well as other rich text fields.)
API changes
?
Data model changes
N/A?
Release notes snippet
Migrations now default to the fallback filter format, fixing a problem where rich text fields were not displaying post-migration.