|
David Callow
|
September 26, 2014 at 6:47 am
(Using EE4) A customer attempting to buy tickets has mailed me with this error message:
<<<Thanks for coming back to me so quickly.
When I select the number of tickets and hit next it loads the next page with no content in the middle and this message pops up:
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.
EED_Ticket_Selector – process_ticket_selections – 306
It’s happening in IE10 and Google Chrome.>>>
As you can see she has tried two browsers. We have not been able to duplicate the problem-we were sent to Paypal with no problem when we tried the ticket purchase ourselves.
Kind Regards,
David
|
|
Tony
|
September 26, 2014 at 6:59 am
Hi David,
We’re sorry but your request failed to pass a security check.
Please click the back button on your browser and try again.
Usually happens when you are caching Event Espresso critical pages.
Are you running caching either using a plugin or on the server?
|
|
David Callow
|
September 26, 2014 at 7:12 am
Hi,
Thanks for your quick response. I am using Quick Cache! I have just deactivated it-so she could get through now?
Kind Regards,
David
|
|
Tony
|
September 26, 2014 at 7:18 am
De-activating caching plugins generall does not remove the cache they have created.
However, in testing we found that with Quickcache the default setup should skip Event Espresso pages and not cache them (rightly so), have you altered any of the settings being used?
Have you cleared/purged the cache?
|
|
David Callow
|
September 26, 2014 at 7:43 am
Hi,
I’ve just purged the cache and set to default. I had been playing around with the settings. Maybe that was the problem.
Thanks, David
|
|
Tony
|
September 26, 2014 at 7:50 am
I just tested a registration (stopping after being directed to Paypal) without any issues.
I can’t see quick cache at all within the source code now, so I’m guessing you’ve either disabled it, or set it not to include code within the source, but either way, it seems to be working now.
|
|
David Callow
|
September 26, 2014 at 8:33 am
Hi,
Thanks for doing the test. I purged the cache and then disabled the plugin again just in case!
Thanks again,
David
|
|
Tony
|
September 26, 2014 at 9:15 am
No problem.
Just let us know if you have any further problems.
|
