Posted: January 15, 2023 at 5:03 pm
I spent some frustrating time this morning activating and deactivating all my plugins. Sometimes after deactivating EE4 and the Braintree gateway the no-cache situation would go away and all would be good, but sometimes that wasn’t the case. I never did find a combination of active and deactivated plugins that would work or not work all the time, so I went back to DreamHost and asked for further data. In response, they tell me they believe the problem comes from EE4. I’m going to paste their response below for your analysis, as this appears to be well beyond my capabilities as a user.
Thank you for reaching back out to us. Sorry to hear you’re still having
And from what I found out, the Event Espresso plugin is the one creating
From there, you can also check its cookie with the plugin developer, so
I would recommend having them check
When testing the site via SSH using the curl command while the plugin is
But when the plugin is deactivated, it shows the following result after
Kindly provide them the details above, to help them check which cookie
Once cleared, you can then test the server cache by using the curl
Yes, we set a no-cache cookie when using Event Espresso.
Originally we tried to restrict that to only happen on specific pages, however, we ran into multiple issues where sessions were being wiped on X requests and breaking registrations.
ummm….that’s stunning. So making our entire site never cached when EE4 is active is the best solution? I don’t recall that being disclosed anywhere – did I miss something? Seems like a situation that would make a lot of us admins unhappy.
When Event Espresso shortcodes can be placed literally anywhere on the site and loaded in ways we can’t detect prior to the page loading, yes. It’s either that or the admin runs into issues with sessions breaking and registrations stop working with the current setup.
You can’t cache eCommerce requests so no, no disclosure as such. For Event Espresso to function the requests for each individual user can not be cached.
I’ll open a discussion to see if we have any plans to change this in the future.
Ok, thanks. You can call this one closed.