I don’t mean to bump this thread, but I can’t find an “edit” button so I’ll have to make a new post.
I have determined that this problem is definitely being caused by W3 Total Cache. I recently made substantial modifications to my home page (not my WordPress home: the site index, in which I’ve included wp-load.php). I then uploaded the version. Yet despite the fact that a new file had been uploaded, the old index page was still inexplicably showing.
I solved this problem instantly by manually flushing W3 Total Cache. Suddenly, the new page showed up.
This is obviously not an ideal situation: I’m not around to manually flush the cache every time one of my writers publishes a new article. What setting in W3TC could be causing this page to fail to update?
Why are you using wp-load.php directly in your theme? That is definitely not a best practice as it’s a core file.
Hi Frederick,
I’m not using it directly in my theme. I’m using wp-load.php in an external file, in order to display WordPress headlines on a non-Wordpress page. Best practice or not, it’s what a lot of sites do to call on their WordPress content in a directory other than the one in which their WordPress installations are placed. W3 Total Cache didn’t have a problem with this until the last upgrade.
It’s also a fixable problem, because every time I manually flush the page cache, all the headlines show up properly. I just don’t know what setting I should modify so that it flushes without my having to do it manually.
Ok, well this is the first time I’m ever hearing of it any case. Can you submit a bug submission form from the support tab of the plugin please?
Any update on how this was resolved? I had a similar question regarding how W3 Total Cache behaves on external non-Wordpress pages (forgive my cross-posting):
http://wordpress.org/support/topic/w3-total-cache-optimizing-pages-outside-of-wordpress/
I call WordPress via wp-blog-header.php and would just like to know what sort of behavior I should expect from W3 Total Cache in this instance.
To be honest, this one kind of fixed itself. I don’t think it’s a problem inherently in the plugin: I suspect it was caused by the interaction of the plugin with some in-built caching settings in my hosting. The issue disappeared for our website when we moved from one host to another.
@cyril: Thanks for the response. I really appreciate it.
For the external page where you call wp-load.php (or wp-blog-header.php), are you finding that W3 Total Cache is caching or minifying anything else on the page? Or is W3 Total Cache only impacting the WordPress elements that appear on the page?
As far as I can tell, W3TC appears to treat the external page just like any other page as far as caching/minifying is concerned.
@cyril: Thanks. That’s my impression.
I’d love if Frederick could confirm this.
