|
jbitman
|
December 20, 2021 at 6:59 pm
If you are NOT logged into the WordPress back-end of the site, and try to register for events, it will go to the cart, and message that it is empty. You can this event here as an example:
https://sandamiano.org/events/new-years-retreat-let-us-begin-again/
If you are logged into the WordPress back end, and log in, things will progress as expected. This might lead me to believe that it is javascript library related, but I don’t know.
We changed web hosts from Dreamhost to WPEngine on December 13th, and that is when this issue started occurring. Donations through WPGive work just fine, but Event Espresso Events are essentially down. In my support ticket, I said the previous host was HostGator, but that was incorrect.
Thank you,
Jason Bitman
|
|
Tony
|
December 21, 2021 at 4:31 am
Hi Jason,
We’ve received your support token request, however, as your using WPEngine this isn’t something we can fix for you as you’ll need to contact them.
To explain, WPEngine forces server-side caching on all pages by default and you’ll need to exclude the EE critical pages from that caching which we have documentation for here:
https://eventespresso.com/wiki/setup-wpengine-hosting-event-espresso/
So in short, open up a ticket with WPEngine and ask them to exclude the pages listed in Event Espresso -> General Settings -> Critical Pages (if you haven’t changed those pages the slugs in the doc above should work) and the above issue should stop.
The reason it works when logged in vs logged out is logged in users aren’t server cached responses from the server.
|
|
jbitman
|
December 21, 2021 at 11:25 am
Tony,
Here is the response from WPEngine on the heartbeat:
Heartbeat on our platform is by default limited to every 60 seconds on editing pages. Are you looking to enable it on non-editing pages (pages and posts you are not editing in WP Admin)?
Do I need the heartbeat on non-editing pages?
|
|
Tony
|
December 22, 2021 at 3:11 am
Yes, but only one for Event Espresso.
You’ll need it enabled on the thank you page which on your site appears to be:
https://sandamiano.org/thank-you-2/
|
