1 Blog Cacher

Features

• Quick and easy installation/configuration.
• Cached files are stored in HTML files, and organized in directories emulating the urls (if "safe_mode" isn't enabled), so it's easy displaying the content of the files and organize them (for instance deleting the cache for a given entry, for all categories, for all searches, for all posts from a given date, etc.)
• If "safe_mode" is enabled, the plugin still works, creating all the files in the cache directory.
• Management of HTTP headers, that are saved in .txt files after being conveniently modified, for full cached responses.
• Option to remove all cache files (or just the expired ones) from the WordPress panel.
• Expiration time for cached files.
• Rejected and accepted strings in order to control exactly the urls to cache.
• Rejected User Agents in order to avoid over-caching from search engines.
• Cached files (including front page cache) are updated when posts and comments are published/edited/deleted.
• Option to include a "Expires" header in order to enable browser cache (even fastest response speed and less page requests. Inconvenience: Users won't be seeing their comments after submitting them).
• HTTP header 304 "not modified" returned when it's convenient (less loading time):
  • If the plugin is going to return the same cache (from the same date) to a user, it returns a 304 header instead.
  • Even with a different cache, if the content to return is the same (checked through a Etag header with a hash), a 304 header is also returned.
• Only GET requests are cached.
• Browser super-reload (Ctrl+F5) avoids cached urls.
• Compatible with Gzip compression.
• Support for dynamic code (mfunc and mclude comments) as in Staticize Reloaded (and later in WP-Cache).

Changelog

Version 2.0.4

• Support for WordPress 2.6 cookies (fixes problems with users not being logged-in).

Version 2.0.3

• Support for WordPress 2.5 cookies (fixes problems with users not being logged-in).

Version 2.0.2

• Now the plugin works with secured sites (HTTPS).
• Fixed the bug where the plugin didn't work if "WordPress address" and "Blog address" were different.

Version 2.0.1

• Fixed an error that prevented commenters from being cached individually.

Version 2.0

• Use of WordPress advanced-cache. The plugin runs before WordPress is fully loaded (less execution time and specially less memory use).
• Management of HTTP headers, that are saved in .txt files after being conveniently modified, for full cached responses.
• Support for dynamic code (mfunc and mclude comments) as in Staticize Reloaded (and later in WP-Cache).
• If Gzip compression is enabled, compressed content is saved in .gz files so it's only compressed once (less execution time and less CPU use). If dynamic code is used, that code is run and only if the final content is different from the already saved it's compressed again for the response.
  • If you have Gzip compression enabled and you are not using dynamic code, you can set the constant OBC_LOOK_FOR_DYNAMIC_CODE to false in order ro avoid this check.
• HTTP header 304 "not modified" returned when it's convenient (less loading time):
  • If the plugin is going to return the same cache (from the same date) to a user, it returns a 304 header instead.
  • Even with a different cache, if the content to return is the same (checked through a Etag header with a hash), a 304 header is also returned.
• When a post is created, modified or removed, the cache for that post and the index are removed for *all* users.
• (Logged) users and commenters management. Choose the plugin's behaviour for each group:
  • Use no cache.
  • Use a single global cache.
  • Use an individual cache for each user.
• More configuration options:
  • Option to cache or not error pages (status 404).
  • Option to cache or not redirections (status 301 or 302).
  • Option to omit url trailing slash ("/") in order to avoid caching the same content twice (don't use this in WordPress 2.3+ or if you are using a plugin that redirects urls with trailing slash).
  • Option to save all files in the same directory.
• The plugin creates automatically a .htaccess file in the cache directory that forbids web access.
• Only "inconvenience" in this version: now the cache directory must be /wp-cache/ (though it would be easy changing this in the code).

Requirements

The plugin is WordPress 1.5+ compatible (tested in 1.5, 2.0, 2.1, 2.2, 2.3, 2.5, 2.6, 2.7 and 2.8)