|
TOCIFT
|
June 30, 2022 at 12:40 pm
Hello guys,
This is serious. We are in the last week of registration with half of our sponsors yet to reg. The system is loading information from a different registration on the registration form before I’ve even started to put something in.
I am also still having intermittent issues with the required text. I’m going to turn off all required text, but the other issue is a real problem. Please help!!!
I’m going to use my token.
Thanks,
Laura
|
|
Tony
|
June 30, 2022 at 3:00 pm
Hi Laura,
Just noting here that we have received your support token request for this and replied via email.
|
|
TOCIFT
|
July 1, 2022 at 9:18 am
Tony,
The system seems to be working at the moment. I viewed a Reg form and I don’t see the Industrial Air Tool company name. I did have Hostgator clear the cache.
I would like to leave the ticket open until next week to see if everything is functioning properly.
Thank you for the help!!
Laura
|
|
TOCIFT
|
July 1, 2022 at 11:46 am
Tony,
I just had a customer tell me that another company’s info was on his form. I had to tell him to just put his info over the top. It registered fine, but this is not an ideal situation. I will get a lot of calls with confusion if it continues. I will call Hostgator again, but there had got to be a way to keep them from caching on the EE4 side. I doubt they are going to change the way they are doing business.
Thanks, Laura
|
|
Tony
|
July 4, 2022 at 5:46 am
I will call Hostgator again, but there had got to be a way to keep them from caching on the EE4 side.
Unfortunately, we can’t do more than we already do to prevent caching.
We already do have multiple different cache-busting methods within Event Espresso.
We set no-cache headers, we add a ‘cache busting’ value to the query string (the ?uts=12345678 is nothing more than a method of ‘busting’ the cache) we set no caching constants within our code (a method used by caching plugins to allow others to disable the cache).
So in short, EE literally says ‘do not cache me!’ and if the server ignores that and caches it anyway there is nothing more we can do on our end, it needs to be done server-side.
I doubt they are going to change the way they are doing business.
If they are forcing caching everywhere, they should.
As great as caching is, and yes it can speed up sites, the way it does that is to save/cache a page generated by Request 1 for an amount of time and then serve that generated content to Request 2,3,4,5…..
That’s quicker because it doesn’t need to pull the details in from the database to generate the page, which in theory is great, but you can’t do that with e-commerce like EE… because each request for the user is specific to that particular user (for example the registration options).
If they are caching every request, they simply can’t tell you that they force caching everywhere and expect for things to work… it can not work that way for anything more than static sites.
To give another example of hosts doing this, WPEngine forces server-side caching on all of their servers by default. They acknowledge the fact that forcing server-side caching isn’t an option for e-commerce and allow you to exclude pages from the cache… which Hostgator will need to do if they are doing the above.
Forcing server-side caching on all sites and every page is not for your benefit but theirs, more caching means fewer resources required on the server per site, which means more sites per server and in turn higher profit per server.
I’d love to be able to give you a better solution here, but if the server is forcing caching then they need to provide a way to exclude pages from that cache as others do.
|
