Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Store: Fix Apple Pay Option #21618

Merged
merged 2 commits into from
Jan 19, 2018
Merged

Store: Fix Apple Pay Option #21618

merged 2 commits into from
Jan 19, 2018

Conversation

justinshreve
Copy link
Contributor

@justinshreve justinshreve commented Jan 17, 2018

Apple Pay support still exists in the latest Stripe Gateway plugin, but has been renamed to "Payment Request Buttons" which also includes Chrome Pay support.

This updates the option we are saving, as well as the text to reflect that both will be enabled (which matches what wp-admin does).

It also introduces a temporary API fix that is causing Stripe saves to fail for new stores (which was also reported on our P2 this morning). The value 'default' gets pushed back for one of the settings that is a dropdown and only has three valid options. This one forces a default. I opened an issue at woocommerce/woocommerce-gateway-stripe#459. I'm not sure if we want to offer a drop down option for this either or just stick with the default the gateway sets. I've left it out for now but we can add it in a follow-up.

To Test:

  • Make sure you can open up the stripe dialog both in 'key' mode and 'connect' mode.
  • Make sure you can toggle the value of the button.
  • Make sure your values save.

@justinshreve justinshreve added [Status] Needs Review The PR is ready for review. This also triggers e2e canary tests and wp-desktop tests automatically. Store labels Jan 17, 2018
@justinshreve justinshreve self-assigned this Jan 17, 2018
@justinshreve justinshreve requested a review from a team January 17, 2018 19:39
@justinshreve justinshreve force-pushed the fix/store-stripe-apply-pay branch from 0fe2d14 to f1bbeae Compare January 17, 2018 19:41
Copy link
Contributor

@timmyc timmyc left a comment

Choose a reason for hiding this comment

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

I'm not able to change any of my Stripe settings using this branch right now - the API is returning the following error message:

"body":{"error":"rest_setting_value_invalid","message":"An invalid setting value was passed."}}

stripe-save

@allendav
Copy link
Contributor

allendav commented Jan 19, 2018

If a site

screen shot 2018-01-18 at 5 56 30 pm

  • when you try to save a change (e.g. to the descriptor) , it borks because of the empty values

screen shot 2018-01-18 at 6 02 45 pm

edit: Workaround: Save settings once in wp-admin, then force refresh calypso

@justinshreve
Copy link
Contributor Author

@allendav Thank you so much for tracking it down that it was those other options. I made a fix that should set these values if they are empty. See d3b08f3.

You should now be able to save if you have borked settings. I made a little plugin to make it help mess up your settings so you can test the fix along with the rest of this branch.

To Test:

@justinshreve justinshreve requested a review from allendav January 19, 2018 06:46
Copy link
Contributor

@timmyc timmyc left a comment

Choose a reason for hiding this comment

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

With the latest updates all is looking good and testing well on the two sites I was experiencing issues with yesterday. Thanks for the work on this @allendav and @justinshreve

@timmyc timmyc added [Status] Ready to Merge and removed [Status] Needs Review The PR is ready for review. This also triggers e2e canary tests and wp-desktop tests automatically. labels Jan 19, 2018
@justinshreve justinshreve merged commit 7c54067 into master Jan 19, 2018
@justinshreve justinshreve deleted the fix/store-stripe-apply-pay branch January 19, 2018 16:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants