|
jschaeffer
|
May 2, 2019 at 9:32 am
Hi I am getting this error when trying to sign up for an event on our webpage. I will link screenshots to show that caching is off.
https://cclonemountain.org/images/no%20cache.jpg
Here is a link to the event sign up page:
https://www.cclonemountain.org/signup/mens-breakfast-may/
|
|
jschaeffer
|
May 2, 2019 at 9:45 am
Currently running Event Espresso 4.9.80.p
|
|
Josh
|
May 2, 2019 at 12:09 pm
Hi,
The screenshots actually shows a different type of caching. Can you contact your host and ask them if it’s possible to deactivate varnish and object caching for that site?
|
|
jschaeffer
|
May 2, 2019 at 2:04 pm
Hi Josh,
I contacted dreamhost and they have confirmed that varnish and all caching has been completely turned off. I am still seeing the error. Is there any further diagnostics that can be done?
|
|
Josh
|
May 2, 2019 at 2:11 pm
They need to make sure that object caching is turned off, that’s a different thing than Varnish. The problem is the object caching stores the WordPress transients outside of the options table, but they need to be in the options table. Here’s another related topic where this was resolved on another DreamPress hosted site:
https://eventespresso.com/topic/no-tickets-can-be-purchased/#post-290787
|
|
jschaeffer
|
May 7, 2019 at 2:33 pm
Hi Josh,
I just wanted to follow up and let you know what DreamHost said.
So DreamHost right now runs two different caching schemes?? I’m not 100% sure. I believe the tech said NGIX and MEMCACHED.
They disabled the NGIX the first time and that didn’t work and my event signups were still broken. He then attempted to shutoff MEMCACHED and once he got that all sorted out he sent this:
… your site is now able to load with
memcached disabled. Transients should now store in the wp_options table
instead of in the Object Cache.
Once MEMCACHED was disabled everything seemed to be fine. He also said they are planning to phase out MEMCACHED soon so this issue for dreamhost should be gone soon.
Thanks Josh I appreciate your patience on this issue.
|
|
jschaeffer
|
May 7, 2019 at 2:34 pm
I could be wrong but I think Varnish is NGIX and then the object caching is MEMCACHED.
|
