|
Brad Richecoeur
|
January 29, 2016 at 2:47 am
Hi
We are having several payment problems for this Event: http://www.qigong-southwest.co.uk/events/bds-summer-camp-deposit (the only Event taking bookings so far). Users cannot process their payments but do manage to register and we receive a ‘Registration Pending Payment notice.
The error message they are getting is:
“You have passed a blank string for ‘card’. You should remove the ‘card’ parameter from your request or supply a non-blank value.”
Is this an issue with EE or Stripe?
Thanks
|
|
Tony
|
January 29, 2016 at 3:32 am
Hi Brad,
The error:
You have passed a blank string for ‘card’. You should remove the ‘card’ parameter from your request or supply a non-blank value.
Is from Stripe themselves, however it is being thrown because Stripe is not being passed over the required details so I would say its on issue on the site rather than Stripe.
Can you temporarily switch to one of the default themes such as twentyfourteen and retest a registration to see if the same error is thrown?
I would recommend creating a full site backup beforehand, just to be safe.
|
|
Brad Richecoeur
|
January 29, 2016 at 6:21 am
OK, thanks I will try this.
Also can you confirm we have the most up to date/correct EE as we were given links to your developer EE install when ww first launched as we were having a complex setup for different payment gateways.
We are using:
Event Espresso: Version 4.8.27.rc.003
Event Espresso – Payment Methods Pro (EE4.6+): Version 1.0.0.dev.000
Event Espresso – Stripe Gateway (EE 4.6.0+): Version 1.0.11.p
Thanks
|
|
Tony
|
January 29, 2016 at 6:48 am
You have the latest version of the Stripe Add-on and Payment Methods Pro, but not Event Espresso core.
The current release version of core is 4.8.32.p
However the release version of core may not be compatible with the Payment Methods Pro add-on, I’ll check in with the developers on this.
Knowing you are using the Payment Methods Pro add-on I suspect this may be a bug with that add-on. Can you explain how you have this events Stripe payment method set up please?
|
|
Brad Richecoeur
|
January 29, 2016 at 7:06 am
Hi
We were told to create a Custom Filed: include_payment_method
And we set up two Stripe payment options: ‘Stripe_original’ and ‘Stripe_two’ which we would then allocate to the relevant Events; and added to the correct ‘Value’ field
We had been taking payments fine for several days though?!
I am getting the client to make a full paid registration to see what error messages come through.
Thanks
|
|
Tony
|
January 29, 2016 at 7:19 am
We were told to create a Custom Filed: include_payment_method
And we set up two Stripe payment options: ‘Stripe_original’ and ‘Stripe_two’ which we would then allocate to the relevant Events; and added to the correct ‘Value’ field
Yes that’s the correct way to set this up, but is this a Stripe_original or Stripe_two event?
We had been taking payments fine for several days though?!
Any changes made between when this did work and now?
If nothing changed this should have continued to work.
I am getting the client to make a full paid registration to see what error messages come through.
You’ll likely find that no errors are shown after that initial error.
The Stripe add-on has to communicate with Stripe to setup a ‘token’ used for all communication, it looks like that is failing on the first page load. If you select Stripe and view the error, then select Stripe again you should be able to make a payment as expected.
So it looks like initially Stripe is not being setup correct, but then after the page reloads it is.
|
|
Tony
|
January 29, 2016 at 7:21 am
Hmm, infact.
That’s now not happening for me (it did with my previous tests) and Stripe is loading fine on the first page load.
Have you made any changes on the site very recently?
|
|
Brad Richecoeur
|
February 9, 2016 at 2:47 am
Hi
I know I am responding intermittently but this issue is occurring intermittently to the point that the client wants to give up as they have no confidence in the system and are spending a lot of their time contacting users who failed to pay for a range of reasons! There seem to be glitches in the whole process and this must be because of the multiple payment add-on bit which seems very unstable. (We have set up a very similar site for another branch of their business – using EE and one payment gateway via Stripe and this works perfectly!)
Users are getting the same message about “blank string…”, also when we send them the payment link to pay they get this issue: “I hit the PAY NOW” button and waited as it reloaded to another page, but it never moved on to letting me pay anything”.
Then occasionally someone manages to go through the whole process and pay!!
So, this particular event is now Full and they are about to release another Event which they held back because of all these issues. Therefore what would happen if we deactivated the ‘Event Espresso-Payment Methods Pro (EE4.6+)’ plugin at this stage so we could just have the single payment gateway? Will this have any impact on the Event that is now sold out and/or the new Event about to be opened for sale?
In desperation…
Thanks
|
|
Tony
|
February 9, 2016 at 4:47 am
Hi Brad,
De-activating the Payment Methods Pro add-on will basically disable any of the additional payment methods you have created using the add-on and leave the default Stripe Payment method your users can use to Pay.
I’ve been digging into this to narrow down the cause and found that this is actually being caused by the payment methods pro add-on itself. The strange part is for me that it only effects some events and not others.
I’ve created a ticket for our developers to investigate this but in the meantime I would recommend de-activating the Payment Methods Pro add-on ad using the single default Stripe payment method. The multi event registration add-on is not causing this and can continue to be used if you prefer.
Can you let me know if you are still using the same version of the payment methods pro add-on you were advised to use HERE, also I would advise updating to the latest version of Event Espresso, the payment methods pro add-on is compatible with the latest version should you wish to use it again (after the above is fixed).
|
|
Brad Richecoeur
|
February 9, 2016 at 5:10 am
Hi Tony
Thanks for your support. We were all up to date last week as far as I’m aware but I will check again; and in the meantime as soon as we are ready we will disable the Payment Methods Pro add-on as you suggest.
|
|
Tony
|
February 12, 2016 at 3:05 am
Hi Brad,
I just wanted to let you know we are working on fix for this.
The Payment Methods Pro add-on highlighted and issue within Stripe when multiple instances of Stripe have been created. The developers have added a fix to the next version of the Stripe payment method that is currently under testing.
Once testing is complete if not other issues are found we will release the update.
|
|
Brad Richecoeur
|
February 12, 2016 at 4:27 am
Many thanks. In the meantime we are deactivating the Add-on and reverting to one payment method via Stripe. However, when I try to ‘delete’ the Custom Field (include_payment_method) within the Events that we are using for the single payment option only, it does not save the deletion? The custom field cannot be removed?
Will this impact on the payment process if we keep the custom field?
Thanks
|
|
Brad Richecoeur
|
February 12, 2016 at 4:45 am
Hi
This system is really becoming a huge pain!
I have deactivated the multiple payments pro add-on but now when I test an event journey to the checkout no payment option appears at all, just the wording “Method of Payment”?
https://www.qigong-southwest.co.uk/events/qigong-summer-camp-deposit
We urgently need to stabilise the system as the client is due to release tickets for this Event this weekend.
|
|
Brad Richecoeur
|
February 12, 2016 at 4:57 am
Ok, sorry ignore the previous email – I had not reset the option to ‘Front-end Registration Page’, sorry!
I would still like clarification about being unable to delete the custom field.
Thanks
|
|
Josh
|
February 12, 2016 at 3:25 pm
The custom field will be ignored if the Payments Pro add-on is deactivated. Usually if custom fields don’t delete like they normally should, that’s an indication that there’s a JavaScript error happening on the page, which may be the result of a theme function or another plugin throwing a JavaScript error.
|
