|
Jonathan P Ledbetter
|
February 17, 2025 at 6:01 pm
I have an issue with EE3. The class registration opened on the website at 5:30pm today. I tested it in two different browsers. I was able to register in Safari and was unable to register in chrome and opera. The error message said:
We are sorry but this event is not yet open for registration.
You will be able to register starting February 17, 2025
I was also on the phone with a co-worker. He could not register on his mobile phone or his laptop using safari.
What could be the reason this is happening?
screen recording: https://streamable.com/50b608
|
|
Garth
|
February 17, 2025 at 7:22 pm
Hi there,
When you see inconsistent behavior, that’s usually a big red flag clue that there is server caching interfering.
When I look at the response headers of your website, I see that the HTTP response summary indicates that the content was served from Cloudflare’s cache (status: HIT), using Brotli compression (content-encoding: br), with a long cache expiration set until March 21, 2025. That means your website is trying to serve outdated information to people.
You will need to: 1) contact your web host for help, or 2) check any plugin or theme settings to ensure they are set to exclude any of your Event Espresso event or critical pages.
== more about caching for anyone else that reads this ==
Serving cached pages (especially with cf-cache-status: HIT and public, max-age=2678400) can be problematic for eCommerce websites because:
1. Stale Content: Users might see outdated product information, pricing, or availability since the cache stores a static version for a long time (in this case, over a month).
2. Cart and Checkout Issues: Cached pages can lead to users seeing other customers’ cart data, checkout pages, or order summaries, which is a serious privacy and security risk.
3.Dynamic Content Not Reflected: Any dynamic elements such as personalized recommendations, discounts, or logged-in user information won’t update in real time if the page is cached.
4. Order Processing Errors: Transactions rely on accurate, real-time data, and caching could disrupt the purchase flow, leading to abandoned carts or failed transactions.
5. SEO Penalties: Search engines might index outdated content, affecting the accuracy of your listings in search results.
Solution: For eCommerce sites, it’s critical to bypass caching on pages like cart, checkout, account dashboards, and product pages that frequently change. Use Cache-Control: no-store or similar headers for these pages to ensure they are always served fresh.
==
So, in short:
1) speak with your host to disable caching for ecommerce pages, like Event Espresso critical pages and Event Espresso event pages.
2) Edit or deactivate any plugins that manage caching.
3) Test. If the problem is resolved then you can confirm the issue is caching.
4) Apply any caching rules incrementally, and test with each change.
Let us know if we can do anything else for you or if you’d find it more convenient to hire us to do this for you.
|
