|
Jake Bingen
|
May 29, 2013 at 11:49 am
Since upgrading to 3.1.32.2.P Recaptcha has stopped working. This applies to Fire/Chrome and IE.
‘Sorry, an error occured and the anti-spam fields could not be verified. Please contact the site admin or click your browser’s back button and try again.’
Once a user submits a form it says this captcha was wrong please try again. Even if the user does not fill out anything on the form and the user receives the captcha error. It appears the captcha is working before the required fields on the form are. This is currently disabled on our site so users can still sign for our classes.
We have WP-reCAPTCHA 3.1.6 installed. The public and private keys match up. Should I get new public/private keys? This is however working on other parts of our website so it does not appear to be Recapcha plugin.
Any ideas why this would have broken with the latest version. I tried a fresh install of this plugin again. Anyone else have issues?
|
|
Dean
|
May 30, 2013 at 12:28 am
Hi Jake,
I can’t really say why that plugin is no longer working, as it is a third party plugin.
Did you know Event Espresso comes with reCAPTCHA built in? It can be activated from the General Settings page.
|
|
Jake Bingen
|
May 30, 2013 at 7:00 am
I deactivated and deleted this 3rd party plugin to see if it was causing a conflict with EE. I thought both were needed to EE to function properly.
I had reCAPTCHA enabled/had public/private keys and this worked in the past. Any other ideas? It seems to be failing right away. Should I reset my keys?
|
|
Josh
|
May 30, 2013 at 8:24 am
Hi Jake,
Can you post a link to a registration page so we can take a look?
|
|
Jake Bingen
|
May 30, 2013 at 8:27 am
Sure I put up a link to one of our classes:
http://www.wonderwaremidwest.com/training?ee=96
|
|
Josh
|
May 30, 2013 at 8:38 am
It looks like the form validation isn’t working at all, which is a separate issue but should be addressed.
Was the form validation working at all before?
|
|
Jake Bingen
|
May 30, 2013 at 8:41 am
Yes this was working before we upgraded to the latest version on browsers.
|
|
Josh
|
May 30, 2013 at 9:25 am
Hi Jake,
I’ve been looking over the source of the page and one thing that I can see that may be causing an issue is the outbound link tracking script that’s getting attached to each link. You might try temporarily disabling the outbound link tracking in the analytics plugin to see if that makes a difference.
|
|
Jake Bingen
|
May 30, 2013 at 9:47 am
Hmm okay. This did not cause an issue before but I can try now…
I disabled the ‘Google Analytics for WP’ 4.3.3 since I could not find a way to disable outbound link tracking within the plugin. This did not make a difference.
Can I disable this ‘outbound link tracking’ in a different way?
|
|
Josh
|
May 30, 2013 at 10:01 am
That’s a question for the Analytics plugin. In this case since you’ve disabled the plugin that’s probably not it. It may take some good old fashioned troubleshooting to find what’s breaking this. This can be done by deactivating other WP plugins and checking the reg form to see if the validation starts working.
If there have been any customizations made to the templates that would be another thing to check.
For what it’s worth, I’ve got a few test sites set up with the newer versions of Event Espresso and the validation and recaptcha are working as expected when I test them. This is kinda of a tricky one because normally when the form validation and recaptcha does not work it will throw errors in the web inspector or in Firebug. I’ve checked your site with those tools and am not seeing any errors though.
|
|
Josh
|
May 30, 2013 at 12:02 pm
I think I may have narrowed things down a bit for you. I ran one of the event pages through the w3c Validator:
http://validator.w3.org/check?verbose=1&uri=http%3A%2F%2Fwww.wonderwaremidwest.com%2Ftraining%3Fee%3D101
and there are some errors in the markup that may be causing the breakage with the form fields not validating. Specifically this one:
Line 222, Column 105: document type does not allow element “div” here
<table class= "training_events_schedule"><div id="espresso-event-id-101">
The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements — such as a “style” element in the “body” section instead of inside “head” — or two elements that overlap (which is not allowed).
One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML’s rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML’s “self-closing” tags for “meta” and “link” in the “head” section of a HTML document may cause the parser to infer the end of the “head” section and the beginning of the “body” section (where “link” and “meta” are not allowed; hence the reported error).
Hope that helps!
|
|
Jake Bingen
|
May 31, 2013 at 7:34 am
The ‘training_events_schedule” is my custom code. However this should just be on this page:
http://www.wonderwaremidwest.com/training not the registration pages.
Training page:
<pre>
<table class= “training_events_schedule”>[ESPRESSO_EVENTS]</table>
[ESPRESSO_CALENDAR show_expired=”true”]
</pre>
The code you mentioned seems to be the default code on the registration_page_display:
<pre>
<div id=”espresso-event-id-<?php echo $event_id; ?>”>
</pre>
|
|
Josh
|
May 31, 2013 at 9:11 am
Hi Jake,
The [ESPRESSO_EVENTS] shortcode generates all the content for all the pages that you go through when you register for an event. This is including the page that uses the registration_page_display.php template.
It might work out better to remove the table markup that wraps the [ESPRESSO_EVENTS] shortcode and create a new page to list out events with [EVENT_LIST]. You could then take the [ESPRESSO_EVENTS] page out of the main navigation and leave it published so the registration process will still work.
So with it set up that way, your customizations will only affect the page that displays the event list.
|
|
Jake Bingen
|
May 31, 2013 at 10:08 am
Josh-
This worked. Thanks for your help I would not have thought of this on my own given it used to work in the past.
Anyways I wrapped the [EVENT_LIST] in the DIV class to apply styling to the table. Then created a new page for [ESPRESSO_EVENTS] and pointed the EE plugin to use this page.
Worked like a charm.
Thanks again for your help.
|
