- Issue created by @matthiasm11
- 🇧🇪Belgium matthiasm11
Patch in attachment as a starting point. (not tested yet, only fixed some code errors)
- 🇧🇪Belgium davidiio
We are not able to apply this patch using mglaman/composer-drupal-lenient (along with the drupal 11 compatibility patch) on a drupal 11 with Commerce 3
Composer still complains about commerce_mollie requiring commerce 2.Should this issue (and drupal 11 compatibility) be prioritize higher? Since drupal 11 is here and commerce 2 is not compatible with drupal 11 all new commerce installs will be in commerce 3.
This module not being compatible with D11 and Commerce 3 means all users of commerce_mollie are unable to upgrade their website.
- Issue was unassigned.
- Status changed to Needs review
about 1 month ago 1:23pm 23 March 2025 - 🇧🇪Belgium adiatis Belgium
Same problem here, new commerce projects are blocked. Patch is not working. Please create new D11/Commerce 3 release.
- First commit to issue fork.
- 🇧🇪Belgium lothardesmet
Tested the patch with the dev-branch and everything is working fine with Commerce 3.
- 🇧🇪Belgium davidiio
We were able to install commerce_mollie on Drupal 11.1.5 with commerce 3 using this issue fork.
When we
composer require drupal/commerce_mollie
, it did not complain aboutmollie/mollie-api-php
missing but had an error message when trying to activate commerce_mollie in Drupal interface.Then I did
composer require mollie/mollie-api-php
and it installed version 3 which is not supported so we had tocomposer require mollie/mollie-api-php:^2
after running through some errors.All of this is weird because commerce_mollie requires mollie-api 2 in its composer.json file
"require": { "drupal/commerce": "~2.20 || ^3.0", "mollie/mollie-api-php": "~2.0" }
But anyway in the end it is working