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.
Problem/Motivation
We need to provide an upgrade path from D7 for the core Text module.
Proposed Resolution
Data in text fields is migrated by #2416765: Migrate Drupal 7 Field/Instance/View mode settings, so this migration only needs to move any of Text's variables into configuration.
Remaining Tasks
- Update the patch to match HEAD
- Write tests
- Review the patch
- Commit it
Comment | File | Size | Author |
---|---|---|---|
#33 | 2409441-33.patch | 3.07 KB | quietone |
#28 | interdiff-2409441-26-28.txt | 479 bytes | phenaproxima |
#28 | 2409441-28.patch | 3.1 KB | phenaproxima |
#26 | interdiff-2409441-23-26.txt | 2.99 KB | phenaproxima |
#26 | 2409441-26.patch | 2.49 KB | phenaproxima |
Comments
Comment #1
oadaeh CreditAttribution: oadaeh commentedAttached is the YAML for this issue, from the patch in #2382117: Migration Files for Drupal 7 Variables.
Test(s) (and maybe a dump file) still need to be written.
Comment #2
miguelc303 CreditAttribution: miguelc303 at Anexus commentedAdded organization support to Anexus IT
Comment #3
jcost CreditAttribution: jcost commentedWill need to be submitted again to Core since moving from sandbox.
Comment #4
phenaproximaComment #5
phenaproximaUpdated for HEAD and wrote a test.
Comment #6
phenaproximaRe-rolled.
Comment #7
phenaproximaRe-rolled in accordance with #2533886: [meta] Move module-specific migration support into the particular modules supported.
Comment #8
phenaproximaHmm. Having a patch might, just might, help.
Comment #9
chx CreditAttribution: chx commentedo_O that's a config setting? Well, then.
Comment #11
alexpottNeeds a reroll...
Comment #12
phenaproximaRe-rolled. No interdiff due to conflicts in Variable.php dump file.
Comment #13
mikeryanManually comparing to the D6 test, this is missing config schema testing - it appears the policy is to do this for all configuration migrations: #2293419: Add config schema test to all configuration test in migration, fix bugs.
It would be great if migration paths which don't vary much from the D6 version had diffs against the equivalent D6 files, so we can more easily ensure feature/testing parity.
Comment #14
phenaproximaBehold!
EDIT: As per the comment below, this one is NOT RTBC. #12 is.
Comment #15
mikeryanWell, so sorry you rolled that new patch - looks like we should not bother with schema testing: https://www.drupal.org/node/2293419#comment-10170598
So, RTBC to the #12 patch.
Comment #17
webchickRelating to the fields issue.
Comment #18
phenaproxima#14 failed testing, but #12 did not, and it's the one to be committed. So back to RTBC.
Comment #21
phenaproximaNeeds a re-roll from #12.
Comment #22
quietone CreditAttribution: quietone commentedreroll
Comment #23
quietone CreditAttribution: quietone commentedThe migration templates for d6 and d7 are the same, so merged them.
Comment #25
quietone CreditAttribution: quietone commentedWhy does this fail?
Comment #26
phenaproximaI'm not sure, but one thing is certain -- when the D6 and D7 versions of a migration are merged, there's no need for two separate tests :) So I have removed the D7 version of the test and it seems OK now...
Comment #28
phenaproximaThis oughta work.
Comment #29
quietone CreditAttribution: quietone commented@phenaproxima, I missed the change MigrateDrupal6Test.php. And yes, I should have merged the tests.
+1 for RTBC
Comment #30
Kazanir CreditAttribution: Kazanir commentedLooks good to me.
Comment #32
phenaproximaComment #33
quietone CreditAttribution: quietone commentedAnd again. No interdiff because it fails. But the change was only to remove one line, loadDumps from the test.
Comment #34
quietone CreditAttribution: quietone commentedBack to RTBC
Comment #35
webchickCommitted and pushed to 8.0.x. Thanks!
Comment #37
lokapujya