Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Hi,
I'm using this module to migrate my D6 website, into 2 different website.
One use the 8.x-3.0-rc4 version and the other one 8.x-3.0-rc5.
The second one doesn't accept to create new migrations from fresh install..th eother one work as designed.
drush debug code:
Drush bootstrap phase : bootstrap_drupal_database() [0.21 sec, 8.58 MB] [bootstrap]
Successfully connected to the Drupal database. [0.21 sec, 8.58 MB] [bootstrap]
Find command files for phase 4 (max=5) [0.21 sec, 8.58 MB] [debug]
Drush bootstrap phase : bootstrap_drupal_full() [0.21 sec, 8.58 MB] [bootstrap]
About to bootstrap the Drupal 8 Kernel. [0.21 sec, 8.59 MB] [debug]
Finished bootstraping the Drupal 8 Kernel. [0.27 sec, 16.92 Mo] [debug]
Cache HIT cid: 8.1.16-install_profile-6dfce66ee85e248453041340113581eb [0.3 sec, 17.89 Mo] [debug]
Find command files for phase 5 (max=5) [0.3 sec, 17.99 Mo] [debug]
Cache HIT cid: 8.1.16-install_profile-6dfce66ee85e248453041340113581eb [0.3 sec, 17.99 Mo] [debug]
Cache HIT cid: 8.1.16-commandfiles-5-849c8b6353def1ac8eb3c9dbbacd8c9a [0.31 sec, 18.38 Mo] [debug]
Find command files for phase 2 (max=3) [1.26 sec, 21.5 Mo] [debug]
Cache HIT cid: 8.1.16-install_profile-6dfce66ee85e248453041340113581eb [1.26 sec, 21.5 Mo] [debug]
Cache HIT cid: 8.1.16-commandfiles-2-de9e51bda4b04a9491378098baf75267 [1.26 sec, 21.51 Mo] [debug]
Command migrate-upgrade needs the following extension(s) enabled to run: migrate_upgrade. [1.91 sec, 23 Mo] [error]
The drush command 'migrate-upgrade' could not be executed. [1.92 sec, 23 Mo]
Is there a bug ?
Thanks
Comment | File | Size | Author |
---|---|---|---|
#6 | Migrate_upgrade_rc5_seem_not_to_work-29196962-6.patch | 775 bytes | stefan.korn |
Comments
Comment #2
aiphesComment #3
longwaveMoving this to the Migrate Upgrade queue, as this doesn't seem to be an issue for Drupal core.
Comment #4
stefan.kornWhat version of drush are you using?
Comment #5
phuang07 CreditAttribution: phuang07 as a volunteer commentedI have issue in rc5 as well. Rc4 is ok.
Comment #6
stefan.korn@ph53: This is probably related to your drush version. RC5 is currently not working with drush version 8, only version 9.
Check if it works for you with this patch.
Comment #7
stefan.kornComment #8
aiphesSo it's normal behaviour as I'm using Drush Version : 8.1.16
If Drush 8 doesn't work with rc5, a warning to no update would be great on the module page.
Comment #9
phuang07 CreditAttribution: phuang07 as a volunteer commented@stefan.korn
The patch #6 is not working.
Comment #10
stefan.kornOk, I think there is another issue with the "legacy-db-key" parameter that is not related to this issue. Will try to sort this out.
Comment #11
stefan.korn@ph53: Could you please try and use patch from here too: https://www.drupal.org/project/migrate_upgrade/issues/2999099#comment-12...
This fixes a general issue with the "legacy-db-key" option, that affects the module as a whole not only regarding Drush version.
Comment #12
designcrs CreditAttribution: designcrs commented@stefan.korn:
Applying #6 https://www.drupal.org/project/migrate_upgrade/issues/2996962#comment-12...
and https://www.drupal.org/project/migrate_upgrade/issues/2999099#comment-12...
has fixed the problem.
I can now run "drush migrate-upgrade" for my D6 site again!
Thank you!
Comment #13
rwmanos CreditAttribution: rwmanos commentedRunning migrate-upgrade with Drush 8.1.15 gives Call to undefined method Drush\Sql\SqlBase::dbSpecFromDbUrl() error.
Applying both patches listed in #12 seem to fix the issue so thank you all for providing a solution. However, I still believe this is extremely inconvenient and the functionality should not break with a regular module update (in rc state already).
Comment #14
heddnIdeally, folks will upgrade to Drush 9 as 8 hasn't been supported on Drupal since 8.3. See http://docs.drush.org/en/master/install/#drupal-compatibility.
But this is a simple fix. So committing.
Comment #16
heddnComment #17
aiphesD8.6.2 seem not to fix the issue, RC5 can be enabled.But when I do
drush @site migrate-upgrade XXXXX --configure-only
I get th errorComment #18
heddnYou have to upgrade from the tag rc5 to the dev branch of this module.
Comment #20
aiphesJust a feedback on another migration using v3.0 and RC4 with Drush 8.
Result is the same: Group: Import from Drupal 6 (migrate_drupal_6) is created, and default group is partially created.
If I re-run the command I get:
Will it be an issue when I will an update of migrations to get back content created between 2 migrations ?
Could it be a memory limit ou time limit of the connexion to the server ?