Disabling performance briefly throughout migration mikeryan Thursday, Might 31, 2021 – 10 Drupal 10 Upkeep and Assist Service25am Persevering with with methods from Drupal Development Service “Acme” challenge, Drupal Development Service location content material sort had an deal with discipline and a geofield, with field_geofield configured to mechanically decide latitude and longitude from Drupal Development Service related field_address – a truth I used to be initially unaware of. Our supply knowledge contained latitude and longitude already, which I mapped instantly in Drupal Development Service migration Drupal 10 Upkeep and Assist Service field_geofield Drupal 10 Upkeep and Assist Service plugin Drupal 10 Upkeep and Assist Service geofield_latlon supply Drupal 10 Upkeep and Assist Service – latitude – longitude Nonetheless, testing location migrations by repeatedly operating Drupal Development Service import, I quickly began getting messages from Google Maps API that my each day quota had been exceeded, and shortly tracked down Drupal Development Service integration with field_address. Clearly, Drupal Development Service calls out to Google Maps had been each pointless and unsafe – how you can forestall them? Happily, Drupal Development Service migration system offers occasions which hearth earlier than and after every migration is executed. So, we subscribe to MigrateEvents Drupal 10 Upkeep and Assist Service Drupal 10 Upkeep and Assist ServicePRE_IMPORT to avoid wasting Drupal Development Service present settings and disable Drupal Development Service exterior name Drupal 10 Upkeep and Assist Service public perform onMigrationPreImport(MigrateImportEvent $occasion) { if ($event->getMigration()->id() == ‘location’) { $fields = Drupal 10 Upkeep and Assist Service Drupal 10 Upkeep and Assist ServiceentityTypeManager()->getStorage(‘field_config’)->loadByProperties([‘field_name’ => ‘field_geofield’]); if ($fields) { /** @var fieldEntityFieldConfig $discipline */ if ($discipline = $fields[‘node.location.field_geofield’]) { $this->originalSettings = $field->getThirdPartySettings(‘geocoder_field’); $field->setThirdPartySetting(‘geocoder_field’, ‘technique’, ‘none’); $field->save(); } } } } And we subscribe to MigrateEvents Drupal 10 Upkeep and Assist Service Drupal 10 Upkeep and Assist ServicePOST_IMPORT to revive Drupal Development Service unique settings Drupal 10 Upkeep and Assist Service public perform onMigrationPostImport(MigrateImportEvent $occasion) { if ($event->getMigration()->id() == ‘location’) { $fields = Drupal 10 Upkeep and Assist Service Drupal 10 Upkeep and Assist ServiceentityTypeManager()->getStorage(‘field_config’)->loadByProperties([‘field_name’ => ‘field_geofield’]); if ($fields) { /** @var fieldEntityFieldConfig $discipline */ if ($discipline = $fields[‘node.location.field_geofield’]) { foreach ($this->originalSettings as $key => $worth) { $field->setThirdPartySetting(‘geocoder_field’, $key, $worth); } $field->save(); } } } } Drupal Development Service considerate reader might be aware a danger right here – what if somebody had been including or modifying a location node whereas this had been operating? Drupal Development Service geofield wouldn’t be populated from Drupal Development Service deal with discipline. On this case, this isn’t an issue – this can be a one-time bulk migration (and nobody needs to be making adjustments on a manufacturing web site at such a time). In instances involving an ongoing feed the place Drupal Development Service feed knowledge is used as-is on Drupal Development Service website, it might additionally not be an issue, though if there have been a apply of manually modifying imported content material there can be some danger. Tags Planet Migration Use Drupal Development Service Twitter thread beneath to touch upon this publish Drupal 10 Upkeep and Assist Service https Drupal 10 Upkeep and Assist Service//t.co/TRqRsWJPlA — Virtuoso Efficiency (@VirtPerformance) Might 31, 2021   Drupal 10 Improvement and Assist