Does new user registration and login clear the Page cache?
Hello @aparnawd
Thank you for reaching out and I am happy to assist you with this.
Can you please share the URL of the page that you see is not cached?
The Page Caching should be disabled for logged-in users. In Performance>Page Cache, make sure to enable the option “Don’t cache pages for logged-in users”. This being said, no this will not trigger the Cache Purge.
One additional note, the page is cached once visited after the cache is purged or after the initial enabling of the plugin.
There is an option in Performance>Page Cache>Cache Preload, which if activated, will preload all pages using the sitemap you provide in the sitemap URL:
I hope this helps!
Thanks!
Hi Marko,
When all does w3 total cache invalidate page cache?
Hello @aparnawd
Thank you for yoru feedback.
This is being handled by the option in Performance>Page Cache, Purge Policy. There you can specify the pages and feeds to purge when posts are created, edited, or comments posted.
I hope this helps!
Thanks!
Hi Marko,
Our cached html files in page_enhanced folder are getting deleted frequently. Can you please help us find a solution for this?
Hello @aparnawd
Thank you for the information.
Once the Page Is cached, it’s created in the page_enhanced/yourwebsite.com/ folder.
for example /some-page/_index_ssl.html
Once the cache is purged, the _old is added to the file /some-page/_index_ssl.html_old which means that the cache is expired and the _old file will be removed with the Garbage collection interval in Performance>Page Cache.
SO W3 Total Cache does not delete the folders, it only deletes the expired files in the time period set by Garbage collection interval.
Thanks!
Hi Marko,
In our case _old is getting added immediately. Cache is not retained. Especially when we access certain /sign-up pages the other page cache files are getting old.
Can you please help us find out the reason for the frequent purging of cache.
Hello @aparnawd
Thank you for your feedback.
_old files are created when the cache is purged.
It’s fine to have _old files. If you always have only _old files – that’s a sign that something is purging the cache all the time.
Some other plugin or theme. There are some plugins like asset cleanup that may trigger W3TC Cache Purge. If you are not updating the posts or adding new articles, W3 Total Cache does not automatically purge the cache.
If you have a Pro version of the plugin installed, You can enable Page Cache Purge Log in Performance>General settings>Debug. Purge Logs provide information on when your cache has been purged and what triggered it.
I hope this helps!
Hi Marko,
Thanks for your assistance. On deactivating Yoast SEO for testing purpose the page cache purging issue got fixed.
Is there a way to make both the plugins work together?
Hello @aparnawd
Thank you for the information.
W3TC and Yoast work great together, however, it appears that something is triggering cache flush in the Yoast SEO plugin.
I would advise reaching out to their support to determine what may be causing this or possibly try out some other plugin for SEO.
Thanks!
