W3Total Cache, Cannot See Latest Post Fix

Getting the most out of your website requires tapping into all options, which includes making your website as fast as possible. My my case, I was trying to speed up one of my WordPress powered sites, using the W3 Total Cache plugin. It really has made a huge difference and according to Google Page Speed tests, it’s doing awesome. But, I ran into a little problem, I could not view the latest post on my homepage or in my categories. But I found a fix.

My WordPress site in question used a static page to host the latest posts. This is a pretty popular setup, especially among custom themes. In my case I was using DIVI 2.0, by Elegant Themes, and modified the homepage to my liking, including the Blog format. But, while W3 Total Cache was doing it’s job, it was also not allowing the latest post to appear to non-admin viewers.

Getting the most out of your website requires tapping into all options, which includes making your website as fast as possible.  My my case, I was trying to speed up one of my WordPress powered sites, using the W3 Total Cache plugin.  It really has made a huge difference and according to Google Page Speed tests, it’s doing awesome.  But, I ran into a little problem, I could not view the latest post on my homepage or in my categories.  But I found a fix.

My WordPress site in question used a static page to host the latest posts.   This is a pretty popular setup, especially among custom themes.  In my case I was using DIVI 2.0, by Elegant Themes, and modified the homepage to my liking, including the Blog format.  But, while W3 Total Cache was doing it’s job, it was also not allowing the latest post to appear to non-admin viewers.

To fix the hidden post problem, you can either quit using a static homepage or you can disable ‘Page Caching’ in the W3 Total Cache General Settings tab.  In my case, not using a static homepage was not an option, so I simply turned off page caching.  Leaving everything else constant, like browser caching, minify, and others, simply turning off Page Caching fixed my issue.  Now all is well in the world.