- Issue created by @hongpong
-
hongpong β
committed d2998fcf on 8.x-3.x
Issue #3489516 "Remove broken Drush 8 file, Update README.md"
-
hongpong β
committed d2998fcf on 8.x-3.x
- π©π°Denmark ressa Copenhagen
It looks like a task can be struck from this issue, since the old wordpress_migrate.drush.inc file was removed.
Can the patch from #2955644-12: Implement WordPress Migrate with Drush 9/10 β be transferred to this issue as an MR? Or are the changes in Drush 13 too big, and it needs a total rewrite?
Also, perhaps the Issue Summary could get an update since this doesn't seem correct: "Drush 12+ is now supported"
- π©π°Denmark ressa Copenhagen
I spotted the Drush command
drush wordpress:migrate-generate
in the patch file β in the other issue, which I added to the Issue Summary ... I hope it's correct?Generating a WordPress migration entirely via Drush, instead of via the GUI, would be a really cool feature to have.
- πΊπΈUnited States hongpong Philadelphia
It is a great question, I haven't made or updated drush commands in a minute. You are probably looking in the right spot. the boilerplate in Drush definitely change over the years. for one thing it uses new style php attributes instead of annotations https://mglaman.dev/blog/writing-drush-commands-php-attributes
i asked the claude bot about drush 9 vs 12 or 13 and it gave me this; https://claude.ai/share/e41bca21-d38d-498c-9818-c17b286642d4
Thanks for your interest in re addressing this, it is a very good idea.