Page cache not expiring

This is exactly what I am facing, have you found a solution? I have setup a proper cron job to trigger wp-cron and I can see (through the cron view plugin) that the hooks for W3TC are being run (page, db and object) but I don’t get the GC to purge the pages every hour, I have to do that manually. Probably I will end up registering an action to do this.

Please Check this post about a fixed version of w3c total cache here.

I am using the version recommended in this post and have no problems with garbage collection any more.

@antonio I haven’t found a solution yet.

@wp-fan, I’d rather find the root cause of this problem as opposed to just installing another fork and seeing whether it fixes it. The fork you mention seems to have been developed for a different problem.

The fork you mention seems to have been developed for a different problem.

@yousefed: Yes and no. It has been developed to fix other problems, but addresses the garbage collection challenge, too. In my installation, I use preCache-Loading, and I can confirm that garbage collection works 100% .

But of course, people will be interested, if you find a fix for the official version and share it with us…

In my installation, I use preCache-Loading, and I can confirm that garbage collection works 100%

I appreciate your help, but for me its unfeasible to switch to another fork due to maintenance considerations. Also; we probably have a different server+settings setup. I could also solve this problem by switching to another caching plugin (“garbage collection also works in plugin xx”), but I post my issue here to solve the cause of this problem, not to go around it.

for me its unfeasible to switch to another fork due to maintenance considerations.

I understand.

Just for your information: When it comes to update notifications, the fork mentioned above behaves like a “normal” version of 0.9.2.5 . You will be notified instantly if a new “official” unforket version is being released.

It seems to have happened to our sites recently. We have been using W3 Total Cache on WPJEDI and other sites for a long time. Since the last update that fixed the security issue, homepage cache does not update for hours until I manually flush the cache. We have disabled homepage Page caching to get around this for now.

I’m having also same problem after upgrading to latest version on wp 3.5, cache never expire, I have to clean all caches manually.

@strats100 and WPJEDI:

The forked version of wmiles mentioned and linked in my post earlier changes the cache behaviour all together.

It checks the sitemap.xml for new posts and checks wether these files are in the cache or have changed recently. If they have changed recently or have been removed from cache, it will immediately re-cache these pages. It will also rewrite the files in cache before they expire. And garbage collection actually works as it should.

To put it in a nutshell: With this setup, there are pre-cached files present reliably _at all times_ .

My settings:
Gargabe collection interval: 86400 seconds (every 24h)
Cache Preload Update Interval: 300 seconds (every 5min)
Pages per interval: 50 (I am on decent shared hosting, this value works very well in my case).

This setup made my website react 100% faster. With minify enabled and set up correctly and using Amazon Cloudfront as CDN, my site now loads in 1,2 seconds on first call in average (Europe), 2,2 seconds in the US (measured by tools.pingdom.com)

Regards,

Thomas

@wp-fan, is that forked version different from the official update that fixes the security issue with db caching? if so, this is going to be a maintenance problem.

s that forked version different from the official update that fixes the security issue with db caching? if so, this is going to be a maintenance problem.

The author of the modified, repaired and enhanced version, wmiles, says in his release notes that his version is based on the official version 0.9.2.5.
In other words: The security update is included, but he made some enhancements (check the release notes and read the links in his post carefully, you will get the full picture if you read).

I cannot see how this would affect maintenance issues in any way. On the contrary: wmiles version works far better than the official version – for me and other people in this forum.

Good to hear that, the fork I installed was prior to the release of the official 0.9.2.5, although it may have been already out as a dev or nightly version, thanks for clarifying.