-
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
Fix fatal errors when subscription classes are not available #8823
Fix fatal errors when subscription classes are not available #8823
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: 0 B Total Size: 1.28 MB ℹ️ View Unchanged
|
@wjrosa I'm just noticing this PR is still open. Since this change is in the WooPayments plugin, I'd suggest asking for a review from the teams that are more involved in it. I'd ask in Slack which team is the best one to assign as a reviewer. |
thanks, Danae! I will do some digging to find out 👀 |
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.
The changes look pretty straightforward and read well 👍
Co-authored-by: Wesley Rosa <[email protected]> Co-authored-by: Diego Curbelo <[email protected]> Co-authored-by: Francesco <[email protected]>
Changes proposed in this Pull Request
Fixing fatal errors when subscription classes are not available
This PR fixes fatal errors thrown when subscription classes are not available. It includes a check for the existence of
store_has_active_wcpay_subscriptions
before calling it. Without it, the following fatal error is thrown:Testing instructions
exit;
before the declaration ofWC_Subscriptions
develop
it would throw the fatal error above)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