|
EastBayDev
|
September 17, 2015 at 6:03 pm
We keep getting these error messages on the web site after users enter their personal information and hit Submit button:
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.
They are then prompted to use the Add to Shopping Cart button, which generates the following message:
It looks like you are attempting to refresh a page after completing your registration or your cart is empty. Please go to the events page and try again.
Users have observed this in two different browsers (Firefox and Chrome).
It also has this message right before the Submit button:
Anti-Spam Measure: Please enter the following phrase Invalid site key. Please see the FAQ.
Not sure why this is happening though I did see a post in the forum from 2013:
https://eventespresso.com/topic/anti-spam-fields-not-verified/
Is swapping out the template files as suggested in the above post the current method to resolve this issue?
Using EE3
|
|
Lorenzo Orlando Caum
|
September 17, 2015 at 6:06 pm
Hi, that does not look like an error that I’ve recently seen reported on our support forums.
Are you running an up to date version of Event Espresso 3?
https://eventespresso.com/wiki/change-log/
Could you provide a link to any event so we can inspect the page for errors?
—
Lorenzo
|
|
EastBayDev
|
September 17, 2015 at 6:38 pm
If I open the page up for registration, our members will try to register.
Are you available to look at it now? I have an event that is not yet published.
By the way, I never saw the error message on my end (Mac) but, several members and guests reported it.
Let me knoow
|
|
Lorenzo Orlando Caum
|
September 18, 2015 at 8:04 am
Hi, could you reply with a link to any event on your site?
Without that link, we won’t be able to see your site.
Thanks
—
Lorenzo
|
|
Josh
|
September 18, 2015 at 9:21 am
Hi EastBayDev,
This error indicates that you need to get a new reCaptcha key and update your reCaptcha keys that were entered in Event Espresso > General Settings:
Anti-Spam Measure: Please enter the following phrase Invalid site key. Please see the FAQ.
There’s more information with a link to register a new key in the reCaptcha FAQ:
https://developers.google.com/recaptcha/docs/faq?hl=en#recently-my-recaptcha-widget-started-displaying-invalid-site-key-whats-happening
|
|
EastBayDev
|
September 18, 2015 at 11:14 am
Thanks Josh and Lorenzo
I deleted the old keys, added new keys.
One more thing, where do I place the script? <script src=’https://www.google.com/recaptcha/api.js’></script>
I used the theme to place it before the closing </head> is that okay?
Here is the page: http://ebwn.org/upcoming-events/
The error is supposed to happen after one selects the Register or Add to Cart buttons. I never did see it so I’ll have to query the users who reported it.
|
|
Josh
|
September 18, 2015 at 12:50 pm
You don’t place the script anywhere, because Event Espresso adds the script when the reCaptcha feature is enabled. It’d be best if you remove what you added so the reCaptcha code is not loading twice on the registration page, and also not unnecessarily loading for every other page on your website.
You can verify if reCaptcha is working by logging out of your site, then try to register for an event.
|
|
EastBayDev
|
September 18, 2015 at 1:05 pm
Great! I logged out and tried to register. The reCaptcha is working. We are testing now.
Members and non members reported seeing the message: “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.”
Members (subscribers) must log in to receive a discount on registration. Unless the reCaptcha is role specific (Editor, Author Subscriber, etc.), I question if members (subscribers) actually saw the message. I never did with the role of Editor.
I’ll close the session as soon as testing is done.
Thanks for your help.
|
|
Josh
|
September 18, 2015 at 1:39 pm
The members may have seen the message if they hadn’t logged in first.
|
