- π©πͺGermany robcast
For me version 2.0-alpha2 of the module works with Drupal 9.5.8 / Drush 11.5.1 after I remembered to run
drush en migrate_devel
:-) - Status changed to Postponed: needs info
over 1 year ago 12:43pm 28 July 2023 - π³π±Netherlands batigolix Utrecht
Is this still an issue with older drush versions?
- πΊπΈUnited States amaisano Boston
I'm using the brand new release for D10 that came out today and am getting these errors as well. Using Drush 11.x.
- π³π±Netherlands batigolix Utrecht
LMAC-1FPJGH8-AG:src amo23$ drush ms --migrate-debug
I think there is no --migrate-debug option for the drush ms command
It does works for the migrate:import command.
But I see it is mentioned in the readme that it also should work for migrate:status. I am unsure what this option is supposed to do form the migrate:status command. What did you expect to happen?
- πΊπΈUnited States amaisano Boston
Right. The command --migrate-debug command works fine for the migrate:import command. --migrate-debug-pre doesn't seem to be doing anything however.
I was hoping to see debug output BEFORE doing the import, which is why i hoped the README was right about the migrate:status be compatible with the debug command, so it can show me "all that it sees" prior to performing the import, which I think was the original idea.
- π³π±Netherlands batigolix Utrecht
From what I can see in the code:
The option --migrate-debug-pre runs before the row is saved and --migrate-debug runs after the row is saved.
So --migrate-debug-pre does not prevent the row from being saved. It just runs beforeIn the older drush versions both options (--migrate-debug-pre and --migrate-debug) worked in combination with migrate:status as triggers to clear the cache and import the migration configuration. In newer drush versions this does not seem to happen.
I suppose the documentation needs to be clarified for this part, but maybe first the old drush code must be cleaned up.
- Status changed to Closed: works as designed
about 1 year ago 7:31am 25 August 2023 - π³π±Netherlands batigolix Utrecht
Feel free to re-open if you think this still needs to be fixed somehow
- Status changed to Active
about 1 year ago 7:01pm 3 October 2023 - π·πΈSerbia kliker
I needed to check couple of migrations and I realized that drush is nor recognising --migrate-debug.
I tried both v2.2 and v2.1 versions of the Migrate Devel:
v2.2
$ lando drush mim upgrade_d7_field --limit=1 --migrate-debug The "--migrate-debug" option does not exist.
drush help migrate:import
is not listing --migrate-debug under Optionsv2.1
drush help migrate:import
is listing --migrate-debug under Options but debug info does not show up below the migrate-import notice.$ lando drush mim upgrade_d7_field --limit=1 --migrate-debug [notice] Processed 1 item (0 created, 0 updated, 0 failed, 1 ignored) - done with 'upgrade_d7_field'
Am I missing something?
Drush Commandline Tool 11.6.0
Drupal version : 9.5.11
PHP version : 8.1.21 - π³πΏNew Zealand jonathan_hunt
* PHP 7.433
* Drupal 9.5.11
* Drush 11.0.2
* Migrate devel 2.2 The "--migrate-debug" option does not exist.Downgraded to Migrate devel 2.1, "--migrate-debug" works as expected.
- π³π±Netherlands batigolix Utrecht
I noticed this as well. I will look into this.
So for user that run into this problem: you can downgrade to version 2.1
- π§π·Brazil carolpettirossi Campinas - SP
Same as #18.
I had to downgrade to 2.1
- π¬π§United Kingdom thetwentyseven
Downgrading to 2.1 works because the 2.2 version the file drush.services.yml is missing.
- π¬π§United Kingdom thetwentyseven
If you updated to 2,2 here it is the patch
- Status changed to RTBC
about 1 year ago 3:46pm 11 October 2023 - π·πΈSerbia kliker
Thank you @thetwentyseven, your patch resolves the v2.2 issue.
- πΊπΈUnited States pbabin
@thetwentyseven - thank you for the patch!
-
thetwentyseven β
authored cb66e42c on 8.x-2.x
Issue #3002711 by thetwentyseven: The "--migrate-debug" option does not...
-
thetwentyseven β
authored cb66e42c on 8.x-2.x
- Status changed to Fixed
about 1 year ago 7:35am 27 October 2023 - π³π±Netherlands batigolix Utrecht
Thanks everybody for fixing & reviewing this. I ll create a new release with this fix
Automatically closed - issue fixed for 2 weeks with no activity.
- Status changed to Fixed
12 months ago 9:45am 6 December 2023