Support

January 16, 2019 at 2:37 pm

Hi there,

You currently have WP Fastest cache enabled on the site and it’s caching the EE event pages with the ticket selector on, have you added the /events/ path to your exclusions?

January 16, 2019 at 4:46 pm

The “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.” error is from a simple check within Event Espresso based on time.

When the ticket selector is generated it adds a timestamp to the page, without going into too much details EE uses that timestamp to tell if a bot is submitting the form.

However, if the page is cached the tickt selector will have an ‘old’ timestamp in the cache, when the tickets are the submittied Event Espresso sees the timestamp is old and rejects the submission. The reason for this is to prevent bots caching the page and continually submitting ticket selections.

So to get the above error you need to either submit the ticket selections really quick after loading the page, or have an old timestamp that is outside of what EE expects, as your page is caching, that’s your problem.

No I haven’t. Do I simply add /events to the exclusions? I’ll give that a shot.

You’ll need to exclude any of EE’s pages from the cache, we have some details on this here:

https://eventespresso.com/wiki/setup-nocache-exclusion-rules-event-espresso/

Did you purge the cache after excluding?

Is there anything else that would cause the issue? Could it be a server related issue?

Do you have server-side caching as well as WP Fastest cache?

I know event expresso uses a lot of resources. It is prime registration season and can’t afford for it to keep going down.

When has EE gone down? The above issue isn’t from EE ‘going down’, its function as expected but caching EE’s pages will cause issues.

Added the exception and still getting server time out issue

Did you purge the cache afterwards?

In the latest version of Event Espresso (4.9.76.p) we’ve remove this timing check so if you update to that latest version if should prevent that error, however, you will still need to exclude EE’s pages from caching.

January 17, 2019 at 7:06 am

You can also contact your web host and ask them to update your server to use a supported version of PHP. PHP 5.6 has reached “End of Life” and PHP 7 (recommended) is much faster. You’ll likely notice a significant improvement to your site’s load times after updating to PHP 7.