- π³πΏNew Zealand dieuwe Auckland, NZ
The change to omnipay 3.2 in the issue fork works - but with one caveat. This will only work with guzzle7, which
drupal/core-recommended:^9.5
does not support. However, usingdrupal/core
directly will allow you to switch to guzzle7.Other than that, this presumably works fine with D10 (not yet tested by me) and on PHP8.1 (tested by me).
- Status changed to Needs review
over 1 year ago 2:09am 18 September 2023 - π³πΏNew Zealand dieuwe Auckland, NZ
Switching to needs review instead of RTBC for now, and will come back to this once I have done more testing.
I wonder if the dependencies for this module should be more permissive or is that a separate issue? (use ^ instead of ~)
- π³πΏNew Zealand xurizaemon Εtepoti, Aotearoa π
Maybe try a
^6 || ^7
if Omnipay and Drupal versions have some intersections.Projects like Geocoder β have done that β¨ Drupal 10 compatibility: changing php-http/guzzle6-adapter dependency into php-http/guzzle7-adapter RTBC for D10 upgrades.
- π³πΏNew Zealand dieuwe Auckland, NZ
The problem is that the requirement for
guzzle/guzzle7
is a hard requirement through theleague/omnipay
package. Drupal core 9.5 does have the multiple version ranges allowed (6 and 7).I think with D9 EOL so close and jumps to D10 needing to happen in the next few months this is probably a fine caveat.
We could probably do
"league/omnipay": "^3.0 || ^3.2",
incommerce_dps
to allow for both D9+D10 and PHP7+PHP8 support to co-exist for a bit longer. - last update
about 1 year ago 11 pass - @xurizaemon opened merge request.
- @xurizaemon opened merge request.
- π³πΏNew Zealand xurizaemon Εtepoti, Aotearoa π
Agreed, I see now that this works with
drupal/core:^9.5
but the following are incompatible:drupal/core-recommended:^9.5
(requiresguzzlehttp/guzzle ~6.5.8
)league/omnipay
(requiresphp-http/guzzle7-adapter ^1
which requiresguzzlehttp/guzzle ^7.0
)
There are few apparent options, including omitting drupal/core-recommended, or (it seems?) replacing
league/omnipay
withomnipay/common
.MR !11 seems to work with Drupal 10, CI on xurizaemon/commerce-demo shows it passing a payment transaction in Behat. Have not tested further than that.
MR !13 here is just me seeing if there's a way to make the same change behave on D9, but I would accept merging a solution for D10 and leaving a release with the prior state for any D9 sites that need it.
(If you're running Commerce DPS with D9 currently, please pop a hand up if we can improve the situation.)
-
xurizaemon β
committed 9fd99484 on 2.0.x
Issue #3275719 by xurizaemon, lucashodge, dieuwe, Wim Leers: Omnipay +...
-
xurizaemon β
committed 9fd99484 on 2.0.x
- π³πΏNew Zealand xurizaemon Εtepoti, Aotearoa π
I've merged this, having realised that a detail which was nagging at me was actually all in my head :D
I trust that D9 sites will continue with whatever secret recipe they found to make it work in the meantime using dev releases.
Thanks all for the effort (and patience).
- Status changed to Fixed
about 1 year ago 10:58pm 25 September 2023 Automatically closed - issue fixed for 2 weeks with no activity.