This module should be updated to include Drush 9 compatibility. Some of this can be automatically generated. see https://weitzman.github.io/blog/port-to-drush9 for tips.
I wrote a patch converting drupalmoduleupgrader to drush 9: #2949601: Drush 9 compatibility. Something similar could be done here.
| Comment | File | Size | Author |
|---|---|---|---|
| #12 | drush-9-support-2955644-11.patch | 6.54 KB | digitaldonkey |
| #11 | drush-9-support-2955644-10.patch | 6.56 KB | digitaldonkey |
| #10 | drush-9-support-2955644-9.patch | 6.11 KB | digitaldonkey |
| #8 | drush-9-support-2955644-8.patch | 6.07 KB | guptahemant |
| #5 | 2955644-5-drush_9_compatibility.patch | 6.31 KB | stella |
Comments
Comment #2
alfaguru commentedHi, I have made a patch for this issue. It's not perfect - the printed list of migrations at the end is always empty and there's no validation of options - but it does generate working migrations when correct options are supplied.
Comment #3
hongpong commentedThank you alfaguru this is an excellent start on this issue. I think we should have validation before committing this though.
Comment #4
hongpong commentedClosing the other issue about this. John B added:
Drush 9 does not work with drush.inc files for earlier versions of drush, and a new drush implementation is needed for this module.
FWIW, drush wordpress-migrate-generate fails silently with drush 8.
Comment #5
stella commentedUpdated patch which now prints out the list of migrations generated.
Comment #6
hongpong commentedThanks will try to get this looked at asap. Will try to get it to jibe w. drush 10 also.
Comment #7
guptahemant commentedHere is the patch against latest release, Its a reroll of #5
Comment #8
guptahemant commentedPrevious patch was empty, here is a new patch.
Comment #9
digitaldonkey commentedAs '--greoup-id' seems required. Maybe you do
$configuration['group_id'] = isset($options['group-id']) ? $options['group-id'] : 'default';
@migrateGenerate():L78
Second get('migration_group') should be getMigrationTags() as of #3159476
Comment #10
digitaldonkey commentedComment #11
digitaldonkey commentedComment #12
digitaldonkey commentedComment #13
digitaldonkey commentedIf I'd known that we only generate config entities, that I can't use for further processing I wouldn't have tried to fix this one :/
What I expected was a kind of `wordpress:migrate-generate --xml-files` so that I could proceed working from there.
Comment #14
hongpong commentedWe are moving this to a new issue for implementing Drush 12+: #3489516: Implement Drush 13+ on wordpress_migrate. Everyone that worked on this one will be credited. Thank you all!