Closed (fixed)
Project:
Drupal core
Version:
9.1.x-dev
Component:
migration system
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
6 May 2021 at 11:09 UTC
Updated:
25 May 2021 at 02:54 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
n4r3nThis patch provides link module's field formatter mapping.
Comment #3
n4r3nComment #5
quietone commented@n4r3n, are these formatters in Drupal 7 core or are they supplied by contrib?
Comment #6
wim leersThanks for starting this issue & patch, @n4r3n! 🙏
They're in D7 contrib, but for a module that was moved into core: the Link module: https://git.drupalcode.org/project/link/-/blob/7.x-1.x/link.module#L1210. For all other contrib-modules-providing-field-types-that-now-live-in-Drupal-8-core cases, we've specified the mapping in core. So I think we should do the same here.
@n4r3n Looks like you'll need to update the expectations in
\Drupal\Tests\migrate_drupal\Kernel\d7\FieldDiscoveryTest::addAllFieldProcessesAltersData()— once you do that tests should pass! 😊👍Comment #7
n4r3nThank you for reviewing it, here is the patch with updated test case.
Comment #8
wim leersThat looks great! Will manually test in the morning 🤓
Comment #9
wim leersManually tested, works beautifully! 👏
This does not migrate the field formatter settings, but that is also not the case for the pre-existing
link_defaultformatter (itscustom_titlesetting is not migrated).Therefore: this is a net improvement for everyone — migrating the formatter settings is out of scope here. Because doing that would require not just adding it for these new mappings, but also for the pre-existing
link_defaultmapping.Comment #12
catchCommitted/pushed to 9.3.x and cherry-picked to 9.2.x and 9.1.x, thanks!
Comment #14
quietone commented