You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since v191022 all s2member Stripe payments fail at Submit Form with onscreen error:
The site is experiencing technical difficulties
and in logs:
PHP Fatal error:
Cannot declare class Stripe\Stripe, because the name is already in use in
/home/xxxx/public_html/wp-content/plugins/s2member-pro/
src/includes/classes/gateways/stripe/stripe-sdk/lib/Stripe.php
on line 11
Disabled another plugin which hadn't changed to make sure the more important s2member is now working. So yes, this is a plugin conflict, but is 'stripe' the wisest class name?
The text was updated successfully, but these errors were encountered:
Thanks for reporting it. Yes, I'm aware of it and will put out a release soon. I've just been looking at what the best approach may be.
The Stripe SDK is distributed by Stripe, and used by many projects. So several plugins could be using it, that's why the overlap. Renaming their namespace could be complicated, because then everything that uses it has to be renamed too, and may introduce unexpected issues. I may need to just check if it's already loaded before trying to add it, but then it risks that the other copy that was loaded first, is older and outdated. I couldn't find a perfect solution, but I'm addressing it in the next release.
Let me know if the error goes away for you, please.
Another thing to try, though, is a plugin manager that will let you activate or deactivate plugins depending on the page. That way you could have both plugins without conflicting, because both would not be active on the same page.
Since v191022 all s2member Stripe payments fail at Submit Form with onscreen error:
The site is experiencing technical difficulties
and in logs:
PHP Fatal error:
Cannot declare class Stripe\Stripe, because the name is already in use in
/home/xxxx/public_html/wp-content/plugins/s2member-pro/
src/includes/classes/gateways/stripe/stripe-sdk/lib/Stripe.php
on line 11
Disabled another plugin which hadn't changed to make sure the more important s2member is now working. So yes, this is a plugin conflict, but is 'stripe' the wisest class name?
The text was updated successfully, but these errors were encountered: