|
jfchatelain
|
March 28, 2017 at 8:44 pm
Hi, Some of my users are receiving 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.
This seems to happen when they go through stripe payment. The transaction fails and the user gets this error message.
No sure exactly what is causing that.
Can you help me on this?
Thanks
|
|
Tony
|
March 29, 2017 at 5:04 am
Hi there,
That error usually means there is a JavaScript error on the checkout page which prevents the details being passed over to Stripe.
Is there a test event I can use to view this?
|
|
jfchatelain
|
March 29, 2017 at 2:07 pm
Hi,
what is weird is that I just created a test ticket only visible to admin and bought it and there was no error. This is an intermittent problem.
Do you know if the problem is when submitting the payment to stripe? I guess yes since there is a transaction that is created.
Also, I’ve noticed multiple transaction for the same registration with that error.
our site is https://billets.sommetmondialdesign.com
Thanks for your help.
|
|
Josh
|
March 29, 2017 at 2:20 pm
It looks like your server is serving the Event Espresso checkout pages from a varnish cache. Here’s a screenshot:
https://www.evernote.com/l/AASq6Ej9ANtJv4Vhnkxq8M4XXOwKQQoRwV0B/image.png
Can you reach out to your host and check to see if that caching can be excluded on the pages that handle Event Espresso’s checkout?
|
|
jfchatelain
|
March 29, 2017 at 2:25 pm
Ok, I host on a VPS but i’m afraid that contacting my host will start an endless discussion. Can you tell me what is that header and what should it be?
I will contact my host anyways, but i will also do research on my side.
Thanks again for your help.
JF
|
|
Josh
|
March 29, 2017 at 2:32 pm
You shouldn’t see any headers that say it’s being served via the Varnish cache on Event Espresso checkout pages.
Here are a few resources that may help:
http://stackoverflow.com/questions/13964351/excluding-a-specific-url-from-varnish-cache
http://stackoverflow.com/questions/13191828/varnish-exclude-url
|
|
jfchatelain
|
March 29, 2017 at 2:38 pm
Thanks
We recently added this code in our functions.php:
function wpse_84670_time_as_version($url) {
return add_query_arg(array('ver' =>$version), $url);
}
add_filter('script_loader_src', 'wpse_84670_time_as_version');
add_filter('style_loader_src', 'wpse_84670_time_as_version');
That was to force the reload of javascript and css when deploying.
unfortunately I can’t reproduce the error on my side.
We just removed that code. Can you tell me on your side if you still see the Http Header: 1.1 Varnish?
Thanks again for your precious help.
JF
|
|
Josh
|
March 29, 2017 at 2:57 pm
You’ll need to be logged out of the website to experience the issue, and removing the code that you just removed isn’t going to fix the caching issue.
If you log out of the site, then go to an Event Espresso page on your site, then open up Chrome Developer tools (or Firebug for Firefox) then click on the network tab and refresh, then click around, you’ll see all of the http headers, which currently indicate the site is being served from a Varnish cache.
|
|
jfchatelain
|
March 29, 2017 at 4:06 pm
I noticed that thi info comes from a response coming from stripe. Which is the file checkout.js (from checkout.stripe.com).
Would that mean that stripe is using vanish? I guess so since there is no response with that header coming from my server.
Let me know your thoughts.
Thanks
JF
|
|
Josh
|
March 30, 2017 at 8:41 am
I think you’re correct. It’s still wise to check for caching issues since you’ve observed that this is a sporadic issue. It may even be an issue with browser caching, in which case this plugin will help:
https://wordpress.org/plugins/busted/
|
|
jfchatelain
|
March 30, 2017 at 9:03 am
Thanks Josh,
regarding the others post about javacript error. From your experience, were those javascript errors visible before the payment. I mean in the checkout page or they happened during the payment process?
Thanks
|
|
Josh
|
March 30, 2017 at 9:24 am
The JavaScript errors would happen either on the page load or when they click on the button to initiate the payment.
|
|
jfchatelain
|
March 31, 2017 at 7:11 pm
Hi, I’ve installed the plugin you suggest and asked my user to retry to buy his ticket but unfortunately this is still happening.
I tried on my side and we can see that other users can buy their tickets without any problems.
Do you have any other suggestions for me?
Thanks
Jeff
|
|
jfchatelain
|
April 3, 2017 at 9:17 am
If that could be of any help, here’s the transaction where the user had the error from stripe:
https://billets.sommetmondialdesign.com/wp-admin/admin.php?page=espresso_transactions&action=view_transaction&TXN_ID=1366&view_transaction_nonce=56966d4f91&return=view_registration
Thank you
|
|
Josh
|
April 3, 2017 at 12:56 pm
Hi Jeff,
Can you ask the individual that reported the error to visit:
supportdetails.com
and forward their browser info?
Then you can send along that browser information in the redeem a support token form, and please be sure to include valid FTP information with that form. We’ll need the FTP information to be able to check the debug logs.
|
|
jfchatelain
|
April 3, 2017 at 2:38 pm
Hi,
I just hung up with the user and was able to find the issue. Like mentioned by you guys it was a Javascript error that cause this error.
The problem is now solved. We can close this ticket.
Thanks for your help.
JF
|
