Hi, just wanted to let you know that Commerce 2.0-RC1 has had breaking changes to its payment gateway API, and that this module will need to be updated.
You can find the instructions here: https://www.drupal.org/node/2894208
If you have any questions, you can post a patch to this issue, and someone from the Commerce Guys team will try to review.

Comments

krcha created an issue. See original summary.

vasike’s picture

Status: Active » Needs review
StatusFileSize
new2.63 KB

Here is a patch for this - this is all i could find about the Payment Gateway API change record.

vasike’s picture

Extra: this module uses 2 (set) credentials for live and test.
The Commerce 2.x recommend to have only one, and use the Mode option.

But this module has already stable releases, i think this should include also some updates about possible existing gateways set.
Maybe a new issue is needed for this.

zenimagine’s picture

Priority: Normal » Critical

I've upgraded to rc1 and I can not update my banned base even after uninstalling PayPlug

https://www.drupal.org/node/2894318
https://www.drupal.org/node/2894437

dom.’s picture

@vasike:
#2: patch RTBC
#3: Payplug gives you a different key for test and live. So using the mode switch, it changes the key used. How would you advice else to handle this situation ?

dom.’s picture

Status: Needs review » Reviewed & tested by the community

Commiting on dev

  • Dom. committed c4d329f on 8.x-1.x
    Issue #2894280 by vasike: Update for Commerce 2.0-RC1
    
vasike’s picture

Dom.

1. Would be nice to add the author for commits, if it is the case, of course ;).
2. About different key for test and live, you could check about a similar issue on Commerce Stripe
#2878295: The gateway should only store one set of API keys
But as i said, if the current release is "bigger than alpha" you need to provide updates :(.

  • Dom. committed 10f6848 on 8.x-1.x authored by vasike
    Issue #2894280 by vasike: Update for Commerce 2.0-RC1
    
dom.’s picture

Status: Reviewed & tested by the community » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.