Lone Shooter

Hi Frederick,

Here are answers/comments to your questions:

“What are your settings for BrowserCache HTML expiration time?”

– Some sites have the expiration time set to 3600 sec but some of them are with Browser Cache turned off. The behavior is the same.

“The plugin checks if file is older than current time minus 5 times the expiration time before it deletes the .old files during the garbage collection run.”

– As I can remember, three or four release ago this didn’t affect the cache file deleting if it was started manually (Performance -> Empty All Caches). In that case all files were removed no matter what the expiration time were. Is this changed in last few releases?

“Also what value do you have under garbage collection interval on Page Cache settings page?”

– Some sites have 3600 sec but some of them have values less than 1000. The behavior is the same.

“Do you have any issues with scheduled posts since both that and the garbage collection relies on wp-cron?”

No, I don’t have any issues with scheduled posts. They are published

Please consider the following:

– The issue with cached files exists no matter of environments. Sites are hosted on different hosting providers with different environments (shared, dedicated, Centos, Ubuntu…). Tried with different W3TC options but it didn’t help.

– Manual deleting cache (Performance -> Empty All Caches) used to work before two or three latest versions, i.e. after manual deleting the cache files on disk were removed. Now, the manual deleting doesn’t delete the cache files located in /wp-content/cache/page_enhanced/%sitename%

No, the problem is not fixed. If you use enhanced disk caching, the cache files are just stay there causing increasing number of inodes during the time. For some reason they can’t be deleted with Empty Cache feature even the cache folder’s permissions are valid.

Yes, it definitely causes the problem on shared hosting. In fact, I already have a lot of problems because of blocked accounts. The only solution so far is to use cron jobs on daily base to clean cache files.

Unfortunately, I didn’t find solution and what causes it although this problem exists since two versions ago.

This is the bug. W3TC doesn’t remove enhance-cached pages anymore from some reason; even when Empty All Caches is performed manually. I needed to create cron jobs that delete the cache folder so you could do this..

Note: the bug is also present in the last v0.9.2.9!

@bigdrobek, the permissions are not cause of the problem. My websites are a couple of years old and the issues with cache files exist although folders rights are valid.

@daniel, if you had read what I wrote, you could have seen that I did all of these. In short the plugin worked good before v0.9.2.8, and now it crates thousands of files without possibility to delete them (except manually).

@QuickSolution, the solution you provided doesn’t work anymore, it was successful only with the earlier W3TC version. Here is the comment from the author of the config file

…Update 10 March 2013: W3 Total Cache has released a few new versions since this was written and they now use a different config file layout, so this is probably obsolete…

[sig moderated as per the Forum Rules]

The same issue here. I have a site with several thousands posts and in a single week (from the last plugin update) more than 200.000 inodes were created. I noticed that the upgrade overwrote the original configurations so I configured the W3TC again (disabled db and object cache, turned on disk enhanced cache etc.) but the issue still exists. Many thousands of inodes are created every day.

To be worse, feature for cleaning all caches seems doesn’t work at all. Before this last version, I was able to go to Performance > Empty All Caches and all cached files would be deleted. Now, I need to clean wp-content/cache/page_enhanced folder manually or via cron job every single day in order to prevent cancellation of my account due to the huge amount of inodes.

Is there any fix for this problem or I need to change cache plugin?