|
botanicwise
|
March 2, 2020 at 6:37 am
We are using SG Optimizer on our site for caching. I’ve excluded the necessary pages from cache, but I noticed that caching was not working generally across the site even though it was enabled. I contacted Siteground about it. They escalated it to their engineers who are saying that there is a conflict with event-espresso-core-reg.
They requested that I reach out to find out if you are aware of any specific configuration that needs to be made to prevent the conflict.
|
|
Tony
|
March 2, 2020 at 6:42 am
Hi there,
Did they provide any more info on what the conflict actually is?
I’m not aware of any issues with Event Espresso conflicting with SG Optimizer other than the fact that you need to exclude EE’s critical pages from caching.
|
|
botanicwise
|
March 2, 2020 at 11:01 am
They did not, but I have requested more details from them. In this support case (https://eventespresso.com/topic/checkout-error-when-using-cache-plugin/), Josh mentions some constants that are used. Is this still the case and should I bring this up with Siteground?
|
|
Josh
|
March 2, 2020 at 11:10 am
Those constants are still set by Event Espresso, it’s up to caching plugins whether to respect those.
|
|
botanicwise
|
March 9, 2020 at 5:06 pm
Hi Josh, finally heard back from SiteGround on this issue. Here is what they are saying:
“Our developers advised that the issue is caused by the following header:
cache-control: no-store, no-cache, must-revalidate
The plugin uses sessions and because of this the header cache-control appears our plugin does not cache. You can provide the plugin developer with this information.”
This header should not be affecting the entire site, right?
|
|
Josh
|
March 11, 2020 at 3:12 pm
I can’t say I understand their reply. One thing you could do is use the WordPress nocache_headers filter hook. This hook allows developers to change the cache-control headers.
https://developer.wordpress.org/reference/hooks/nocache_headers/
You may need to set the priority of the callback to a later priority (e.g. 11 or 99 or if need be higher) if there are other plugins hooking in to the same filter. EE hooks in at priority 10.
|
