0

I want to update Drupal Commerce to 8.x-2.0-beta7 from a clean, Composer-based installation of 8.x-2.0-beta6, following the documentation on http://docs.drupalcommerce.org/v2/getting-started/update.html.

I noticed that composer update drupal/commerce --with-dependencies did not update drupal/core. This surprises me. Isn't drupal/core a dependency? Anyway, says it's white-listed so I then ran composer update drupal/core.

Now I am hitting a problem with updates.

drupal update:debug

Fatal error: Cannot use Drupal\Console\Core\Bootstrap\DrupalConsoleCore as DrupalConsoleCore because the name is already in use in/pathto/commerce8/vendor/drupal/console/src/Bootstrap/Drupal.php on line 11

drupal update:execute

Fatal error: Cannot use Drupal\Console\Core\Bootstrap\DrupalConsoleCore as DrupalConsoleCore because the name is already in use in /pathto/commerce8/vendor/drupal/console/src/Bootstrap/Drupal.php on line 11

I have since run update.php, but the Composer errors persist.

I am learning about Composer, and I don't know yet anything about Drupal Console.

What am I doing wrong?

Improve this question
1
  • These are Drupal Console errors, not Composer errors, whole different program. Please update the question title. Guessing that Drupal Console broke because you forgot to do --with-dependencies when you updated drupal core. You need "composer update drupal/core --with-dependencies"
    – Bojan Zivanovic
    May 10, 2017 at 14:34

1 Answer 1

Reset to default
1

It sounds like Drupal Console someone was installed improperly, based on the duplicate class name error.

Can you try removing the /pathto/commerce8/vendor directory. Then run composer install once more. That'll fixup all third party dependencies, hopefully resolve this.

Improve this answer
2

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.