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

[13.x] Fix a stripe notice with SubscriptionBuilder and metered prices #1261

Merged
merged 1 commit into from
Oct 4, 2021

Conversation

mfauveau
Copy link
Contributor

@mfauveau mfauveau commented Oct 1, 2021

This fixes a Stripe Notice (Stripe Notice: Undefined property of Stripe\SubscriptionItem instance: quantity) when using the SubscriptionBuilder with metered prices.
See my comments on #1254.

This fixes a Stripe Notice (Stripe Notice: Undefined property of Stripe\SubscriptionItem instance: quantity) when using the SubscriptionBuilder with metered prices.
See my comments on laravel#1254.
@driesvints driesvints changed the title Fix a stripe notice with SubscriptionBuilder and metered prices [13.x] Fix a stripe notice with SubscriptionBuilder and metered prices Oct 4, 2021
@driesvints
Copy link
Member

Thanks @mfauveau

@taylorotwell taylorotwell merged commit d7fa022 into laravel:13.x Oct 4, 2021
@stevebauman
Copy link
Contributor

This PR didn't fix this issue for me unfortunately:

Screen Shot 2022-06-13 at 11 20 23 AM

This appears to be a Stripe issue (for anyone else experiencing this). To get rid of these errors, Cashier would have to use the offsetGet() method instead of relying on Stripe's magic __get() method:

https://github.com/stripe/stripe-php/blob/68af684e5b76b941d3d01992879a854d53a43b57/lib/StripeObject.php#L185

https://github.com/stripe/stripe-php/blob/68af684e5b76b941d3d01992879a854d53a43b57/lib/StripeObject.php#L216-L219

@driesvints
Copy link
Member

Fixed here: #1377. Will release today.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants