justinwhall

Correct but as I said above, this will not work in your country.

This is for ACH only no card. This plugin gives you a text field to input the amount you want to pay via ACH and that’s it. Also, last I knew, plaid did not support Australia.

That screen shot doesn’t work. I understand it doesn’t get to the second step. What I’m looking for is the error printed to your debug log.

Assuming you have have the correct API keys in the correct place, yes. Can you provide the error that is printed to your PHP or WordPress debug log?

There’s also no harm assuming they don’t conflict.

I do want to be clear here on a couple things:

1) You only need to disable WPSimplePay on the page this plugin runs on. You _don’t_ need to disable this plugin on the WPsimplepay page as this plugin will not interfere with WPsimplepay.

2) I am not looking for a solution. The issue is WPsimplepay includes the stripe SDK when not actively using it and I don’t have control over that.

So your plugin is ONLY useable on sites that don’t run other popular Stripe plugins?

No. But if a plugin loads the SDK when they are not actively using it (they shouldn’t) then yes, the risk of conflict is there (this is not unique to this plugin).

The user has to enter the amount. My clients don’t get to pick the amount, and, that leaves room to screw things up

What exactly are you looking for? Are you wanting to attach payments to users(customers) and send a unique URL to them? Or are simply looking to create more than one form with fixed amounts?

The former can be achieved with my invoice plugin + the ACH addon.

Of note, if this plugin gets cleaned up, I would have no issues paying for it.

In your words, what would that look like? I can’t address other plugins but I can make changes or perhaps make recommendations depending on what you are looking to achieve.

I’m really sorry that it conflicts with another plugin. I would suggest contacting the plugin that is including the SDK while not actively using it. I was contacted for not doing so and made the change to be compatible with a very popular plugin. I would expect that other plugins to do the same.

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

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

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, 7 months ago by justinwhall.

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.

Thanks @cburnsxblucom!

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

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

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

Hmmm, that’s an error from another plugin. I premium one no less. Sort of hard to debug. I’ve released an update that may help?

Regardless, this plugin will soon be deprecated in favor of an addon to LittleBot Invoices. https://littlebot.io/plugins/littlebot-invoices/