-
Notifications
You must be signed in to change notification settings - Fork 69
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
Ensure 'wcSettings' Exists Before Checking for 'wcSettings.wcBlocksConfig' #9174
Conversation
Test the buildOption 1. Jetpack Beta
Option 2. Jurassic Ninja - available for logged-in A12s🚀 Launch a JN site with this branch 🚀 ℹ️ Install this Tampermonkey script to get more options. Build info:
Note: the build is updated when a new commit is pushed to this PR. |
Size Change: +30 B (0%) Total Size: 1.33 MB
ℹ️ View Unchanged
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was able to test this locally and on staging. To "break" the flow and cause an error message I just disabled the dev token secret being set in both environments. I then tested this in Cart, Cart Block, Checkout and Checkout Block. When the token was not set I properly saw an error message with this PR. When the token was set, I properly got redirected to WooPay.
LGTM!
Fixes n/a
Changes proposed in this Pull Request
The changes in this PR ensure that the
wcSettings
global var exists before attempting to check forwcSettings.wcBlocksConfig
.Testing instructions
Tip
These tests should be executed in the staging site.
Prerequisites
DEV_BLOG_TOKEN_SECRET
does not match.Test: Ensure error message is displayed when
Buy with WooPay
fails when in classic cart[woocommerce_cart]
shortcode.Buy with WooPay
button.Something went wrong. Please try again.
Test: Ensure error message is displayed when
Buy with WooPay
fails when in blocks cartcart
wc-block.Buy with WooPay
button.Something went wrong. Please try again.
npm run changelog
to add a changelog file, choosepatch
to leave it empty if the change is not significant. You can add multiple changelog files in one PR by running this command a few times.Post merge