|
Brett Stallings
|
July 11, 2018 at 10:23 pm
I am receiving feedback from users in the UK. I however am testing from the US and when I hit the register button I can process my registration just fine. Are you aware of any reason UK visitors would be experiencing server timing out error message issues when clicking the register button on our events?
https://www.statscamp.org/london-camp/meta-analysis-statistics-course
|
|
Brett Stallings
|
July 11, 2018 at 10:26 pm
“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.”
|
|
Tony
|
July 12, 2018 at 3:54 am
Hi Brett,
I’m from the UK and get the error, may I ask, when testing are you logged in or out of the site?
The issue with the above is usually due to caching, which will not be active when you are logged into the site.
|
|
Brett Stallings
|
July 12, 2018 at 10:11 am
Hi Tony,
Thank you very much for confirming. Yes, when testing I am logged into the site. I will run a few tests here shortly while not being logged in. Please let me know if you have any additional insight. Should I turn caching off? I am using Wp Fastest Cache plugin.
|
|
Brett Stallings
|
July 12, 2018 at 10:33 am
I just ran a test using Chrome on a Mac while logged out and the registration went through fine. I did not change anything about the caching or site configuration. Just a straight test. Thanks.
|
|
Brett Stallings
|
July 12, 2018 at 10:34 am
Sorry must have been cached in chrome. I did a test using Safari in a private window after history was cleared and it showed me the error as well. I am going to try to disable caching and see if that fixes it.
|
|
Brett Stallings
|
July 12, 2018 at 10:40 am
I added a rule to exclude /registration-checkout and /thank-you from the caching. This seems to have fixed the issue. Is there any other pages vital to EE that I should add to this rule? Thanks.
|
|
Josh
|
July 12, 2018 at 11:38 am
Any page with the ticket selector shortcode or ticket selector, usually has the slug /events/ in the URL.
|
|
Brett Stallings
|
July 12, 2018 at 11:41 am
Thanks Josh! I am not using any of the auto generated /events pages. I put my ticket selector inside a wordpress page via the short code. Would that apply to these pages? Example: https://www.statscamp.org/london-camp/missing-data-analysis-statistics-course
|
|
Josh
|
July 12, 2018 at 11:58 am
Yes. The reason is because if the ticket selector is served as part of a stale cache, there’s the potential of all kinds of weird errors. Like the server timing error. There’s also the potential of serving a stale page where the tickets might appear to be still available, but they’re no longer on sale. The best defense for this is serve those pages dynamically. They may load a bit slower, but they’ll be up to date and current.
|
|
Brett Stallings
|
July 12, 2018 at 1:30 pm
Thank you very much Josh! I appreciate the help. I will include those in the cache rule. Hope you have a great day!
|
|
Brett Stallings
|
July 13, 2018 at 9:48 am
I received feedback this morning form a few customers who are still having the issue in the UK. I made a few adjustments. Curious if you guys have anyone such as Tony in the UK that can try again for me and let me know if they receive the server timing warning or not. Thanks!
https://www.statscamp.org/london-camp/missing-data-analysis-statistics-course
|
|
Tony
|
July 13, 2018 at 9:55 am
Hi Brett,
I just tested again and didn’t get any errors.
Are the saying they get the exact same error?
|
|
Brett Stallings
|
July 13, 2018 at 10:50 am
Thanks Tony! Yes, I believe it was my fault for setting the rule in WP Fastest Cache wrong. This morning I changed all rules to be “Starts With” instead of “Is Equal to” and it looks like it now has the (.*) at the end of each rule indicating it is covering all variations under those rules. I appreciate you checking this out for me again. I believe that should do it.
|
|
Tony
|
July 13, 2018 at 10:58 am
No problem at all 🙂
Please do let us know if you run into any more problems.
|
