Persistent caching using files. WARNING: PHP 5.1.6 or newer is required.
DOES NOT support WordPress MultiSite.
| Author: | Vladimir Kolesnikov (profile at wordpress.org) |
| WordPress version required: | 2.6 |
| WordPress version tested: | 3.1.4 |
| Plugin version: | 1.2.9.1 |
| Added to WordPress repository: | 12-02-2010 |
| Last updated: | 16-12-2010
Warning! This plugin has not been updated in over 2 years. It may no longer be maintained or supported and may have compatibility issues when used with more recent versions of WordPress.
|
| Rating, %: | 70 |
| Rated by: | 2 |
| Plugin URI: | http://blog.sjinks.pro/wordpress-plugins/wp-f... |
| Total downloads: | 43 952 |
| Active installs: | 700+ |
 Click to start download |
|
The plugin implements object level persistent caching and can be used instead of the built in WordPress WP_Object_Cache.
Unlike WP Super Cache, Hyper Cache and other plugins, WP File Cache does not cache the entire page; instead, it caches the data WordPress explicitly asks it to cache (using wp_cache_xxx() API functions).
Although this means that the performance will be less than with, say, WP Super Cache, all your pages remain dynamic.
WP File Cache won't help you much if the plugins or theme you are using do not use WordPress Cache API. This is by design, since the plugin tries to play nice. However, for most WordPress installations this will not be critical.
WP File Cache significantly reduces the load from your database. Say, my blog's home page without the plugin executes 24 queries (0.02403 sec); with the plugin enabled, only 4 queries (0.00188 sec). Unlike DB Cache/DB Cache Reloaded, the plugin will work in the Admin Panel and supports all plugins that use WordPress Cache API.
Please note that WP File Cache shifts the load from your database to your disk/file system and if Disk I/O is a bottleneck, file based caches will not help you.
To get the maximum cache performance, please disable open_basedir in your php.ini — it really slows the things down.
WARNING: chances are that the plugin will not work when PHP safe mode is enabled and web server is operated by a different user than owns the files.
FAQ
ChangeLog