WP Super Cache

After a html file is generated the webserver will serve that file instead of processing the comparatively heavier PHP scripts.

Installation

You should have the Apache mod mime and mod rewrite modules installed and WordPress fancy permalinks enabled. PHP safe mode should be disabled. If any of those are missing or off you can still use the slower WP-Cache part of the plugin.
If you have WP-Cache installed already, please disable it. Edit wp-config.php and make sure the WP_CACHE define is deleted, and remove the files wp-content/wp-cache-config.php and wp-content/advanced-cache.php. These will be recreated when you install this plugin.
Upload this directory to your plugins directory. It will create a 'wp-content/plugins/wp-super-cache/' directory.
If you are using WordPress MU you will need to install this in 'wp-content/mu-plugins/wp-super-cache/' and the file wp-cache.php must be copied into the mu-plugins directory.
WordPress users should go to their Plugins page and activate "WP Super Cache".
Now go to Settings->WP Super Cache and enable caching. If you see an error message or a blank screen you may need to fix it. See the "FAQ" section later in this readme for instructions.
mod_rewrite rules will be inserted into your .htaccess file.
After you have enabled the plugin, look for the file "wp-content/cache/.htaccess". If it's not there you must create it.

Key features "WP Super Cache":

· A plugin and hooks system. A common complaint with WP Cache was that hacking was required to make it work nicely with other plugins. Now you can take advantage of the simple plugin system built in to change how or when pages are cached. Use do_cacheaction() and add_cacheaction() like you would with WordPress hooks. Plugins can add their own options to the admin page too.
· Works well with WordPress MU in VHOST or non-VHOST configuration. Each blog’s cache files are identified to improve performance.
· Normal WP-Cache files are now split in two. Meta files go in their own directory making it much faster to scan and update the cache.
· Includes this WP-Cache and protected posts fix.
· Automatically disable gzip compression in WordPress instead of dying.
· As Akismet and other spam fighting tools have improved, the cache will only be invalidated if a comment is definitely not spam.
· A “lock down” button. I like to think of this as my “Digg Proof” button. This basically prepares your site for a heavy digging or slashdotting. It locks down the static cache files and doesn’t delete them when a new comment is made.
· Automatic updating of your .htaccess file. (Backup your .htaccess before installing the plugin!)
· Don’t super cache any request with GET parameters.
· Better version checking of wp-cache-config.php and advanced-cache.php in case you’re using an old one.
· Better support for Microsoft Windows.
· Properly serve cached static files on Red Hat/Cent OS systems or others that have an entry for gzip in /etc/mime.types.
· The Reject URI function now uses regular expressions.

Requirements:

· WordPress 2.2 or higher

Limitations:

· If you’re logged in or have left a comment you’ll never see a super-cached page. You’ll see plain old regular WP-Cached pages instead. That’s not so bad since a huge majority of your visitors will never leave a comment.
· Mod Rewrite is used to serve the static HTML pages. As fancy permalinks is also a requirement it should already be installed.
· Some of the more dynamic aspects of your site’s template won’t refresh quite as quickly. For example, recent comment sidebar plugins. Those plugin should use Javascript to load their content instead.
· Some sites have problems serving compressed html files and need extra configuration.
· Don’t expect a cheap hosting plan to survive a major traffic spike, even if it is cached!
· Remember that dynamic content such as that within the sidebar, will only refresh when the cached pages are refreshed. This timeout value can be modified, but cached files will only be removed if you have a healthy mix of static and dynamic requests.
· Some plugins like SK2, Bad Behaviour and others that depend on “fresh” data may not work very well, at least until those plugins support this plugin and clear the cache when required.