|
Ellimatta
|
July 28, 2016 at 5:15 am
Hi,
I see there are several posts on this topic already going back a number of years but there does not appear to be any solution described.
If I enable the reCaptcha option on the registration form, I get the error below and can’t proceed.
An error has occurred:
A valid transaction could not be initiated for processing your registrations.
EE_SPCO_Reg_Step_Attendee_Information – process_reg_step – 744
I have updated everything, theme, plugins, wordpress, event espresso. Made no difference.
I have tried enabling WP_DEBUG but since updating everything, i get no warnings at all from that.
I do not have any caching plugins.
I do not have any other plugins using reCaptcha.
Does anyone know what actually causes this issue?
Regards,
Mike
|
|
Josh
|
July 28, 2016 at 7:44 am
Hi Mike,
What we’ve found is it’s caused by a mis-configured web server. Most servers will allow using the reCaptcha feature, but we’ve found that some do not. You can disable the reCaptcha option and use this plugin to block registration form spam:
https://wordpress.org/plugins/blackhole-bad-bots/installation/
|
|
Ellimatta
|
July 29, 2016 at 6:03 pm
Thanks Josh,
Do you know what the specific web server config is that causes this?
I use Better WordPress reCaptcha plugin on another site on the same server and that works fine which is interesting.
|
|
Josh
|
July 29, 2016 at 6:22 pm
It’s possibly related to the X-Frame-Options SAMEORIGIN http header.
|
|
Ellimatta
|
July 30, 2016 at 3:47 am
Hi Josh,
I don’t mean to argue, but having X-Frame-Options SAMORIGIN set is not a mis-configuration. It’s a standard security measure to prevent clickjacking.
I would expect a properly coded plugin to work with that, especially when I paid over $300 AUD for it.
I’m also unsure how this setting would affect creating a valid transaction. The setting prevents content from the site being loaded in iframes on other sites? How would this relate to the activity occurring when processing a registration?
Using yet another plugin to work around faults in a paid one, is a disappointing response given this issue has been raised multiple times dating back 2.5 years.
|
|
Josh
|
August 1, 2016 at 7:23 am
Thanks for your feedback.
|
