|
BeachCitiesvbc
|
April 19, 2019 at 12:43 pm
website link: https://www.beachcitiesvbc.com/events/week-1-summer-camp-july-8th-12th/
register button errors out.
|
|
BeachCitiesvbc
|
April 19, 2019 at 12:48 pm
I wanted to add:
When I try to register it takes me to an error message of “nothing in the event queue”.
|
|
Josh
|
April 19, 2019 at 12:49 pm
Hi,
I checked your site and I can see it’s hosted on WPEngine, which uses a specific type of caching that needs to be excluded for Event Espresso pages. You can contact WPEngine support and ask them to add those exclusions. You’ll find more details here:
https://eventespresso.com/wiki/setup-wpengine-hosting-event-espresso/
Please be sure to ask them to exclude your site’s /register/ page too.
|
|
BeachCitiesvbc
|
April 22, 2019 at 6:16 pm
We’ve had WP Engine update the pages that are excluded with cache, in accordance with the instructions above. We’ve also cleared our cache in Cloudflare. But the issue is still occurring. Any idea what else might be causing the problem?
|
|
Josh
|
April 22, 2019 at 7:09 pm
I mentioned this earlier, but it bears repeating: Did you also ask them to exclude the /register/ page too? That page will also need to be excluded from the cache.
|
|
BeachCitiesvbc
|
April 22, 2019 at 7:44 pm
Yes.
|
|
Tony
|
April 23, 2019 at 2:33 am
Hi there,
Looking at the headers for the /register/ page it still shows as cachable – https://monosnap.com/file/96ysq7bGu3D0iYl1trP9LSOY1vg6vZ
You’ll need to contact WP Engine support and have them exclude that page correctly as currently, it is not.
|
|
BeachCitiesvbc
|
April 23, 2019 at 9:16 am
What constitutes excluding it “correctly”? They have confirmed multiple times that it’s been excluded, so might there be a different method EE requires?
|
|
Tony
|
April 23, 2019 at 9:35 am
What constitutes excluding it “correctly”?
I can’t give you specifics as its their infratructure and I have no control over it, so the ‘correct’ method to exclude a page from caching is whatever they do on their end to exclude the page from caching and right now, the page is showing as cachable.
They have confirmed multiple times that it’s been excluded, so might there be a different method EE requires?
The caching (and exclusion of caching) is actually nothing to do with EE, it’s on their end and all to do with their server. So regardless of what they have ‘confirmed’, the response headers from their server say otherwise.
If I open up your event page and view the headers, I see no caching on the event page itself, see:
https://monosnap.com/file/yNcrYwzdjszurKDauxSPXGi4Tj2Sp6
Then proceeding through to the checkout page:
https://monosnap.com/file/YPvdKF3mvDtdwpxVarXuWd05YLwBDm
See the cache headers, that’s a response from their server to indicate the page is cached. EE already sets no-cache headers and various other ‘cache busting’ methods, yet the server has control and can ignore whatever EE does.
If you send them the above screenshot (taken a few minutes ago), can they explain why the page is still shwoing cache headers, if it’s not cached?
|
|
BeachCitiesvbc
|
April 23, 2019 at 9:53 am
I think we finally got it solved. WPENGINE just told me regens weren’t going through so the cache excludes weren’t sticking. It appears to be working now…
Thanks
|
|
Tony
|
April 23, 2019 at 12:14 pm
Great, so something on their server was ignoring their excludes.
I’m glad it’s working for you now.
|
