Hello @smc2935,
I have carefully reviewed your site and noticed that the object-cache.php file was renamed. In some cases, the file just needs to be recreated manually in order for the Memcached to work properly within the plugin.
Regarding the Automatic Purge functionality not working, our plugin will work if the post’s capability_type is a default WordPress post type. If it uses a custom capability_type, the Automatic Purge function will not be triggered.
Could you perform another test and if the issue still persists, please provide us with more information on how the posts are created.
Thanks for the response.
I’m not sure how the object-cahce.php file would have been renamed. How can I fix that?
The posts are normal posts, not custom post types.
This problem started a couple weeks ago. I’ve been using SG Optimizer for about a year with no problems. Nothing on the site has changed since the issue started, except maybe a plugin or theme update. But I’ve been running the same plugins and theme for months with no problem.
I have fixed the issue with the object-cache.php file and now the Memcached should stay enabled.
Please perform another test on your end and let us know if the Automatic Purge functionality is working now.
Oh gotcha. Thanks.
I’m still having the issue. It’s not showing new posts unless I’m logged into the site.
It appears the issue is caused by the File-Based Caching option which is enabled for your site. The FB cache is not cleared when a new post is created. You should consider manually purging the SG cache or keeping File-Based Caching option disabled for your site.
That worked!
Thanks for the help!
I’m glad to be of service.
Please note that our developers will apply a fix for that issue in the next plugin releases.
Hello @smc2935 ,
We have released a new version of our SiteGround Optimizer plugin that addressed the problems with the Automatic cache purge functionality.
Please update the plugin to its latest version and test if the problems reported would persist.
Best regards,
Georgi Ganchev
Hi @georgiganchev,
The update fixed it. Thanks!