- Issue created by @irafah
- First commit to issue fork.
- 🇬🇧United Kingdom kimberleycgm
I've added an MR to update the composer restriction. I've tested with our site locally and it all works well, so I don't think there is any need to limit it to version 2.
I've had to use composer aliases to install commerce v3 in the meantime, so it would be great to get this released properly asap.
Thanks
- 🇬🇧United Kingdom nexusnovaz
MR LGTM. Seems like a simple change and it shouldn't in theory affect anything else too much currently.
- 🇬🇧United Kingdom kimberleycgm
Noticed one thing that needs adjusting - adding fix shortly.
- 🇬🇧United Kingdom kimberleycgm
Pushed an update. The payment type is now mandatory and we run through the parent create method for all the set up.
- Status changed to Needs review
3 months ago 11:12pm 24 June 2025 - 🇺🇸United States j_s
FYI Commerce 2.x is no longer supported, which means this Commerce Cybersource module can no longer be installed with a normal composer require. The MR should be updated to remove 2.x compatibility. And a release should be made to make installing this module possible.
- 🇮🇱Israel jsacksick
Pushed an update. The payment type is now mandatory and we run through the parent create method for all the set up.
Where did you see that the payment type was now mandatory? It is not, plenty of modules aren't specifying it?
-
jsacksick →
committed 2ae515dd on 8.x-1.x authored by
kimberleycgm →
[#3508869] feat: Commerce 3...
-
jsacksick →
committed 2ae515dd on 8.x-1.x authored by
kimberleycgm →
- Status changed to Fixed
20 days ago 7:54am 28 August 2025 Automatically closed - issue fixed for 2 weeks with no activity.