|
Brett Stallings
|
January 23, 2019 at 10:52 pm
I am getting reports of a server timing issue warning. The reports are only coming from students registering from South Africa and no issue with those in the US.
The error reads…. “We’re sorry, but your ticket selections could not be processed due to a server timing error. Please hit the back button on your browser and try again.”
We are using WP-Fastest Cache and I had only excluded the /registration-checkout/ page from caching. Now after reading another support article I have also excluded the following pages. Is there anything else I need to do to resolve this issue?
My next course of action would be to disable the Bot Trap but I’d rather not do that so we can keep the spam sends to a minimum. I have read about disabling the Bot Trap’s Encrypt Bot Data Feature first and then trying the other setting.
Please advise as to your thoughts. Thanks!
/events/
/registration-checkout/
/event-registration/
/transactions/
/thank-you/
/registration-cancelled/
|
|
Brett Stallings
|
January 23, 2019 at 11:04 pm
I located a help topic from a prior discussion regarding this error and realize that I had failed to put this new events page under the parent URL which I had specified in my rule with WP-fastest cache. As Josh instructed me previously I need to include all of my custom course pages in the exclusion. I think this may solve my issue. I am goin to have another South African student test now with the changes to my caching exclusion.
https://eventespresso.com/topic/server-timing-error-message/
If that does not work is my next course of action the Bot Trap disabling?
|
|
Tony
|
January 24, 2019 at 4:03 am
Hi there,
I can see you are using the latest version of Event Espresso on your site currently, were you using that version previously?
The reason I ask is we’ve made some changes to how that detection works and that specific error no longer exists in EE anymore.
Removing the ticket selector from caching should also have prevented the above error.
|
|
Brett Stallings
|
January 25, 2019 at 12:23 pm
Hi Tony!
I updated to the latest version of EE just after we got the error just to get everything with our setup current. We have had several successful registrations now that the caching adjustment was made so that seemed to be the source of the issue. Thank you very much for your follow up. I believe we have this issue resolved. Have a great day!
|
|
Tony
|
January 25, 2019 at 12:58 pm
Great! I’m glad it’s working.
Same to you 🙂
|
