In the case that we would do the following:

    $this->addFieldMapping('path', 'field')
      ->description(t('Setting manual alias'));

    $this->addFieldMapping('pathauto')
      ->description(t('Disabling pathauto'))
      ->defaultValue(0);

I was thinking possibly there might be a problem if MigratePathautoHandler runs before MigratePathHandler since the latter relies on $entity->path being set as the URL alias, but the former doesn't account for that. This may not be a real issue since I am uncertain of the actual order of operations for those handlers or if they could possibly run in the reverse order, but it seems a good thing to have fixed just in case, if not for showing that these types of conditions could exist and users will need to be cautious of them.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Dave Reid’s picture

Status: Active » Needs review
FileSize
762 bytes
mikeryan’s picture

Committed, thanks! Now, what would be cool were if migration support moved directly into pathauto;).

mikeryan’s picture

Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.