Migrate configuration from 6.x-1.x, 7.x-1.x

I am happy to report that I was able to use this patch to successfully migrate my External Links module configuration from my drupal-7.99 site running extlink-7.x-1.21 to a drupal-10.2.1 site running extlink-8.x-1.7.

Unfortunately, I cannot RTBC this issue because I wrote the patch → . But, hopefully, my success will help other people migrating D7 to D10.

Unfortunately, however, now that my D7 to D10 site migration is complete, my ability to contribute further to this issue is severely limited, because the D7 site that I had been using to test has been retired. However, I'll keep an eye on this issue and try to answer questions to the best of my ability.

@mparker17 could you please turn this into a MR?

@Wim Leers, 2Y later still plans for review? ;D (joking, sorry)

@Anybody, sure! Here's a link to !12, where I applied the patch from #6 ✨ Migrate configuration from 6.x-1.x, 7.x-1.x Needs review .

Has some warnings in the MR.

Should note the warnings for stylelint are known and I’ll fix in another ticket

The remaining lints are happening in files that weren't changed in this MR (i.e.: eslint failing because of extlink.js; phpstan (next major) failing because of src/Form/ExtlinkAdminSettingsForm.php; stylelint failing because of extlink.css.

I also see Drupal\Tests\extlink\FunctionalJavascript\ExtlinkAdminTest::testExtlinkDisabledOnAdminRoutes is failing in several tests, and nothing related to that was changed in the merge request.

That being said, I see Drupal\Tests\extlink\Kernel\ValidateD6SettingsMigrationTest::testMigration and Drupal\Tests\extlink\Kernel\ValidateD7SettingsMigrationTest::testMigration are failing, and those were changed here, so I'll work on those.

Pipeline is all green now.

Drupal\Tests\extlink\Kernel\ValidateD6SettingsMigrationTest::testMigration and Drupal\Tests\extlink\Kernel\ValidateD7SettingsMigrationTest::testMigration are failing,

Message I'm getting is that extlink is not enabled on source site.

Have 0 idea if that's correct, I copied the fixtures from another module but they seem to be passing now.

@smustgrave, thank you! In this case, as long as the fixtures set up the tables needed for the test, then I'd say it's fine.

(Normally I would RTBC at this point, but since I wrote some of the patch, and I don't have a migration to test anymore, I probably shouldn't)

smustgrave → closed merge request !12

It's non disruptive so I don't mind merging. Thanks for taking a look!