=== WP Super Cache ===
Contributors: donncha, automattic, kraftbj
Tags: performance,caching,wp-cache,wp-super-cache,cache
Tested up to: 4.5.2
Stable tag: 1.4.8
Requires at least: 3.0
A very fast caching engine for WordPress that produces static html files.
== Description ==
This plugin generates static html files from your dynamic WordPress blog. After a html file is generated your webserver will serve that file instead of processing the comparatively heavier and more expensive WordPress PHP scripts.
The static html files will be served to the vast majority of your users, but because a user's details are displayed in the comment form after they leave a comment those requests are handled by the legacy caching engine. Static files are served to:
1. Users who are not logged in.
2. Users who have not left a comment on your blog.
3. Or users who have not viewed a password protected post.
99% of your visitors will be served static html files. Those users who don't see the static files will still benefit because they will see different cached files that aren't quite as efficient but still better than uncached. This plugin will help your server cope with a front page appearance on digg.com or other social networking site.
If for some reason "supercaching" doesn't work on your server then don't worry. Caching will still be performed, but every request will require loading the PHP engine. In normal circumstances this isn't bad at all. Visitors to your site will notice no slowdown or difference. Supercache really comes into it's own if your server is underpowered, or you're experiencing heavy traffic.
Super Cached html files will be served more quickly than PHP generated cached files but in every day use, the difference isn't noticeable.
The plugin serves cached files in 3 ways (ranked by speed):
1. Mod_Rewrite. The fastest method is by using Apache mod_rewrite (or whatever similar module your web server supports) to serve "supercached" static html files. This completely bypasses PHP and is extremely quick. If your server is hit by a deluge of traffic it is more likely to cope as the requests are "lighter". This does require the Apache mod_rewrite module (which is probably installed if you have custom permalinks) and a modification of your .htaccess file. Visits by anonymous or unknown users will be served this way.
2. PHP. Supercached static files can now be served by PHP. The plugin will serve a "supercached" file if it exists and it's almost as fast as the mod_rewrite method. It's easier to configure as the .htaccess file doesn't need to be changed. You still need a custom permalink. You can keep portions of your page dynamic in this caching mode. Your server may not cope as well with a really large amount of traffic. (You're gaming Digg aren't you? You'll need mod_rewrite, the rest of us are ok with PHP!)
3. Legacy caching. This is mainly used to cache pages for known users. These are logged in users, visitors who leave comments or those who should be shown custom per-user data. It's the most flexible caching method but also the slowest. As each page is different it's often better not to cache pages for these users at all and avoid legacy caching. Legacy caching will also cache visits by unknown users if this caching mode is selected. You can have dynamic parts to your page in this mode too.
If you're new to caching use PHP caching. It's easy to set up and very fast. Avoid legacy caching if you can.
= Recommended Settings =
Advanced users will probably want to use mod_rewrite caching, but PHP caching is almost as good and recommended for everyone else. Enable the following:
1. PHP caching.
2. Compress pages.
3. Don't cache pages for known users.
4. Cache rebuild.
5. CDN support.
6. Extra homepage checks.
Garbage collection is the act of cleaning up cache files that are out of date and stale. There's no correct value for the expiry time but a good starting point is 1800 seconds if you're not using legacy mode. If you are using that mode start with an expiry time of 600 seconds.
If you are not using legacy mode caching consider deleting the contents of the "Rejected User Agents" text box and allow search engines to create supercache static files.
Likewise, preload as many posts as you can and enable "Preload Mode". Garbage collection will still occur but it won't affect the preloaded files. If you don't care about sidebar widgets updating often set the preload interval to 2880 minutes (2 days) so all your posts aren't recached very often. When the preload occurs the cache files for the post being refreshed is deleted and then regenerated. Afterwards a garbage collection of all old files is performed to clean out stale cache files.
With preloading on cached files will still be deleted when posts are made or edited or comments made.
See the [WP Super Cache homepage](https://wordpress.org/plugins/wp-super-cache/) for further information. [Developer documentation](http://z9.io/wp-super-cache-developers/) is also available for those who need to interact with the cache or write plugins.
There's a [GIT repository](https://github.com/Automattic/wp-super-cache) too if you want to contribute a patch.
The [changelog](http://svn.wp-plugins.org/wp-super-cache/trunk/Changelog.txt) is a good place to start if you want to know what has changed since you last downloaded the plugin.
Interested in translating WP Super Cache to your language? Grab the [development version](http://downloads.wordpress.org/plugin/wp-super-cache.zip) where you will find an up to date wp-super-cache.pot. Send any translation files to donncha @ ocaoimh.ie and thank you!
The cache directory, usually wp-content/cache/ is only for temporary files. Do not ever put important files or symlinks to important files or directories in that directory. They will be deleted if the plugin has write access to them.
== Upgrade Notice ==
= 1.4.8 =
Removed malware URL in a code comment.
== Changelog ==
= 1.4.8 =
* Removed malware URL in a code comment. (harmless to operation of plugin but gets flagged by A/V software)
* Updated translation file.
= 1.4.7 =
* Update the settings page for WordPress 4.4. layout changes.
= 1.4.6 =
* Generate the file cache/.htaccess even when one exists so gzip rules are created and gzipped pages are served correctly. Props Tigertech. https://wordpress.org/support/topic/all-website-pages-downloading-gz-file-after-latest-update?replies=36#post-7494087
= 1.4.5 =
* Enhancement: Only preload public post types. Props webaware.
* Added an uninstall function that deletes the config file. Deactivate function doesn't delete it any more.
* Possible to deactivate the plugin without visiting the settings page now.
* Fixed the cache rebuild system. Rebuild files now survive longer than the request that generate them.
* Minor optimisations: prune_super_cache() exits immediately if the file doesn't exist. The output of wp_cache_get_cookies_values() is now cached.
* Added PHP pid to the debug log to aid debugging.
* Various small bug fixes.
* Fixed reset of expiry time and GC settings when updating advanced settings.
* Removed CacheMeta class to avoid APC errors. It's not used any more.
* Fixed reset of advanced settings when using "easy" settings page.
* Fixed XSS in settings page.
* Hide cache files when servers display directory indexes.
* Prevent PHP object injection through use of serialize().
= 1.4.4 =
* Fixed fatal error in output handler if GET parameters present in query. Props webaware.
* Fixed debug log. It wasn't logging the right message.
= 1.4.3 =
* Security release fixing an XSS bug in the settings page. Props Marc Montpas from Sucuri.
* Added wp_debug_log(). Props Jen Heilemann.
* Minor fixes.
= 1.4.2 =
* Fixed "acceptable file list".
* Fixed "Don't cache GET requests" feature.
* Maybe fixed "304 not modified" problem for some users.
* Fixed some PHP warnings.
= 1.4.1 =
* Fixed XSS in settings page. Props Simon Waters, Surevine Limited.
* Fix to object cache s
wp-super-cache 对象缓存功能修复版本(1.4.8版本)
需积分: 10 116 浏览量
2016-09-04
03:10:01
上传
评论
收藏 859KB GZ 举报
wp-super-cache.tar.gz （50个子文件） 
wp-super-cache 
Changelog.txt 14KB
wp-cache-config-sample.php 3KB plugins domain-mapping.php 4KB awaitingmoderation.php 2KB wptouch.php 5KB dynamic-cache-test.php 8KB badbehaviour.php 3KB jetpack.php 3KB searchengine.php 3KB multisite.php 2KB wp-cache.php 193KB wp-cache-base.php 1KB languages wp-super-cache-ua_UA.po 88KB wp-super-cache-uk.po 63KB wp-super-cache-ja.po 91KB wp-super-cache-sv_SE.po 68KB wp-super-cache-be_BY.mo 74KB wp-super-cache-ru_RU.po 103KB wp-super-cache-sv_SE.mo 56KB wp-super-cache-it_IT.po 80KB wp-super-cache-es_ES.po 51KB wp-super-cache-de_DE.mo 69KB wp-super-cache-ro_RO.po 73KB wp-super-cache-fr_FR.po 74KB wp-super-cache-zh_TW.mo 73KB wp-super-cache-uk.mo 58KB wp-super-cache-zh_CN.mo 67KB wp-super-cache-zh_TW.po 85KB wp-super-cache-tr_TR.mo 69KB wp-super-cache-it_IT.mo 65KB wp-super-cache-ro_RO.mo 58KB wp-super-cache-sr_RS.mo 83KB wp-super-cache-lt_LT.mo 56KB wp-super-cache-ja.mo 77KB wp-super-cache-sr_RS.po 95KB wp-super-cache-ru_RU.mo 87KB wp-super-cache-ua_UA.mo 74KB wp-super-cache-zh_CN.po 81KB wp-super-cache-fr_FR.mo 60KB wp-super-cache-be_BY.po 88KB wp-super-cache-lt_LT.po 71KB wp-super-cache-tr_TR.po 80KB wp-super-cache-de_DE.po 78KB wp-super-cache-es_ES.mo 45KB wp-super-cache.pot 57KB wp-cache-phase2.php 56KB ossdl-cdn.php 10KB wp-cache-phase1.php 25KB advanced-cache.php 1KB readme.txt 49KB资源评论
