Version 1.2.8 broken site – Just tested

Could you provide error logs? Is there an actual error?

No error on the page, the ACH form is just gone. I didn’t turn on any logging. I can email you screen capture if you want, what’s a good email to send to (rather than posting here).

Found this in my hosting dashboard, this help?

PHP Fatal error: Cannot declare class Stripe\\Stripe, because the name is already in use in /nas/content/live/*******/wp-content/plugins/ach-for-stripe-plaid/vendor/stripe/stripe-php/lib/Stripe.php on line 10

^^ That’s a conflict with another plugin. Do you have other plugins that use Stripe?

Yep, and it’s critical to running business day to day. I’m sure you know of Pippin over at SandHills Dev? This is the plugin:

https://wpsimplepay.com/

I also use:

https://fatcatapps.com/easypricingtables/

To create payment forms. Both are critical to current setup. Any way you can code LittleBot to work around that? I use these on client sites also that I recommended LittleBot to

Oh, one more. Kyle developed this
https://cloudswipe.net/

• This reply was modified 4 years, 6 months ago by crucible67.

Can you disable them and confirm that’s the issue?

EDIT: Correction, ok, I’ve update LittleBot to 1.2.8 and tried turning on/off each of the (3) STRIPE plugins listed above. When CloudSwipe and Easy Pricing Tables are activated, and WPSimplePay is deactivated, LittleBot payment page loads fine now. I refresh, cleared cache, and loading fine. So I’m 99% sure it’s WPSimplePay that is a conflict. I’ve got that installed on many sites so it would be awesome if you can resolve the conflict. Their support team is usually very responsive if needed.

Let us know when it’s resolved?

• This reply was modified 4 years, 6 months ago by crucible67.

update: I’m chatting with Kyle on Drift (CloudSwipe) and he said this:

“Looks like the class “Stripe\Stripe” has been declared already. A common issue when running multiple Stripe plugins. In our plugin, we do check prior to running and do not call if the class already exist as I recall.”

Hope that helps!

Has this issue been resolved? I have the same basic setup as the other user.

Thanks!

Hi @geek2009 – what do you mean same basic setup?

The issue here is there’s another plugin including the Stripe SDK when they are not actively using it. In other words, another plugin is including the SDK on the page where this plugin renders the payment form.

I could check if the SDK is already loaded and that could _potentially_ fix this problem but I’d be trading one issue for another. The new issue would be I’d have no idea what VERSION some other plugin is including on the page potentially breaking this plugin.

Interesting. I see your point. I just sent a support request to WP Simple Pay to see if there is anything they can do.

Thanks!

Hi @jwind my only issue with what you said above if you check for the SDK is you haven’t spent much time making the payment form “useable”. Meaning, it’s email, dollar amount and a note. The user has to enter the amount. My clients don’t get to pick the amount, and, that leaves room to screw things up. So your plugin is ONLY useable on sites that don’t run other popular Stripe plugins? Leaving on Littlebot as a payment method. In my opinion, spending time on code to check for SDK, version, maybe show an error if version is an issue (or something) is worth it. Otherwise this plugin has limited shelf life and a very tiny user base (my opinion). Other Stripe developers have to deal with this, and checking if SDK is loaded. Is there really no way around this?

I won’t argue that the plugin is basic. However, I don’t agree on the second part. A plugin should only include the SDK when actively using it. In fact, I was called out for not following these guidelines due to my conflict conflicting with a popular plugin for not doing this.

https://www.ads-software.com/support/topic/breaking-conflict-with-gravity-forms-stripe-addon-v3-4/

• This reply was modified 4 years, 5 months ago by justinwhall.

Noted. I guess the point here is how do users like me, who really like the plugin and want to use it, proceed with the current (or future) updates when I can’t just turn off other Stripe plugins? Taking payments with WPSimplePay is critical to onboarding clients. Only some are comfortable connecting up for ACH, as you know. I’m not sure how to proceed forward other than making darn sure I don’t install the latest update.