Skip to content
This repository was archived by the owner on Jul 12, 2024. It is now read-only.

Conversation

@louwie17
Copy link
Contributor

@louwie17 louwie17 commented Dec 2, 2021

Fixes #7992

Fixes issue where a payment gateway id that has multiple configs differentiated by a colon in the id to still match the payment gateway correctly.
We use this for wc-pay to have different config for the us versus the rest of the world. Example of the id: woocommerce_payments:us.

No changelog necessary.

cc @joshuatf if you know of any other places that this could be a problem?

Screenshots

Screen Shot 2021-12-02 at 11 08 17 AM

Detailed test instructions:

  1. Use fresh site, and ensure you select a country that is WCPay supported (USA)
  2. Go through Onboarding wizard and select "WooCommerce Payments" in the free features (deselect everything else)
  3. Click the "Setup payments" task (NOT the WCPay specific task)
  4. Click "Get Started" button on the WCPay card.
  5. Notice how the Set up button is now present on step 2
  6. Try the same thing for the Paypal or Stripe gateways, step 2 should not be blank.

Copy link
Contributor

@joshuatf joshuatf left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the fix, @louwie17! I don't see any other areas right now that need fixes, but worth double checking with @joelclimbsthings as he may be more familiar with some of the logic around suggestion/gateway IDs on the client.

@joelclimbsthings
Copy link
Contributor

Thanks for jumping on this so quickly! After a quick scan I don't see anything else that will require changes here.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

WCPay task stepper stalls after clicking Get Started

4 participants