|
Richard Leino
|
January 9, 2017 at 8:07 am
This is happening for a bunch of users this AM. I recently upgraded EE. Did something change?
I’m using Stripe.
The one thing I’ve noticed about the State Form at checkout (https://www.afcea-qp.org) is that it has multiple entries for Virginia. (va, VA-Virginia, VA.)
I can’t edit this form to remove the values and I suspect that may be the root cause.
|
|
Richard Leino
|
January 9, 2017 at 8:40 am
I don’t think the State field is causing the issue. I found the extra State entries in the DB and removed them. When I go to check out (if not logged in) then there is an HTTP 500 error when I go to Payment.
|
|
Richard Leino
|
January 9, 2017 at 8:53 am
I think it might be a CAPTCHA issue. I disabled CAPTCHA and it is now working. Can you guys check your code to see if something broke in your recent release?
|
|
Tony
|
January 9, 2017 at 9:06 am
I don’t think the State field is causing the issue. I found the extra State entries in the DB and removed them.
That will not be the cause of the problem but you can remove those additional states within:
Event Espresso -> General Settings -> Countries.
Select the country in the dropdown and it will list the states there.
By deleting the values within the DB you will break the contacts that are linked to those ‘duplicate’ entries as they will link to state that no longer exists.
I think it might be a CAPTCHA issue. I disabled CAPTCHA and it is now working. Can you guys check your code to see if something broke in your recent release?
You mean the EE reCAPTCHA settings or another plugin?
Generally the “You have passed a blank string for ‘card’.” error happens with Stripe when there is a JS error being thrown on the page that prevents the submission to Stripe.
Can you re-enable the above so I can view the page with it enabled?
|
|
Richard Leino
|
January 9, 2017 at 9:13 am
You mean the EE reCAPTCHA settings or another plugin?
Generally the “You have passed a blank string for ‘card’.” error happens with Stripe when there is a JS error being thrown on the page that prevents the submission to Stripe.
Can you re-enable the above so I can view the page with it enabled?
I can’t re-enable RE-CAPTCHA right now. I just sent out a big announcment today and registration failed for a dozen users because the plugin was broken.
In answer to your question, I disabled RE-CAPTCHA for EE only. Before that point, it was displaying the RE-CAPTCHA properly (check mark with I am Not a Robot) and it was taking entries but when I clicked to proceed to payment I was getting an HTTP 500 error. I have been using this form for over 2 years now through successive EE4 upgrades and it just now broke.
When things slow down and I’m not worried aobut having to tell users to re-try registration because we’re trying to troubleshoot then I’ll re-enable Re-captcha. In the meantime, are you sure you guys didn’t break something in your latest release?
|
|
Tony
|
January 9, 2017 at 9:34 am
In answer to your question, I disabled RE-CAPTCHA for EE only. Before that point, it was displaying the RE-CAPTCHA properly (check mark with I am Not a Robot) and it was taking entries but when I clicked to proceed to payment I was getting an HTTP 500 error. I have been using this form for over 2 years now through successive EE4 upgrades and it just now broke.
Ok, but is the reCAPTCHA form you are using the one from within EE or another plugin?
To disable it did you use the settings within Event Espresso -> Registration Form -> Reg Form Settings?
In the meantime, are you sure you guys didn’t break something in your latest release?
I’ve tested for this on multiple test sites to confirm I could not trigger the same problem.
If you check within your servers error logs you should find what was causing the error 500 there, if you post the error it will help narrow this down some.
|
|
Richard Leino
|
January 9, 2017 at 9:42 am
Ok, but is the reCAPTCHA form you are using the one from within EE or another plugin?
Within EE.
To disable it did you use the settings within Event Espresso -> Registration Form -> Reg Form Settings?
Yes. Disabled there.
I suspected CAPTCHA because it worked fine for me (I was logged in) but then I check from a browser not logged in and it failed. Logged in users aren’t given the CAPTCHA option.
[09-Jan-2017 15:23:06 UTC] PHP Fatal error: Call to a member function toggle_failed_transaction_status() on integer in /mnt/stor20-wc2-dfw1/435600/www.afcea-qp.org/web/content/wp-content/plugins/event-espresso-core-reg/modules/single_page_checkout/reg_steps/payment_options/EE_SPCO_Reg_Step_Payment_Options.class.php on line 1745
[09-Jan-2017 15:29:57 UTC] PHP Fatal error: Call to a member function toggle_failed_transaction_status() on integer in /mnt/stor20-wc2-dfw1/435600/www.afcea-qp.org/web/content/wp-content/plugins/event-espresso-core-reg/modules/single_page_checkout/reg_steps/payment_options/EE_SPCO_Reg_Step_Payment_Options.class.php on line 1745
[09-Jan-2017 15:30:25 UTC] PHP Fatal error: Call to a member function toggle_failed_transaction_status() on integer in /mnt/stor20-wc2-dfw1/435600/www.afcea-qp.org/web/content/wp-content/plugins/event-espresso-core-reg/modules/single_page_checkout/reg_steps/payment_options/EE_SPCO_Reg_Step_Payment_Options.class.php on line 1745
[09-Jan-2017 15:35:08 UTC] PHP Fatal error: Call to a member function toggle_failed_transaction_status() on integer in /mnt/stor20-wc2-dfw1/435600/www.afcea-qp.org/web/content/wp-content/plugins/event-espresso-core-reg/modules/single_page_checkout/reg_steps/payment_options/EE_SPCO_Reg_Step_Payment_Options.class.php on line 1745
[09-Jan-2017 15:35:54 UTC] PHP Fatal error: Call to a member function toggle_failed_transaction_status() on integer in /mnt/stor20-wc2-dfw1/435600/www.afcea-qp.org/web/content/wp-content/plugins/event-espresso-core-reg/modules/single_page_checkout/reg_steps/payment_options/EE_SPCO_Reg_Step_Payment_Options.class.php on line 1745
|
|
Josh
|
January 10, 2017 at 8:37 am
Hi Richard,
The reCaptcha module within EE hasn’t changed in quite some time, but the reCaptcha API does change (we have no control over that). A better way to prevent spam on your site is to use the Blackhole for bad bots plugin.
Also, you can try the setting that encodes the registration session data. This can prevent fatal errors on some servers. It’s recommended to try this setting during off-peak registration times just in case your server doesn’t allow using base64encoding (some of the cheaper shared hosts don’t). You can set Event Espresso to encode session data by going to Event Espresso > General Settings > Admin Options and set Encode Session Data to Yes, then save. After you save this setting, it’s important to test a registration to make sure your server supports encoding data.
|
|
Richard Leino
|
January 10, 2017 at 10:53 am
Just to be clear, are you telling me that, because the reCaptcha API has changed that your plugin no longer supports reCaptcha?
I’m just making sure I understand the advice: Do not use the option that you provide within EE for ReCaptcha.
|
|
Josh
|
January 10, 2017 at 11:03 am
No I’m not saying that. EE still includes and offers reCaptcha as an option, and the reCaptcha module works as expected on our testing servers. We do not guarantee that the reCaptcha API is compatible on all web servers though. So to be clear, the reCaptcha module may not be compatible with your web server. In which case you can use another method to prevent spam.
|
|
Richard Leino
|
January 10, 2017 at 11:57 am
Have you tested this:
1. User is not logged in to your WordPress site.
2. User has to use re-CAPTCHA before payment.
3. User initiates and completes payment using Stripe
|
|
Josh
|
January 10, 2017 at 1:48 pm
Yes we most certainly have. Have you tried changing the setting for Encode Session Data to Yes?
|
|
Richard Leino
|
January 10, 2017 at 3:05 pm
Not yet. For now, I’m OK with disabling Re-CAPTCHA. Thanks for the tip on the Blackhole plugin.
|
