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.
This needs testing in 6.x as well.
Steps to reproduce:
- Add a bunch of fields to a node type in D7.
- Add a piece of content in D7.
- In D8, run the migration (I used the UI in the latest version of Migrate Upgrade).
- The content gets migrated, but nothing but title and body come over.
- Be sad. :(
Comment | File | Size | Author |
---|---|---|---|
#8 | interdiff-2563819-7.txt | 2.72 KB | phenaproxima |
#7 | 2563819-7.patch | 8.55 KB | phenaproxima |
#7 | 2563819-7-FAIL.patch | 6.6 KB | phenaproxima |
#2 | 2563819-2-FAIL.patch | 2.39 KB | phenaproxima |
Screen Shot 2015-09-05 at 2.34.22 PM.png | 53.42 KB | webchick |
Comments
Comment #2
phenaproximaFail patch proving the issue. It's real!
Comment #3
phenaproximaOn further investigation, I have discovered that what's actually broken here isn't the field definitions or values, but the display settings. They're not migrating correctly, so it only looks like fields are broken. Which is itself a critical brokenness, but still :)
Renaming the issue.
Comment #4
webchickSending to testbot so we can see it BURN.
Comment #7
phenaproximaI screwed up with git a bit, but hopefully these patches will do the trick.
Comment #8
phenaproximaForgot the interdiff.
Comment #11
mikeryanCode looks good, and my node fields show up on a D7 migration.
Comment #12
webchickThis patch exposed a gnarly problem in #2410875: Migration for Drupal 7 Taxonomy vocabularies and terms so we should get this in.
Patch overall looks fine, although:
Wow, that is some midnight dark black frigging magic. :\ I've literally no idea how someone who hadn't helped write this system would ever have figured that fix out. :( Thank you.
Committed and pushed to 8.0.x. YEAH!
Comment #14
webchickSadly, this introduces a new SQLite fail, and thus a critical: #2566723: New test fail on PHP 5.5 & SQLite 3.8.
Any hopes of a quick fix?