] 8<9,vM` s~?3>r*" 7M Z 5 !=$"bb"j"-0#$^# ##H$[%\j&&?'()K**w+Z,%v,,J-..7/&/0:(0nc1p1C3U3^3b33334 04=43\444C5 R5,_55^=6p6+ 797/O77 7 7`7+7+83@8t888!88!:7::;I;@<H<s<A=%=== >> >">51>g>z>3:?1n??H@^@AAAABuB Cj7CCCXD?^DDDD}D>ENDEEEyF FnF$ G/G5GRGnGG~GHHII II<IgJnJ+J*JJJJ KbK]L MN&N P"PkBQRWR SESeS*{S S S S SbS5T]KT$TT TTU)UGUU$U"V7V!RVtV 5W@W/X&DXkX<qXbX Y|ZyZ[0[ H[!U[-w[k[] "] -]8]>]mW]T]^U:^^p>_U_` ``'`9`JX``daa`bbc0c c cc7dS9d?d<d e)e@e7Uejeef4fYSff f f ff(f+g, -J)g*ň/. 3OĉA"ŋA*@fVj͌98Drƍ']<ZŽ*H@Y[[RrVR^Zʘ\)xEٛq$&KNalMk |&9#M q~1Ρҡ ~ *âXjlã20c-t Wä*F1_¥Fۥ"9B|K_*~֨eUh($M `mt {7Ӫ20ث ek%dD eErϰְXK_ʱ^ *1Nc x ̴g 6Z @!M)oķPͷAZ V ZyBϾ'  ! .Z;W-'4\cwT!g!! 3 9](yz6 '-!< O ] kxnOP>hT*: %M*xNZ`L<$U z -C0>J,(gy! U( / < IV!e,',^ h*u(}4G9| E+C 98xHQvsHoN'=@J\ffu$ $0 U` *;UdkQ"\GP_ fp@%-\_e F-pG9 ;Hj8HwJ!MG:% Ef+330)d)# CTL!P`s$6#J=T0? <,@MpOco Rmk>[/r:jM4S9*z" 5tQ" Ni1-(FG1ANBP L2x6|DV98GEwya&{O7H\H]IW_0qh$  }*7K; 8-e~/nI\.EXd [vV UU++,DZ)<5]'b3KF.3%)BZ :S%( !4>lCgRAY&;=Qf@Xu#2'?JW^Y Make sure they appear before any existing WordPress rules. %1$s is Digg proof thanks to caching by %2$s%1$s is maintained and developed by %2$s with contributions from many others.%s Cached Pages%s Expired Pages%s is writable. Please make it readonly after your page is generated as this is a security risk.%s removed!%s.htaccess has been updated with the necessary mod_rewrite rules. Please verify they are correct. They should look like this:%s/advanced-cache.php does not exist or cannot be updated.(1 = less, 5 = more, may cause severe server load.)(Experimental)(Only legacy caching supported, disabled compression and requires Bad Behavior in "%s/plugins/bad-behavior/") (may not always be accurate on busy sites)(only log requests from this IP address. Your IP is %s)(requires friendsadverts.php too) 1. If it already exists please delete the file first.2. Make %1$s writable using the chmod command through your ftp or server software. (chmod 777 %1$s) and refresh this page. This is only a temporary measure and you’ll have to make it read only afterwards again. (Change 777 to 755 in the previous command)3. Refresh this page to update %s/advanced-cache.php304 Not Modified browser caching. Indicate when a page has not been modified since last requested.304 support is disabled by default because in the past GoDaddy had problems with some of the headers used.Frequently Asked QuestionsInstallation HelpSupport ForumUse Google Libraries allows you to load some commonly used Javascript libraries from Google webservers. Ironically it may reduce your Yslow score.WP Minify reduces the number of files served by your web server by joining Javascript and CSS files together. Alternatively you can use WPSCMin, a Supercache plugin that minifies cached pages. It does not however join JS/CSS files together.Yahoo! Yslow is an extension for the Firefox add-on Firebug. It analyzes web pages and suggests ways to improve their performance based on a set of rules for high performance web pages. Also try the performance tools online at GTMetrix.No Adverts for Friends plugin is %s.

WP_CACHE constant added to wp-config.php

If you continue to see this warning message please see point 5 of the FAQ. The WP_CACHE line must be moved up.

WP_CACHE constant set to false

The WP_CACHE constant is used by WordPress to load the code that serves cached pages. Unfortunately it is set to false. Please edit your wp-config.php and add or edit the following line above the final require_once command:

define('WP_CACHE', true);

  • 1. Open %1$s$wp_cache_file in a text editor.
  • 2. Change the text CACHEHOME to %2$s
  • 3. Save the file and copy it to %3$s and refresh this page.
    • WARNING: Test some static urls e.g., %s to ensure your CDN service is fully working before saving changes.Advanced users only: Speed up your site with Caching and cache-control explains how to make your site more cacheable with .htaccess rules.Advanced users only: Install an object cache. Choose from Memcached, XCache, eAcccelerator and others.Error: WP_CACHE is not enabled in your wp-config.php file and I couldn’t modify it.Garbage Collection
    Last GC was %s minutes ago
    Page last cached: %sWarning! You attempted to enable compression but zlib.output_compression is enabled. See #21 in the Troubleshooting section of the readme file.A custom url or permalink structure is required for this plugin to work correctly. Please go to the Permalinks Options Page to configure your permalinks.A difference between the rules in your .htaccess file and the plugin rewrite rules has been found. This could be simple whitespace differences but you should compare the rules in the file with those below as soon as possible. Click the ’Update Mod_Rewrite Rules’ button to update the rules.A simple way of doing that is by changing the permissions temporarily using the CHMOD command or through your ftp client. Make sure it’s globally writeable and it should be fine.Accepted Filenames & Rejected URIsAdd direct page:Add here strings (not a filename) that forces a page not to be cached. For example, if your URLs include year and you dont want to cache last year posts, it’s enough to specify the year, i.e. ’/2004/’. WP-Cache will search if that string is part of the URI and if so, it will not cache that page.Add here those filenames that can be cached, even if they match one of the rejected substring specified above.Add the rules yourself. Edit %s.htaccess and find the block of code enclosed by the lines # BEGIN WPSuperCache and # END WPSuperCache. There are two sections that look very similar. Just below the line %%{HTTP:Cookie} !^.*(comment_author_|wordpress_logged_in|wp-postpass_).*$ add these lines: (do it twice, once for each section)Additional CNAMESAdvancedAgeAlternatively, you can edit your %s.htaccess file manually and add the following code (before any WordPress rules):ArchivesAvailable PluginsAwaiting ModerationAwaiting Moderation is now %sBad BehaviorBad Behavior support is now %sBad Behaviour not found. Please check your install.CDNCDN functionality provided by OSSDL CDN Off Linker by Mark KubackiCache ContentsCache TesterCache hits to this website for quick access.Cache plugins are PHP scripts that live in a plugins folder inside the wp-super-cache folder. They are loaded when Supercache loads, much sooner than regular WordPress plugins.Cache rebuild. Serve a supercache file to anonymous users while a new file is being generated.Cache stats are not automatically generated. You must click the link below to regenerate the stats on this page.Cache stats last generated: %s minutes ago.Cached %s seconds agoCached pages since %1$s : %2$sCachingCaching OffCaching OnCaching is only one part of making a website faster. Here are some other plugins that will help:Caching must be enabled to use this featureCancel Cache PreloadCannot continue... fix previous problems and retry.Cannot update .htaccessCategoryChange ExpirationCheck front page every 5 minutes.Checking for and deleting expired files is expensive, but it’s expensive leaving them there too. On a very busy site you should set the expiry time to 300 seconds. Experiment with different values and visit this page to see how many expired files remain at different times during the day. If you are using legacy caching aim to have less than 500 cached files if possible. You can have many times more cached files when using mod_rewrite or PHP caching.Cleaning up old supercache files.Clear all cache files when a post or page is published.Clear cache on error.Coarse file locking. You probably don’t need this but it may help if your server is underpowered. Warning! May cause your server to lock up in very rare cases!Comment moderation is enabled. Your comment may take some time to appear.Compress pages so they’re served more quickly to visitors.Compression is disabled by default because some hosts have problems with compressed files. Switching it on and off clears the cache.Configuration file changed, some values might be wrong. Load the page again from the "Settings" menu to reset them.Configuration file missing and %1$s directory (%2$s) is not writable by the Web server.Check its permissions.Currently caching from post %d to %d.Currently logging to: DebugDebuggingDeleteDelete CacheDelete ExpiredDelete Super Cache cached files (opens in new window)Delete cached fileDelete the plugin mod_rewrite rules in %s.htaccess enclosed by # BEGIN WPSuperCache and # END WPSuperCache and let the plugin regenerate them by reloading this page.Deleting supercache file: %s
    Deleting wp-cache file: %s
    Developers: Make your plugin lock down compatible by checking the "WPLOCKDOWN" constant. The following code will make sure your plugin respects the WPLOCKDOWN setting.Directly Cached FilesDirectly cached files are files created directly off %s where your blog lives. This feature is only useful if you are expecting a major Digg or Slashdot level of traffic to one post or page.Directories to include in static file matching. Use a comma as the delimiter. Default is wp-content, wp-includes, which will be enforced if this field is left empty.DisableDisabledDo not cache the following page types. See the Conditional Tags documentation for a complete discussion on each type.Domain MappingDomain Mapping plugin detected! Please go to the Supercache plugins page and enable the domain mapping helper plugin.Domain Mapping support is now %sDon’t cache pages for known users.EasyEdit %s and add the following line:
    define('WP_CACHE', true);
    Otherwise, WP-Cache will not be executed by WordPress core. EmailEmail the blog admin when checks are made. (useful for testing)EnableEnable CDN SupportEnabledEnables or disables plugin to Remove the text "Your comment is awaiting moderation." when someone leaves a moderated comment.ErrorError: GZIP compression is enabled, disable it if you want to enable wp-cache.Exclude if substringExcludes something from being rewritten if one of the above strings is found in the match. Use a comma as the delimiter like this, .php, .flv, .do, and always include .php (default).Existing direct pageExpire time:Expired files are files older than %s seconds. They are still used by the plugin and are deleted periodically.Expiry Time & Garbage CollectionFeedsFetching %s to prime cache: Fetching first copy of %s: Fetching second copy of %s: Fix ConfigurationFix problems with the plugin by debugging it here. It can send you debug emails or log them to a file in your cache directory.For best performance you should enable "Mobile device support" or delete the mobile rewrite rules in your .htaccess. Look for the 2 lines with the text "2.0\ MMP|240x320" and delete those.For example: to cache %1$sabout/, you would enter %1$sabout/ or /about/. The cached file will be generated the next time an anonymous user visits that page.Fresh Super Cached FilesFresh WP-Cached FilesFront PageFront page textFull refresh of cache in %d hours %d minutes and %d seconds.GZIP compression is enabled in WordPress, wp-cache will be bypassed until you disable gzip compression.Garbage CollectionGzip encoding rules in %s.htaccess created.He blogs at %1$s and posts photos at %2$s.Hide file listHomeI’m 99% certain that they aren’t bugs in WP Super Cache and they only happen in very rare cases but you can run a simple check once every 5 minutes to verify that your site is ok if you’re worried. You will be emailed if there is a problem.IP AddressIf that doesn’t work, make sure the file %s/advanced-cache.php doesn’t exist:If the expiry time is more than 1800 seconds (half an hour), garbage collection will be done every 10 minutes, otherwise it will happen 10 seconds after the expiry time above.If uninstalling this plugin, make sure the directory %s is writeable by the webserver so the files advanced-cache.php and cache-config.php can be deleted automatically. (Making sure those files are writeable too is probably a good idea!)In ’Preload Mode’ regular garbage collection will only clean out old legacy files for known users, not the preloaded supercache files. This is a recommended setting when the cache is preloaded.In very rare cases two problems may arise on some blogs:
    1. The front page may start downloading as a zip file.
    2. The wrong page is occasionally cached as the front page if your blog uses a static front page and the permalink structure is /%category%/%postname%/.
    Include directoriesIt appears that mod_rewrite is not installed. Sometimes this check isn’t 100% reliable, especially if you are not using Apache. Please verify that the mod_rewrite module is loaded. It is required for serving Super Cache static files. You will still be able to use legacy or PHP modes.It looks like your blog has URLs that end with a "/". Unfortunately since you installed this plugin a duplicate content bug has been found where URLs not ending in a "/" end serve the same content as those with the "/" and do not redirect to the proper URL. To fix, you must edit your .htaccess file and add these two rules to the two groups of Super Cache rules:KeyLate init. Display cached files after WordPress has loaded. Most useful in legacy mode.Legacy page caching.Less emails, 1 at the start and 1 at the end of preloading all posts.List all cached filesList the newest cached pages on this page.Lock DownLock Down:Log levelLogging TypeLogging to a file is easier but faces the problem that clearing the cache will clear the log file.Make WordPress FasterMake the textbox blank to remove it from the list of direct pages and delete the cached file.Many emails, 2 emails per 100 posts.Medium, 1 email per 100 posts.MiscellaneousMissing Apache ModulesMobile device support.Mobile rewrite rules detectedMobile support requires extra rules in your .htaccess file, or you can set the plugin to legacy mode. Here are your options (in order of difficulty):Mod Rewrite RulesMod Rewrite rules cannot be updated!Mod Rewrite rules must be updated!Mod Rewrite rules updated!Mod rewrite may not be installed!Mod_rewrite is fastest, PHP is almost as fast and easier to get working, while legacy caching is slower again, but more flexible and also easy to get working. New users should use PHP caching.Need Help?Need help? Check the Super Cache readme file. It includes installation documentation, a FAQ and Troubleshooting tips. The support forum is also available. Your question may already have been answered.Newest Cached Pages:Next GC in %s minutesNote:Note: enables PHP caching, cache rebuild, and mobile supportNotice: Mod_rewrite or Legacy caching enabled. Showing Advanced Settings Page by default.Notice: PHP caching enabled but Supercache mod_rewrite rules detected. Cached files will be served using those rules. If your site is working ok please ignore this message or you can edit the .htaccess file in the root of your install and remove the SuperCache rules.Notice: WP Super Cache mod_rewrite rule checks disabled unless running on on the main site of this network.Notice: WP Super Cache mod_rewrite rule checks disabled unless running on the main site of this network.OKObject cache in use. No cache listing available.Off-site URLOne or more page requests failed:Only refresh current page when comments made.PHP is compressing the data sent to the visitors of your site. Disabling this is recommended as the plugin caches the compressed output once instead of compressing the same page over and over again. Also see #21 in the Troubleshooting section. See this page for instructions on modifying your php.ini.Page %d: %d (%s)Page 1: %sPage 2: %sPagesPermlink Structure ErrorPlease rate this plugin and tell me if it works for you or not. It really helps development.Please create %s /wp-cache-config.php from wp-super-cache/wp-cache-config-sample.phpPlease say hi to him on %s too!Please see entry 16 in the Troubleshooting section of the readme.txtPlease see the readme.txt for instructions on uninstalling this script. Look for the heading, "How to uninstall WP Super Cache".Please visit %1$s to clear the cache as the front page of your site is not correct and missing the text, "%2$s"!Please visit %s to clear the cache as the front page of your site is now downloading!PluginsPreloadPreload %s posts.Preload Cache NowPreload has been restarted. %sPreload mode (garbage collection only on legacy cache files. Recommended.)Preloading creates lots of files however. Caching is done from the newest post to the oldest so please consider only caching the newest if you have lots (10,000+) of posts. This is especially important on shared hosting.Preloading of cache disabled. Please disable legacy page caching or talk to your host administrator.Prepare your server for an expected spike in traffic by enabling the lock down. When this is enabled, new comments on a post will not refresh the cached static files.Proudly tell the world your server is Digg proof! (places a message in your blog’s footer)Provides support for Domain Mapping plugin to map multiple domains to a blog.Rate This Plugin!Read Only Mode. Configuration cannot be changed.Readonly:RecommendedRecommended Links and PluginsRefresh of cache in %d hours %d minutes and %d seconds.Refresh preloaded cache files every %s minutes. (0 to disable, minimum %d minutes.)Refresh this page when the file permissions have been modified.Refresh this page when you have updated your .htaccess file.Refreshed the following posts:Regenerate cache statsRejected User AgentsRequired to serve compressed supercache files properly.Required to set caching information on supercache pages. IE7 users will see old pages without this module.Restore Default ConfigurationRewrite rules must be updatedRules must be added to %s too:Sample WP-Cache config file (%s) does not exist.Verify you installation.SaveSave ChangesSave FilesSave StringsSave UA StringsScheduled preloading of cache cancelled.Scheduled preloading of cache in %d minutesScheduled preloading of cache in 10 seconds.Scheduling next preload refresh in %d minutes.Scroll down the Advanced Settings page and click the Update Mod_Rewrite Rules button.Search PagesSend me status emails when files are refreshed.Send non-secure (non https) request for homepageSet the expiry date on supercached pages. Visitors may not see new pages when they refresh or leave comments without this module.Set the expiry time to 0 seconds to disable garbage collection.Set the plugin to legacy mode and enable mobile support.SettingsSingle PostsSorry. My blog is locked down. Updates will appear shortlyStale Super Cached FilesStale WP-Cached FilesStrings in the HTTP ’User Agent’ header that prevent WP-Cache from caching bot, spiders, and crawlers’ requests. Note that super cached files are still sent to these agents if they already exists.TagsTest CacheTest your cached website by clicking the test button below.Tester & ContentsText to search for on your front page. If this text is missing the cache will be cleared. Leave blank to disable.Thank you for upgrading.The WP Super Cache configuration file is %s/wp-cache-config.php and cannot be modified. That file must be writeable by the webserver to make any changes.The cache on your blog has been cleared because the front page of your site is missing the text "%2$s". Please visit %1$s to verify the cache has been cleared.The cache on your blog has been cleared because the front page of your site is now downloading. Please visit %s to verify the cache has been cleared.The file %s.htaccess cannot be modified by the web server. Please correct this using the chmod command or your ftp client.The following Apache modules are missing. The plugin will work in legacy mode without them. In full Supercache mode, your visitors may see corrupted pages or out of date content however.The mod_rewrite rules changed since you last installed this plugin. Unfortunately you must remove the old supercache rules before the new ones are updated. Refresh this page when you have edited your .htaccess file. If you wish to manually upgrade, change the following line: %1$s so it looks like this: %2$s The only changes are "HTTP_COOKIE" becomes "HTTP:Cookie" and "wordpressuser" becomes "wordpress". This is a WordPress 2.5 change but it’s backwards compatible with older versions if you’re brave enough to use them.The new URL to be used in place of %1$s for rewriting. No trailing / please.
    Example: %2$s.The pages do not match! Timestamps differ or were not found!The rewrite rules required by this plugin have changed or are missing. The timestamps on both pages match!These CNAMES will be used in place of %1$s for rewriting (in addition to the off-site URL above). Use a comma as the delimiter. For pages with a large number of static files, this can improve browser performance. CNAMEs may also need to be configured on your CDN.
    Example: %2$sThis is strictly an advanced feature only and knowledge of both PHP and WordPress actions is required to create them.This will cache every published post and page on your site. It will create supercache static files so unknown visitors (including bots) will hit a cached page. This will probably help your Google ranking as they are using speed as a metric when judging websites now.This will have no affect on ordinary users but mobile users will see uncached pages.To serve static html files your server must have the correct mod_rewrite rules added to a file called %s.htaccessToo many cached files, no listing possible.Trailing slash check required.URIUnfortunately WordPress cannot find the file wp-cron.php. This script is required for the the correct operation of garbage collection by this plugin, WordPress scheduled posts as well as other critical activities.Unfortunately the rewrite rules cannot be updated automatically when running WordPress MU. Please open your .htaccess and add the following mod_rewrite rules above any other rules in that file.UpdateUpdate Direct PagesUpdate Mod_Rewrite RulesUpdate SettingsUpdate StatusUse PHP to serve cache files.Use mod_rewrite to serve cache files.Use object cache to store cached files.View Mod_Rewrite RulesWP Super Cache SettingsWP Super Cache has checked the front page of your blog. Please visit %s if you would like to disable this.WP Super Cache is disabled. Please go to the plugin admin page to enable caching.WP Super Cache mod rewrite rules were detected in your %s.htaccess file.
    Click the following link to see the lines added to that file. If you have upgraded the plugin make sure these rules match.WP Super Cache must be configured. Go to the admin page to enable and configure the plugin.WP-CacheWP-Super-CacheWarningWarning!Warning! %s is writeable!Warning! Compression is disabled as gzencode() function not found.Warning! PHP Safe Mode Enabled!Warning! WP Super Cache caching broken! The script advanced-cache.php could not load wp-cache-phase1.php.

    Please edit %1$s/advanced-cache.php and make sure the path to %2$swp-cache-phase1.php is correct.Warning! Your hostname "%s" resolves to %sWordPress MU DetectedWordPress is locked down. Super Cache static files will not be deleted when new comments are made.WordPress is not locked down. New comments will refresh Super Cache static files as normal.Writeable:You can define different CDN URLs for each site on a multsite network.You can edit the file yourself add the following rules.You can see where the rules go and examine the complete rules by clicking the "View mod_rewrite rules" link below.You may experience problems running this plugin because SAFE MODE is enabled.You must have BEGIN and END markers in %s.htaccess for the auto update to work. They look like this and surround the main WordPress mod_rewrite rules:You must make %s writable to enable this feature. As this is a security risk please make it readonly after your page is generated.You or an administrator may be able to make it work by changing the group owner of the plugin scripts to match that of the web server user. The group owner of the %s/cache/ directory must also be changed. See the safe mode manual page for further details.You or an administrator must disable this. See the safe mode manual page for further details. This cannot be disabled in a .htaccess file unfortunately. It must be done in the php.ini config file.You should change the permissions on %s and make it more restrictive. Use your ftp client, or the following command to fix things:Your %s.htaccess is not writable by the webserver and must be updated with the necessary mod_rewrite rules. The new rules go above the regular WordPress rules as shown in the code below:Your WP-Cache config file (%s) is out of date and not writable by the Web server.Please delete it and refresh this page.Your cache directory ($cache_path) did not exist and couldn’t be created by the web server. Check %s permissions.Your cache directory (%1$s) or %2$s need to be writable for this plugin to work. Double-check it.Your comment is awaiting moderation.Your server is set up to check the owner of PHP scripts before allowing them to read and write files.Your server thinks your hostname resolves to %s. Some services such as garbage collection by this plugin, and WordPress scheduled posts may not operate correctly.Your website probably uses lots of static files. Image, Javascript and CSS files are usually static files that could just as easily be served from another site or CDN. Therefore this plugin replaces any links in the wp-content and wp-includes directories (except for PHP files) on your site with the URL you provide below. That way you can either copy all the static content to a dedicated host or mirror the files to a CDN by origin pull.Zlib Output Compression Enabled![%1$s] %2$d posts refreshed[%1$s] Cache Preload Started[%1$s] Cache Preload Stopped[%1$s] Refreshing posts from %2$d to %3$d[%s] Cache Preload Completed[%s] Front page check![%s] Front page is gzipped! Cache Cleared![%s] Front page is gzipped! Please clear cache![%s] Front page is not correct! Cache Cleared![%s] Front page is not correct! Please clear cache![%s] Preload may have stalled.alldisabledenabledfilesecondsProject-Id-Version: WP Super Cache (Traditional Chinese) Report-Msgid-Bugs-To: http://wordpress.org/tag/wp-super-cache POT-Creation-Date: 2010-12-09 13:32+0000 PO-Revision-Date: Last-Translator: Liang, Jih-Kai Language-Team: privism MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Poedit-Language: Chinese X-Poedit-Country: TAIWAN X-Poedit-SourceCharset: utf-8 確認它們出現在任何已存在的 WordPress 規則之前。%1$s 使用的快取程式為 %2$s%1$s由%2$s開發及維護，並得到許多人的幫助貢獻。%s 個頁面已快取%s 個頁面已過期%s 可寫入。由於這牽涉到一個安全風險，請在你的網頁產生後把它設為唯讀。%s 已移除！%s.htaccess 已更新必要的 mod_rewrite 規則。請確保它們是正確的。它們應該像這樣：%s/advanced-cache.php 不存在或是無法更新。（1 = 低，5 = 更多，可能會導致嚴重的伺服器負載）(實驗選項)（只支援傳統模式，停用壓縮，Bad Behavior 路徑必須為 "%s/plugins/bad-behavior/"）（在忙碌的網站上未必準確）（僅記錄來自此IP位址的請求。你的 IP 是 %s）（必須有 friendsadverts.php）1. 如果它已經存在，請先刪除。2. 請使用你的FTP程式或伺服器軟體，以chmod指令使%1$s可寫入。（chmod 777 %1$s），並重新整理此頁面。這只是一個暫時的作法，你事後必須在把它變更為唯讀。（使用前面的指令將權限從 777 變更為 755）3. 重新整理此頁面以更新 %s/advanced-cache.php304 未修改支援。當一個頁面在上次被要求後沒有被更改的時候送出。304支援預設為停用，因為過去GoDaddy在它使用的某些檔頭會產生問題。常見問題安裝指南支援論壇Use Google Libraries可以讓你從Google的伺服器上載入一些常用的Javascript函式庫。很諷刺的是它會降低你的Yslow分數。WP Minify 合併Javascript及CSS檔案，以減少網頁伺服器需要服務的檔案數量。 或者你也可以使用 WPSCMin，一個減少快取面數量的 Supercache 外掛。(但它並不會合併JS/CSS檔案)Yahoo! Yslow 是Firefox附加元件Firebug的一個延伸套件。它可以分析你的網頁，並根據一些高效率網頁規則，建議你增加效能的方式。 你也可以試試一個線上效能分析工具 GTMetrix。No Adverts for Friends 外掛模組 %s

    WP_CACHE 不斷被新增到 wp-config.php

    如果你持續看到此警告訊息，請參閱 FAQ 第五點。WP_CACHE 原始碼必須往前移動。

    WP_CACHE變數被設為false

    WP_CACHE變數被WordPress用來載入快取程式，可是它被設為false(關閉)。請編輯你的wp-config.php檔並把以下的內容放在最後的require_once命令之前。

    define('WP_CACHE', true);

  • 1. 以文字編輯器開啟 %1$s$wp_cache_file。
  • 2. 將 CACHEHOME 變更為 %2$s
  • 3. 儲存檔案並複製為 %3$s，然後重新整理此頁面。
    • 警告： 請先測試一些固定的網址，例如%s。在儲存變更前，確定你的CDN服務完全正常。進階使用者專用： 使用快取及快取控制加速你的網站，解釋怎麼讓你的網站更適用.htaccess規則來進行快取。進階使用者專用： 安裝物件快取。 你可以從Memcached、XCache、eAcccelerator或其它的加速器中選擇一個。錯誤：在你的 wp-config.php 檔案裡 WP_CACHE 是停用狀態，且無法修改。垃圾收集
    上次垃圾收集於 %s 分鐘前
    最新快取頁面： %s警告！ 你試著要開啟壓縮，但是zlib.output_compression已被啟用。 參見讀我檔案裡錯誤排除段落第21條。外掛要正常運作，必須有自定url或固定網址。請到固定網址選項設定你的固定網址。發現.htaccess的rewrite規則和外掛rewrite規則的不一致。有可能只是單純空白字元的差別，但是你應該立即比較以下的規則。 點擊「更新Mod_Rewrite規則」按鈕以更新規則。最簡單的方式是使用CHMOD指令或透過FTP程式來變更權限。請確保它們正確並可以寫入。接受的檔案名稱和拒絕的URI新增直接頁面：在下方輸入框內新增字串（不是檔案名稱），控制頁面是否被快取。舉例來說，如果你的URL中包含年份，但你不想快取去年的文章，那麼就指定年份，例如 ’/2004/’ 。WP-Cache 將會搜尋這個字串是否包含在URI之中，如果是的話則不會快取這個頁面。這是可以被快取的檔案名，即使它們與上方設定的拒絕字串相符時也仍將被快取。自行加入規則。編輯 %s.htaccess 並找到 # BEGIN WPSuperCache and # END WPSuperCache 原始碼區段。這兩部分看起來非常相似。只要在 %%{HTTP:Cookie} !^.*(comment_author_|wordpress|wp-postpass_).*$ 下方新增這一行（這動作要做兩次，一個區段一次）：額外的正規名稱(CNAMES)進階選項時間(秒)或者，你可以手動編輯 %s.htaccess 檔案並加入以下原始碼（在任何 WordPress 規則前）：存檔可使用的外掛Awaiting ModerationAwaiting Moderation 外掛模組 %sBad BehaviorBad Behaviour 外掛模組 %s找不到 Bad Behaviour. 請檢查你的安裝。CDNCDN 功能由OSSDL CDN Off Linker提供，作者為Mark Kubacki快取內容快取測試啟用快取以加速對本網站的存取快取外掛是wp-super-cache裡plugin資料夾中的一些PHP程式。它們在Supercache載入的時候就會被載入，比一般的WordPress plugin要早得多。重建快取。當新檔案重建的時候，提供supercache檔案給匿名使用者。快取統計不會自動產生，你必須點擊以下的連結，本頁的統計資料才會重新產生。快取統計最後產生時間：%s分鐘以前。已快取 %s 秒快取頁面自 %1$s ：%2$s快取關閉快取開啟快取快取只是讓網站變快的方法之一。這邊是一些其它有幫助的外掛：必須啟用快取才能使用這個功能取消快取預先載入無法繼續... 解決前述問題然後重試。無法更新 .htaccess分類變更過期時間每五分鐘檢查首頁檢查和刪除過期檔案代價高昂，但把這些檔案留在那裡也一樣。在非常忙碌的網站，你應該將過期時間設定為 300 秒。嘗試使用不同的數值，並注意這些頁面一天裡在不同時段產生多少過期檔案，如果可能的話盡量不讓快取文件數多於500個。清除舊的supercache檔案。當有文章或網誌分頁發佈時清除所有快取。清除快取時發生錯誤。粗略檔案鎖定。你大概不會用到這個功能，但如果你的伺服器效能較差，開啟後可能會有所幫助。警告！可能在少數情況下鎖死你的伺服器！迴響審核已啟用。您的迴響可能需要一些時間才會顯示。壓縮網頁，讓使用者能更快觀看壓縮預設為停用，因為某些主機在壓縮檔案時可能發生問題。啟用或停用這項功能會清除快取。設定檔已變更。某些數值可能錯誤。再次從"設定"選單讀取頁面後重設它們。設定檔遺失，%1$s 目錄（%2$s）也無法被伺服器寫入。請檢查權限。目前正在快取第%d到%d篇文章。當前記錄到：除錯設定除錯刪除刪除快取刪除過期檔案刪除 Super Cache 快取檔案（在新視窗打開）刪除快取檔案從 %s.htaccess 內刪除 # BEGIN WPSuperCache and # END WPSuperCache 原始碼區段的 mod_rewrite 規則，重新載入頁面讓外掛可以再次產生它們。刪除supercache檔案：%s
    刪除wp-cache檔案：%s
    開發者：透過檢查"WPLOCKDOWN"，讓你的外掛與鎖定功能相容。下面的原始碼將確保你的外掛遵守WPLOCKDOWN設定。直接快取檔案直接快取檔案是從你的部落格 %s 產生直接建立的檔案。這項功能只在你預測將會有從 Digg 或 Slashdot 大量流量進入某篇文章或頁面時才有用。靜態檔案比對包含的目錄。使用逗號作為分隔符號。預設為 wp-content, wp-includes ，當這個欄位空白時會強制套用。停用停用不快取以下頁面類型。查看條件標籤文件中對每個類型的完整探討。Domain MappingDomain Mapping外掛模組已被偵測到！請到Supercache外掛頁面啟用domain mapping支援外掛。Domain Mapping 外掛模組 %s不要為已知使用者快取。簡易模式編輯 %s 並加入以下原始碼：
    define('WP_CACHE', true);
    否則，WP-Cache 將無法被 WordPress 核心執行。電子郵件當檢查時寄送電子郵件給網站管理員。（供測試用）啟用啟用CDN支援啟用啟動或關閉此外掛，決定當有人發佈需審核的迴響時，是否去除「您的迴響正等待審核中」字樣。錯誤錯誤：GZIP壓縮已啟用，如果你想啟用wp-cache，請停用它。若含有以下字串則排除若網址中包含以上的字串，則不會被重寫。使用逗號作為分隔符號，像這樣：.php, .flv, .do，並請永遠包含.php (預設值)。已存在的直接頁面過期時間：過期檔案是超過 %s 秒鐘的檔案。它們仍然會被外掛使用並會定期刪除。過期時間 & 垃圾收集訂閱抓取 %s 至主要快取：抓取第一份%s：抓取第二份%s：修復設定在這裡使用外掛除錯模式解決問題。它可以寄發給你除錯電子郵件或在你的快取目錄內產生的紀錄檔。為了獲得最好的效能，你應該啟用"行動裝置支援"，或從你的 .htaccess 刪除行動裝置重寫規則。尋找包含 "2.0\ MMP|240x320" 字串的兩行並刪除它們。舉例來說：快取 %1$sabout/, 你應該輸入 %1$sabout/ 或 /about/ 。快取檔案將在下一個匿名使用者訪問該頁面時產生。新的 Super Cached 檔案新的 WP-Cached 檔案首頁首頁文字完整更新快取，耗費了%d小時%d分鐘%d秒。在 WordPress 上GZIP壓縮已啟用，wp-cache將被繞過，直到你停用gzip壓縮。垃圾收集%s.htaccess上Gzip規則建立。我的部落格在 %1$s，相簿在 %2$s.隱藏檔案清單主頁我有十足的把握肯定，它們不是 WP Super Cache 的錯誤。它只會發生在極少數的情況下，但如果你擔心的話，你可以每5分鐘進行一次簡單的檢查，以確保你的網站是正常的。如果有問題，你將會收到電子郵件。IP位址如果無法運作，請確認 %s/advanced-cache.php 檔案不存在：如果過期時間大於1800秒（半個小時），垃圾回收會每10分鐘進行一次，否則就會在設定到期時間的10秒後進行清理。如果移除這個外掛，請確認目錄 %s 為伺服器可以寫入，advanced-cache.php 和 cache-config.php 檔案會自動刪除。（確認這些檔案是可寫入的，也是個好主意！）在「預先載入」模式，通常的垃圾回收只會清除給已知使用者的傳統快取檔案，而不會清除預先載入的supercache檔案。這是預先載入的建議設定。在極少數的部落格可能會出現兩個問題：
    1. 在首頁可能會以一個 zip 檔案開始下載。
    2. 如果你的部落格使用一個靜態的首頁，或以 /%category%/%postname%/ 作為固定連結架構的話，那麼錯誤的頁面有時候會變成首頁的快取畫面。
    包含以下目錄看來 mod_rewrite 沒有安裝。有時候這種檢查並非 100% 可信，特別是當你不是使用 Apache 時。請重新檢查 mod_rewrite 模組已經載入。執行 Super Cache 靜態檔案時必須要有它。但你仍然可以使用傳統或PHP快取模式。看起來你的部落格有以"/"結束的URL。不幸地在你安裝這個外掛後，在URL不是以"/"結束的頁面，發現了一個重複內容的bug，也就是相同的內容卻不是被指向正確的URL。你必須修改你的 .htaccess 檔案以修復這個問題，在兩個 Super Cache 規則區段內新增下面兩個規則：關鍵字延遲初始化，在WordPress載入之後再顯示快取。通常使用在傳統模式。傳統快取模式較少信件，開始的時候一封還有結束的時候一封。列出所有快取檔案在本頁列出最新的快取頁面。鎖定鎖定：記錄等級記錄種類記錄到一個檔案更容易，但面臨的問題是清除快取將會清除記錄檔。讓 WordPress 更快速將輸入框清空，就能將它從直接頁面清單中移除並刪除快取檔案。很多信件，每一百篇文章二封信。中等，每一百篇文章一封信。雜項Apache 模組遺失行動裝置支援。行動裝置重寫規則檢測行動裝置支援必須在你的 .htaccess 檔案裡新增額外規則，或是你可以將外掛設定為傳統模式。這是你的選擇（根據個人需求）：Mod Rewrite 規則Mod Rewrite 規則無法更新！Mod Rewrite 規則必須更新！Mod Rewrite 規則已更新！Mod rewrite 可能沒有安裝！Mod_rewrite快取是最快的，PHP快取幾乎一樣快且較容易上手；傳統模式較慢，但是有更多的調性且同樣容易上手。新使用者應該使用PHP快取。需要幫助?需要幫助？ 看看Super Cache 讀我檔案。 它包含了安裝資訊，常見問題及錯誤排除小技巧。另外在支援論壇上，你的問題可能也已經有人回答過了。最新的快取頁面：下次垃圾收集於 %s 分鐘後備註：啟用PHP快取，重建快取，以及行動裝置支援注意：Mod_rewrite或傳統快取已被開啟。 預設顯示進階選項頁面。注意：PHP快取已被啟用，但偵測到Supercache mod_rewrite規則。快取檔案會用這些規則來服務。如果你的網站動作正常，你可以忽略這個訊息，否則請編輯站台安裝根目錄下的.htaccess檔以移除SuperCache規則。注意：除非在這個網路的主站上執行，WP Super Cache mod_rewrite規則檢查會被關閉。注意：除非在這個網路的主站上執行，WP Super Cache mod_rewrite規則檢查會被關閉。s完成正在使用Object快取。無法顯示快取清單。站外URL一個或以上的頁面要求失敗：當迴響發佈時，只更新目前頁面。PHP頁面壓縮啟用中。建議將它關閉，因為外掛針對一個頁面只需要壓縮一次，而不需要反覆的壓縮。另請參見錯換排除段落第21條。 這邊有如何修改你的php.ini的說明。頁面 %d: %d (%s)頁面1： %s頁面2： %s網誌分頁固定網址結構錯誤請為這個外掛評分，並告訴我它是否運作正常。這對開發非常有幫助。請以 wp-super-cache/wp-cache-config-sample.php 建立 %s /wp-cache-config.php在%s上向我問好！請參閱readme.txt第16項錯誤排除段落反安裝資訊請參見readme.txt，尋找"How to uninstall WP Super Cache"標題。請前往 %1$s 清除快取，部落格的首頁不正確，遺失文字，"%2$s"！請前往 %s 清除快取，網站的首頁正在下載！外掛預先載入預先載入 %s 篇文章。馬上開始預先載入預先載入已經被重新啟動. %s預先載入模式(只對傳統模式快取做垃圾回收。建議選項。)不過預先載入會產生很多檔案。快取會從最新的文章開始做到最早的文章，所以當你有非常多(10,000+)文章的時候，可能只會有新文章被快取到。這在分享主機上特別重要。預先載入已被關閉。請關閉傳統模式或和主機管理員連絡。如果你預測會有流量高峰到來時，可以啟用鎖定功能。當這個功能啟用時，在文章裡發佈新迴響將不會更新靜態快取檔案。告訴全世界你的伺服器已使用快取！（在你的部落格底部放置一段訊息）Domain Mapping外掛支援，映射多個網域至一個blog。為這個外掛評分！唯讀模式。設定無法變更。唯讀：建議選項建議連結及外掛在%d小時%d分鐘%d秒之後更新快取。每%s分鐘更新預載快取檔案。(0關閉，最低%d分鐘。)在權限修改後請重新整理這個頁面。當你已更新你的 .htaccess 檔案後重新整理此頁。已更新下列文章：重新產生快取統計被拒絕的使用者代理（User Agents）需要正確的supercache壓縮檔案。需要在supercache頁面設定快取訊息。IE7使用者將會看到沒有這個模組的舊頁面。還原到預設選項Mod Rewrite 規則必須更新！也必須新增到%s的規則：WP-Cache 設定檔範本（%s）不存在。請確認你的安裝。儲存儲存變更儲存檔案儲存字串儲存UA字串預載快取排程已被取消。下次預載快取排程時間：%d分鐘後預載快取將在十秒之後開始。下次更新預載快取時間：%d分鐘後捲動到進階選項頁面的下方並點擊更新Mod_Rewrite規則按鈕。搜尋頁面當檔案被更新的時候寄信給我。要非加密(非https)傳輸要求首頁設定supercached快取過期時間。沒有這個模組，訪客在重新整理或留下迴響時可能看不到新頁面。把過期時間設定為0以關閉垃圾回收功能將外掛設為傳統模式並開啟行動裝置支援。設定單篇文章抱歉。我的部落格已經鎖定。將會在短時間後更新。舊的 Super Cached 檔案舊的 WP-Cached 檔案HTTP User Agent；防止快取機器人、蜘蛛或抓取器對於 WP-Cache 的請求。請注意，如果快取檔案已經存在，仍然會發送給這些代理。標籤測試快取請按下面的測試按鈕以測試你的網站快取。測試及內容在你的首頁裡要搜尋的文字。如果缺少這些文字時快取將被清除。保留空白停用這個功能。感謝升級。WP Super Cache 設定檔 %s/wp-cache-config.php 無法修改。該檔案必須可以從伺服器端進行寫入。你的部落格已被清除快取，因為你的部落格首頁缺少文字 "%2$s"。請前往 %1$s 確認快取已被清除。你的部落格快取已被清除。因為你的部落格首頁正在下載，請前往 %s 確認快取已被清除。%s.htaccess 檔案無法被網頁伺服器更新。請使用 chmod 指令或透過 FTP 程式修正。以下的Apache模組遺失。沒有它們外掛將在傳統模式下工作。若在完整的Supercache模式，你的訪客可能會看到損壞的網頁或是過時的內容。從你上次安裝此外掛，mod_rewrite 規則已經變更。在新的supercache規則更新前，你必須先刪除舊的supercache規則。在你修改你的 .htaccess 檔案後重新整理此頁。如果你希望手動更新，更改以下幾行：%1$s 使它看起來像這樣：%2$s ，唯一改變的地方是 "HTTP_COOKIE" 變成 "HTTP:Cookie" 以及 "wordpressuser" 變成 "wordpress"。這是 WordPress 2.5 的改變，但如果你敢使用，它與舊版本相容。這個新的 URL 在會重寫 (rewriting) 時用來取代 %1$s。請不要加上結尾的 /。
    例： %2$s無頁面時間標籤或標籤不相符這個外掛所需的rewrite規則已被變更或不存在。頁面時間標籤相符！這些 正規名稱記錄(CNAMES) 會在重寫時用來取代 %1$s (和上面的站外URL一起)。 使用逗號作為分隔符號。 在有大量靜態檔案的網頁中，這可以增進瀏覽器效能。 這些CNAME可能也需要在你的CDN被設定。
    例： %2$s這是一個非常進階的功能，只有對PHP和Wordpress動作都非常了解的人才能撰寫。這會快取你網站上所有已發布的文章和頁面。它會產生supercache靜態檔案，匿名訪客(包括機器人)會命中快取頁面。這有可能會對你的Google排名有幫助，因為他們也將網站速度納入衡量項目之一。不會對一般使用者造成任何影響，但行動裝置使用者將會看到未快取的頁面。為了使用靜態的HTML檔案，你的伺服器上必須有正確的mod_rewrite規則，新增到一個名為 %s.htaccess 的檔案。快取檔案過多，無法列出。尾端斜線的檢查是必須的。URI 網址很抱歉，WordPress 找不到 wp-cron.php 檔案。必須要有這個程式才能正確執行垃圾回收、排程文章及其他重要活動。抱歉，當執行 WordPress MU 時重寫規則無法自動更新。請開啟你的 .htaccess，並在上述檔案中任何位置加入下方的 mod_rewrite 規則。更新更新直接頁面更新 Mod_Rewrite 規則更新狀態更新狀態使用PHP快取使用mod_rewrite快取使用object快取來儲存快取檔案。查看 Mod_Rewrite 規則WP Super Cache 狀態WP Super Cache 已檢查過你部落格的首頁。如果你想停用這項功能，請前往 %s 。WP Super Cache 停用。請前往 外掛管理員啟用快取。在你的%s.htaccess檔案中已經檢測到WP Super Cache重寫規則。
    點選以下連結，查看新增到該檔案的內容。如果你已經升級外掛，請確保與這些規則相同。WP Super Cache 必須設定。請前往管理後台啟用和設定外掛。WP-CacheWP-Super-Cache警告警告！警告！%s 可寫入！警告！因為找不到gzencode()函式，壓縮已被停用。警告！PHP 安全模式已啟用！警告！ WP Super Cache快取毀損！ advanced-cache.php 腳本無法載入 wp-cache-phase1.php。

    請編輯 %1$s/advanced-cache.php 並且確認指向 %2$swp-cache-phase1.php 的路徑是正確的。警告！你的主機名稱 "%s" 解析到 %sWordPress MU 檢測WordPress 已鎖定。新的迴響產生時將不會刪除 Super Cache 靜態快取檔案。WordPress 未鎖定。新的迴響產生時將會正常更新 Super Cache 靜態快取檔案。可寫入：你可以為多站台網路中的每個站台定義不同的CDN URL。你可以自行編輯並新增以下規則。你可以看到規則去向，透過點選下方的「查看 mod_rewrite 規則」連結來看到完整的規則在安全模式下，你的外掛可能會遭遇錯誤。要讓它自動工作，你必須在 %s.htaccess 上有 BEGIN 和 END 標記，它們看起來像這樣，圍繞 WordPress 的 mod_rewrite 規則：啟用這項功能前必須確認 %s 是可寫入狀態。由於這牽涉到一個安全風險，請在你的網頁產生後把它設為唯讀。你或管理員可以透過變更外掛程式群組的所有者使其與伺服器使用者一致，進而讓其運作。%s/cache/ 目錄的所有者也必須變更。查看安全模式使用手冊以取得更多說明。你或管理員必須先停用此項目。查看安全模式使用手冊以取得更多說明。很抱歉，這無法在 .htaccess 檔案裡停用。它必須在 php.ini 設定檔中完成。你應該變更 %s 權限使其更加嚴密。使用你的FTP程式，或是按照以下指令來解決：你的%s.htaccess無法由伺服器寫入，必須更新 mod_rewrite 規則。新的規則必須在一般的 WordPress 規則之上，如下面的原始碼所示：你的 WP-Cache 設定檔（%s）已經過期，且無法由伺服器端寫入，請刪除它並重新整理此頁面。你的快取目錄（$cache_path）不存在，且無法從伺服器端建立。請檢查 %s 權限。你的快取目錄（%1$s）或 %2$s 必須讓外掛可寫入才能正常運作。請重新檢查一次。您的迴響正等待審核中。你的伺服器設定為先檢查 PHP 程式擁有者才可以存取檔案。你的伺服器認為你的主機名稱解析到 %s. WP Super Cache 外掛的某些服務，例如垃圾回收、WordPress 排程文章可能無法正常執行。你的網站可能使用了許多的靜態檔案。圖片、Javascript、CSS檔案通常都是靜態檔案，可以很簡單地使用另一個站台或CDN來服務。所以這個外掛會根據你下面所提供的URL，取代你的網站中wp-content和wp-includes目錄下除了PHP檔案以外的任何連結。用這個方式，你可以把所有的靜態內容拷貝到一個專用的主機或或使用origin pull鏡射到CDN上。Zlib輸出壓縮已被啟用！[%1$s]%2$d 篇文章已被更新[%1$s] 快取預載已經開始[%1$s] 快取預載已停止[%1$s] 更新第 %2$d 到第 %3$d 篇文章[%s] 預載快取完成[%s] 首頁檢查！[%s] 首頁已使用gzip壓縮！快取已清除！[%s] 首頁已使用gzip壓縮！請清除快取！[%s] 首頁不正確！快取已清除！[%s] 首頁不正確！請清除快取！[%s] 預先載入可能已經停止所有已停用已啟用檔案秒