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.

What is new in this release:

• Fixed fatal error in output handler if GET parameters present in query.
• Fixed debug log. It wasn't logging the right message.

What is new in version 1.4.4:

• Fixed fatal error in output handler if GET parameters present in query.
• Fixed debug log. It wasn't logging the right message.

What is new in version 1.4.3:

• Security release fixing an XSS bug in the settings page.
• Added wp_debug_log().
• Minor fixes.

What is new in version 1.4.1:

• Fixed XSS in settings page. Props Simon Waters, Surevine Limited.
• Fix to object cache so entries may now be deleted when posts updated. (object cache still experimental)

What is new in version 1.4:

• Replace legacy mfunc/mnclude/dynamic-cached-content functionality with a "wpsc_cachedata" cacheaction filter.
• Added dynamic-cache-test.php plugin example wpsc_cachedata filter plugin.
• Delete post, tag and category cache when a post changes from draft to publish or vice versa.
• Update advanced-cache.php and wp-config.php if wp-cache-phase1.php doesn't load, usually happening after migrating to a new hosting service.

What is new in version 1.3.2:

• Any mfunc/mclude/dynamic-cached-content tags in comments are now removed.
• Dynamic cached content feature disabled by default and must be enabled on the Advanced Settings page.

What is new in version 1.3:

• More support for sites that use the LOGGED_IN_COOKIE constant and custom cookies.

What is new in version 1.2:

• Garbage collection of old cache files is significantly improved. I added a scheduled job that keeps an eye on things and restarts the job if necessary. Also, if you enable caching from the Easy page garbage collection will be enabled too.
• Editors can delete single cached files from the admin bar now.
• Fixed the cached page counter on the settings page.
• Some sites that updated to 1.0 experienced too much garbage collection. There are still stragglers out there who haven.t upgraded but that.s fixed now!
• Supercached mobile files are now used as there was a tiny little typo that needed fixing.
• If your site is in a directory and you saw problems updating a page then that should be fixed now.
• The deactivate hook has been changed so your configuration isn.t hosed when you upgrade. Unfortunately this will only happen after you do this upgrade.
• Some sites use custom cookies with the LOGGED_IN_COOKIE constant. Added support for that.

What is new in version 1.1:

• Only create blogs cached directories if valid requests and blogs exist.
• Only clear current blog's cache files if navigation menu is modified
• Added clean_post_cache action to clear cache on post actions
• Removed garbage collection details on Contents tab
• Added wp_cache_check_mobile cacheaction filter to shortcircuit mobile device check.
• Don't delete cache files for draft posts
• Added action on wp_trash_post to clear the cache when trashed posts are deleted
• Show a warning when 304 browser caching is disabled (because mod_rewrite caching is on)
• New check for safe mode if using less that PHP 5.3.0
• Added wp_supercache_remove_cookies filter to disable anonymous browsing mode.
• Fixed garbage collection schedule dropdown
• Fixed preload problem clearing site's cache on "page on front" sites.
• Fix for PHP variable not defined warnings
• Fixed problem refreshing cache when comments made as siteurl() sometimes didn't work
• Preloading of taxonomies is now optional
• Domain mapping fixes.
• Better support for https sites. Remove https:// to get cache paths.

What is new in version 0.9.9.9:

• Fixed typo, is_front_page.
• Serve repeated static files from the same CDN hostname.
• Updated translations.
• Make supercache dir lowercase to avoid problems with unicode URLs.
• Add option to skip https loaded static content.
• Remove 5 second check on age of existing cache files. Should help with posts that get lots of comments and traffic.
• Lots of bugs fixed.

What is new in version 0.9.9.5:

• Disable compression on on easy setup page. Still causes problems on some hosts.
• Remove footerlink on easy setup page.
• Don't delete mod_rewrite rules when caching is disabled.
• Don't stop users using settings page when in safe mode.

What is new in version 0.9.9.4:

• Settings page split into tabbed pages.
• Added new "Easy" settings page for new users.
• New PHP caching mode to serve supercached files.
• Mobile support fixes.
• Added Domain mapping support plugin.
• Added "awaiting moderation" plugin that removes that text from posts.
• Terminology change. Changed "half on" to "legacy caching".
• Fixed cache tester on some installs of WordPress.
• Updated documentation
• Added $wp_super_cache_lock_down config variable to hide lockdown and directly cached pages admin items.
• Preloaded checks if it has stalled and reschedules the job to continue.
• Serve the gzipped page when first cached if the client supports compression.
• Lots more bug fixes.

What is new in version 0.9.9.3:

• Fixed division by zero error in half on mode.
• Always show "delete cache" button.
• Fixed "Update mod_rewrite rules" button.
• Minor text changes to admin page.

What is new in version 0.9.9:

• Added experimental object cache support.
• Added Chinese(Traditional) translation.
• Added FAQ on WP-Cache vs Supercache files.
• Use Supercache file if WP-Cache file not found. Useful if mod_rewrite rules are broken or not working.
• Get mobile browser list from WP Mobile Edition if found. Warn user if .htaccess out of date.
• Make sure writer lock is unlocked after writing cache files.
• Added link to developer docs in readme.
• Added Ukranian translation.
• Added Upgrade Notice section to readme.
• Warn if zlib compression in PHP is enabled.
• Added compression troubleshooting answer.
• Added Japanese translation.
• Updated Italian translation.
• Link to WP Mobile Edition from admin page for mobile support.

What is new in version 0.9.6.1:

• Move "not logged in" message init below check for POST.
• Add is_admin() check so plugin definitely can't cache the backend.
• Add "do not cache" page type to admin page.

What is new in version 0.9.4.3:

• Added "Don't cache for logged in users" option.
• Display file size stats on admin page.
• Clear the cache when profile page is updated.
• Don't cache post previews.
• Added backslashes to rejected URI regex list.
• Fixed problems with posts and comments not refreshing.

Requirements:

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