1 Blog Theme has been moved to my personal web site, along with other scripts and themes:

• 1 Blog Cacher

The new version of this plugin has been released. New features:

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

You can read the plugin full features or download it right away.

The new version of this plugin has been released. New features:

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

You can read the plugin full features or download it right away.

The new version of this plugin has been released. New features:

• 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.

You can read the plugin full features or download it right away.

Update: the plugin zip contained a file (advanced-cache.php) with an error that prevented commenters from being cached individually. The error has been fixed and the correct zip uploaded. Sorry for any inconvenience.

The new version of this plugin has been released. New features:

• 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).

You can read the plugin full features or download it right away.