Posted: February 14, 2022 at 10:14 am
|
My client just opened her first event using your system on Saturday and has gotten multiple emails from customers saying that they aren’t able to check out. THey get a message that zero tickets are available but only 1 ticket is in the event queue. I double checked the quantities to be sure it wasn’t an issue with stock, and there are plenty of spots available and no reserved spots being held. Help? My client is getting frustrated! I have the latest Event Espresso 4 installed. |
Hi there, Can you post a link to the event, please? |
|
|
Single Event page is here: Calendar is here: |
Ok, the issue is due to caching. Are you using GoDaddy managed WordPress by any chance? If you try to register onto that single event above whilst logged out of the site you’ll see:
Because the registration checkout page has caching force on it (as does every page). You can’t catch e-commerce requests like those from Event Espresso and that will need to be disabled, depending on your provider I may be able to provide more specific details. If you’re using GoDaddy Managed WordPress you’ll need to contact their support and have them disable the caching in place on the server for you. |
|
|
Yes, it is godaddy managed hosting. I will call them, thank you. And thank you for the quick response! |
Unfortunately, we get so many conflicting answers from GoDaddy support on this that I can’t give you a step by step on what to do. Some support reps have said you can disable the cache, others say you can’t, some disable it only for it to be magically re-enabled a few days/weeks/months later which is why my advice above is to contact them for their ‘latest’ advice. We have details on which pages need to be excluded from the caching here: https://eventespresso.com/wiki/setup-nocache-exclusion-rules-event-espresso/ |
|
|
I just spoke to GoDaddy and the CDN was already off. So that was not the issue. Is it possibly the caching in the wordpress back end that is causing the issue? Can I turn that off? |
|
Or perhaps I need to move the site off of managed wordpress hosting? |
|
I see two caching buttons at the top of my wordpress back end. The first (just called caching takes me to the General WordPress settings page. I see Endurance Caching there. Should I turn that off, or change the level? it’s currently set to advanced (level 3). Then I also have a Managed WordPress button. That has the option to flush the cache. |
Did you ask about the CDN or did they state that? It’s nothing to do with the CDN (Content Delivery Network) as that’s not server-side caching. GoDaddy Managed WordPress hosting packages have server-side caching force on all pages, so for example, see the headers here on your checkout page: https://monosnap.com/file/EdN2clYRF2eYJsoNILYeq2qhhZAuHL Caching is enabled, the page is cachable. GoDaddy is going to tell you that the headers also show that the page has not been cached, but whatever their servers are doing with caching, breaks the checkout when it shows the pages as cachable.
That would be my choice, but I’m not telling you that you need to as you don’t if they can disable the caching on the EE critical page slugs, or the site entirely (they’ve done both in the past). |
|
|
OK, thanks for all the info. I will start by calling them back. The first guy I talked to said the only caching on their side was the CDN. I’ll call back and try to get to someone who knows more! |
Yep, unfortunately the run around you are already getting is not all that uncommon.
Set that to off, save, then flush the cache. |
|
|
GoDaddy said they can’t completely turn off the caching on any of their shared hosting account, and that we’ll have to migrate the site to one of their business plans in order to eliminate caching. So I guess that is what we’ll be doing. |
|
If we were to move the site to a different host, do you have a recommendation for an affordable one that would work with your system? |
That answer changes so often!
There isn’t really anything special about Event Espresso and it should work with any hosting, it’s caching that causes problems. Caching is basically a way to reduce the load on the server, so if you go to Sounds great, until you realise that any e-commerce type requests, (cart checkout, ticket registrations etc) all need to be unique to the specific user requesting it otherwise your not getting what you selected but something else from another user. That’s why the cache needs to be disabled and the error I mentioned above is from EE trying to build out the checkout page based on the data available to it, cached data or not it doesn’t know the difference. We’ve seen users switching to DreamHost, BlueHost and WPEngine (they also have server-side caching but you can request it is disabled for specific pages) but really any hosting will do as long as they are flexible with what can and can’t be cached. (Caching is advertised as a way to speed up your site and that it does, but it’s also a great way to reduce the load required per site on the server, meaning they can fit more sites on a single server, more profit per server. That’s a little simplistic, but you get the idea, its not all about whats best for you and your site) |
|
|
What pages exactly would I need to request the caching to be turned off on? |
We list the details on: https://eventespresso.com/wiki/setup-nocache-exclusion-rules-event-espresso/ The default page slugs for EE4 are:
As long as you haven’t changed them excluding the above should be all you need to do. |
|
|
So I found this info on your site from Lorenzo: Here is a solution that is recommended by Mendel from Godaddy: Login to your WP dashboard and click on Flush Cache which appears on the admin toolbar: http://cl.ly/image/2228341I1P18 If I follow this step and flush the cache, then ask GoDaddy to remove that file, will that fix the issue? Or will it keep happening? |
I can’t answer you here as I don’t have any control over what GoDaddy decide to do. The reason I didn’t give you the above before is due to what I mentioned above. We’ve been told by some reps the above is the correct method, others state it is not. That method was provided by one of their support techs for another user a while back, we advised people to use that method and all of a sudden users started getting hit with sites re-enabling the caching. So, I’m not going to advise you do the above, you need to follow the steps GoDaddy provide for their servers. I’d like to give you a solid solution to this but its completely outside of our control and GoDaddy keep changing their mind on what is and is not an acceptable solution. |
|
|
Got it. We’ll move to another hosting plan then. Better to be safe than sorry! |
The support post ‘Abandoned Cart problem’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.