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.
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.Top Drupal contributor Acquia would like to thank their partners for their contributions to Drupal.
Drupal is a registered trademark of Dries Buytaert.
Comments
Comment #2
kmajzlik CreditAttribution: kmajzlik at Ciklum Western Europe for BurdaForward commentedComment #3
bojanz CreditAttribution: bojanz at Centarro commentedYou updated Commerce but didn't update Entity API ("composer update drupal/commerce --with-dependencies" should have done it for you).
You can do "composer update drupal/entity" to update Entity API.
Comment #4
kmajzlik CreditAttribution: kmajzlik at Ciklum Western Europe for BurdaForward commentedSo it means there is a bug in composer.json of Commerce. If current Commerce release (2.5) needs Entity 8.x-1.0-beta3 then it should be marked there but only ~1.0 specified which causes usage of incompatible version of Entity module.
I made
composer update --with-dependencies drupal/commerce drupal/commerce_price drupal/commerce_product drupal/commerce_order drupal/commerce_payment drupal/commerce_payment_example drupal/commerce_checkout drupal/commerce_tax drupal/commerce_cart drupal/commerce_log drupal/commerce_store drupal/commerce_promotionand it caused failing site.
We need module in consistent state in meaning of dependencies in composer.json
Comment #5
bojanz CreditAttribution: bojanz at Centarro commentedLet's do that.
Comment #6
kmajzlik CreditAttribution: kmajzlik at Ciklum Western Europe for BurdaForward commentedhttps://github.com/drupalcommerce/commerce/pull/852
Comment #8
bojanz CreditAttribution: bojanz at Centarro commentedThanks!