|
Ted Harty
|
March 20, 2017 at 12:22 pm
Certain events on my calendar @ https://immersionfreediving.com/pfi-intermediate-freediver-course/
give the following error message when people try to sign up for a course.
An error has occurred:
We’re sorry but your request failed to pass a security check.
Please click the back button on your browser and try again.
There doesn’t seem to be any rhyme or reason why certain classes get this error and other do not.
How do I stop this from happening?
|
|
Lorenzo Orlando Caum
|
March 20, 2017 at 12:45 pm
Hi Ted,
That is from the bot trap. Is this happening for many events or just a couple?
It can be turned off through Event Espresso –> Events –> Registration Form –> Bot Trap Settings:
https://cl.ly/073Y1d272b08
However, it is intended to stop junk transactions from bots.
—
Lorenzo
|
|
Ted Harty
|
March 21, 2017 at 2:01 pm
enable bot trap is set to no.
|
|
Ted Harty
|
March 21, 2017 at 2:03 pm
now the events are registering properly. Bot trap was already set to no. In order to test it was working I had to click on the register button for some events which made some events to sold out. My past experience is that the ticket will not release properly and the event will stay as sold out. I will start another topic on this.
|
|
Ted Harty
|
March 21, 2017 at 2:36 pm
just adding comment to be notified via email.
|
|
Josh
|
March 21, 2017 at 3:56 pm
Hi Ted,
A suggestion that may help you is you can set up an event for testing, then do your testing on that one event. This will avoid the times where you’re testing on your actual events and those tests hold reservations.
|
|
Ted Harty
|
March 21, 2017 at 4:05 pm
The issues I was having was certain events allowed you to sign up with no problems other would give the error message. Didn’t see how to test that other than trying to register for different events that were already on the calendar.
Why would some events trigger this bug and other events not trigger this. I tested across multiple computers and the same events would work and same events would trigger the bug across computers. Now those same events seem to work, but honestly I don’t want to go to try and register for all the events as that will likely mess up the totals.
|
|
Josh
|
March 22, 2017 at 9:45 am
The other thing you can do is after you run your test, you go to Event Espresso > Maintenance > Reset and click on the Reset Ticket and Datetime Reserved Counts button.
|
|
Ted Harty
|
March 22, 2017 at 5:06 pm
Can you explain in detail what will happen when I press the reset ticket and date time reserved counts button?
Sounds scary.
Why were customers and myself getting the error message associated with the bot check when I had the bot check set to off?
|
|
Josh
|
March 23, 2017 at 9:32 am
It’s not scary at all. What it does is set the number of reserved tickets to 0. Normally they should be 0 anyway.
Why were customers and myself getting the error message associated with the bot check when I had the bot check set to off?
I don’t know. It could be a bad cookie in your web browser. Which you can even clear your browser’s cache and cookies.
|
|
Ted Harty
|
March 23, 2017 at 9:46 am
Josh,
Can you explain what a reserved ticket is?
Thanks
|
|
Josh
|
March 23, 2017 at 1:02 pm
It’s a temporary hold for a spot for your event that happens when someone starts a registration. Once they finalize their registration (or if they don’t finalize, 60 minutes passes) the temporary hold is removed and the ticket is moved back into available inventory.
|
