Make migrate:import --migrate-debug compatible with Drush9+

Created on 22 January 2018, almost 7 years ago
Updated 24 February 2023, almost 2 years ago

Drush9 does not support old style hooks. See https://weitzman.github.io/blog/port-to-drush9

Done:

  • Adds the drush.services.yml and composer boilerplate.
  • Adds a new DrushCommands class.
  • Registers the new options, replacing hook_drush_help_alter().
  • Makes the kint() dumps work for the migrate:import commands.

ToDo:

  • Release 8.x-2.x branch
  • Make the migration rebuilds work.
  • Maybe combine the EventSubscriber and Drush commands in a single class?
  • move preMigrateStatus() the new Drush 9 command hooks.
  • move preMigrateImport() the new Drush 9 command hooks.
πŸ“Œ Task
Status

Fixed

Version

2.0

Component

Code

Created by

πŸ‡¨πŸ‡ΏCzech Republic kmajzlik

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡ΊπŸ‡ΈUnited States BThiemeNatlaw

    This issue still needs to be reviewed. We are attempting to migrate a large site from Drupal 7 - Drupal 9, and are on a fresh Drupal 9.4.7 install along with migrate_devel 8.x-2.0-alpha2, and the same issue persists with Drush 11.4.0. Has anyone found a solution? This bug makes the module essentially useless.

  • πŸ‡³πŸ‡ΏNew Zealand xurizaemon Ōtepoti, Aotearoa 🏝

    Hi @BThiemeNatlaw

    I think it's that the release installed on that site was generated a few days before the commit in this issue was landed.

    - 8.x-2.0-alpha2 is dated 23 June 2020.
    - Commit fixing this issue was 27 June 2020.

    Try composer require 'drupal/migrate_devel:2.x-dev@dev' (or something like that), and see if the issue is resolved please?

    There are many benefits to publishing a stable release for a project. There may be things we can do to support an updated release of Migrate Devel, which might in turn reduce the number of people bumping on that issue you appear to have hit.

    Practically, I think we largely use Migrate Devel on the 'dev branch' (eg some 2.x-dev build, likely pinning to a specific point to avoid surprises). Since it's a development tooling module, sites may opt to be more tolerant of a dev release.

    (There is an issue template for requesting a stable release of a module over in #3239062: 'Stable Release Request' Issue Template β†’ which you might find helpful too.)

    Hope this sorts it out for you!

Production build 0.71.5 2024