File: /www/wwwroot/www.cytocare.cn/wp-content/languages/plugins/wp-super-cache-zh_CN.mo
�� � < � \ x( < y( � �( �) �) �) ` �) ~ * - �* � �* * m+ 7 �+ � �+ # V, w z, j �, y ]- � �- � }. t "/ � �/ � s0 v �0 K q1 ? �1 G �1 � E2 � 3 @ 4 � S5 � �5 � �6 B f7 w �7 !8 � =8 � �8 � �9 � |; / :< � j= & #> J> " a> �> : �> n �? _ ?@ �A �A �A K �A �
B �B V �B �B C
C C ,C @C ^C kC 3 �C �C �C � �C �D �D �D % �D �D �D E E /E
<E ? JE j �E � �E ^ �F p $G + �G �G �G �G o ^H / �H �H I
I ( I " FI G iI � �I ` �J
K 3 "K VK nK �K �K h �K x
L = �L ! �L B �L 4 &M 0 [M ! �N B �N �N O L O I [O @ �O � �O s kP � �P `Q A iQ
�Q �Q D �Q k S �S �S �S �S �S �S �S 5 �S 0T QT � dT 3 $U 1 XU � �U 2V � HV � W �W �W ' �W D �W ?X HX 4 PX � �X � 7Y �Y u �Y mZ G �Z �Z � �Z * �[ ? �[ �[ �[ \ \ /\ u P\ S �\ ] } "] �] I �] @ �] Z 1^ p �^ z �^ x_ � �_ \` i q` n �` $ Ja A oa �a �a �a �a �a b .b 1 4b fb a xb � �b � �c
=d Hd g Xd �d � �d ge me |e y �e �e
�f � g b �g � ,h � �h �i � �j C lk � �k & ^l �m �m m �m n % 'n � Mo �p �p &
q z 4q � �q Jr ; ]r E �r �r * �r � s �s �s
t t
t L !u ] nu # �u �u
v v 3v Cv � Sv �v � w �w " �w �w ! x
#x � .x y "y D 7y P |y �y ) �y z l z X t{ ) �{ �| } } - } = I} �~ k �~ �
�
� +� 1� 2 J� S }� U р � '� p Ձ U F� �� �� �� �� Ђ � 8
� @ C� . �� � �� s �� � � � �� j B� M �� 5 �� � 1� r ه L� 0 ]�
�� �� �� S È : � ? R� �� �� ȉ ى � � � 7 �� j ي D�
b� p� �� [ �� � �
�
&� 4� A� Q� . [� f �� � / �� 0 .� � _� ? � 8 !� Z�
c� n� � ~� ,� 9� � B� � � ~� � '� / � : � ! Q� � s� � 5� R � _� � }� �
� ; � r S� ƕ � ߕ 8 �� � �� � a� � � � �� � #� � Ǚ � O� 3 � K 8� � �� � /� ŝ z ޟ < Y� � �� � !� G �� # � � (� T � = B� ��
�� T �� � �� � ~ '� + �� Ҧ v � g ]� Ũ � ɨ � �� ?� F� Z�
s� 5 �� d �� � ' 2� Z� + q� 6 �� ԫ � j �� b f� � ɬ l �� & � (� 1� ;� J� Z� g b� ʮ � � �� i � F y� - �� � O � + ^� G �� 0 ұ @ � g D� * �� � ײ � w� b @� [ ��
�� �
� � �� W $� � |� F � 8 L� M �� - ӹ � � 0 �� � �� � �� � /� � �� � ^� � � � m� $ � L � e c� � � � l� � #� D� `� }� 1 �� ) �� �� � 3� * J� / u� . �� 3 �� � '� +� 3� <� D� - \� � �� 7� ?� & `� 0 �� � �� �� �� �� Z �� v � * �� � �� 5 b� 4 �� q �� $ ?� p d� g �� q =� � �� � Z� Y �� � R� } �� u y� K �� E ;� M �� � �� � �� ( l� � �� � '� � � U �� w *� �� � �� � J� � � � �� � u� � a� ( �� � ' 2� " Z� }� Z �� > �� � 1� 8� < E� � �� � E � _� f�
s� ~� �� �� �� �� ; �� � +� � /� �� �� � : � O� \� l� y� �� �� G �� k �� � `� H ;� Z �� ' �� � � t #� � �� 3 � O� \� o� �� % �� E ��
� c %� �� = �� �� �� � � J (� f s� @ �� � ? ;� & {� � �� * �� K �� � +� c 5� Q �� - �� � � a �� p �� n� 2 u� �� �� > �� n � {� �� �� �� �� �� ( �� =
� H� d� � z� D K� B �� � �� u� � �� � 9� � � � 9
� G� Q� 0 X� � �� � ?� � k �� b� 2 z� �� � �� 3 N� J �� � � � � � � � K �� � v �� o� 9 v� 3 �� @ � U %� R {� � � � � c � e I� �� E � ! = " C % f % � � 8 � � ] � � ] � � � [ � � $
� � � e � 1 5 g � q P � g � � � � � h H ( � q %
- : a N � < � ^ � \ h $ } p � � � > � V � D - c � � ! R t { � � ? � Z � . + 4 Z � � � � � � $ y � � 6 $ I n $ � � � � � � F � P S c � ^ � p � ^ m z } < � / � � b
m � � � � 2 � N � T B � � g > R � � * @ ! S 9 u > � ' � � ! f �! � +" � �" w m# O �# 3 5$ � i$ d �$ _% $ x% �% �% �% I �% 7 & * I& t& �& �& �& $ �& � �& 6 �' u �' C( V( p( " �( T �( ) ) ) %) 2) 9) V) , ]) b �) �) 3 �) * .* ~ Y* 7 �* 6 + G+ N+ [+ � n+ , , y /, h �, � - � �- 3 X. B �. ! �. � �. � / W C0 �0 � �0 91 @1 0 M1 ` ~1 �1 �1 D u2 � �2 � C3 k �3 y ;4 � �4 s =5 � �5 [6 : z6 � �7 � N8 � �8 h : 6 �: � ; � �; 6 .< ! e< � �< / *= 9 Z> �> 2 �> T �?
/@ :@ M@ � `@ * �@
A F A g aB �B � �B x zC �C �C D -D 7 4D a lD �D ! �D E ( E - IE wE �E X �E [ �E � QF U G " lG �G �G �G �G �G W �G !H 2H 9H AH � ^H ? �H * I % JI F pI # �I 9 �J * K : @K z {K * �K � !L � �L d �N b �N PO ]O � �O C cP r �Q J R 9 eR I �R �R � S �S � �T ` �U n �U � fV � W u �W � X ! �X ? �X \ �Y ~ GZ � �Z � T[ F] d] �] �] 8 �] . �] 2 ^ R^ g^ 2 |^ 5 �^ ) �^ ) _ & 9_ `_ g_ n_ x_ �_ - �_ � �_ S` W` � k � � F
� � � 9 � � T 4 � M � P _ } � ^ � " � B � \ � ` � � � � l ~ $ � � G � � D p � g � 8 k � m E 2 � e / � � � D j � � Z K y �
� ! � t � c - = � � � S � f � Z I � � Y � ) � X � � P ; � ] @ � V � � � r � h � � U s � _ � � � � U � Q � � = � 3 S W z B V � q � � � H � � � � � � � u � [ � � Y � � � N � � X � x M [ 9 l � n C * ) � � % ( / Q � � ; 5 � f ` � 3 � � � � � j
� �
� � � h J � � � � � � � d � � � � � � L c o � � A � + � E , i � u � � { # w � 1 � � � d v > � C � 6 � � N � , 5 � g � � J � � � � # � � � . � } � � & . � G � � z m | e * � s � � w � � ' � � < � � � A � � I R ] T | ' � � � � � � � � 6 � v : � t + � � & " $ � : � { q � W b 0 � � y � � � o O H � � 2 � a � � � 7 � � ? � 4 ? � � r � � � x � � � � � p � L \ 7 � � ~ � � K � F a � � � � � � � � @ � ^ � 0 � � � � � � � > ! � � - � � O � n b � 1 ( 8 R < � % i � � Make sure they appear before any existing WordPress rules. %1$sJetpack%2$s was not found on your site but %3$syou can install it%2$s. The Site Accelerator feature is free to use on any WordPress site and offers the same benefit as other CDN services. You should give it a try! %s %s Files %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.htaccess has been updated with the necessary mod_rewrite rules. Please verify they are correct. They should look like this: %s/advanced-cache.php</em> cannot be updated. (Only WPCache caching supported, disabled compression and requires <a href="http://www.bad-behavior.ioerror.us/">Bad Behavior</a> in "%s/plugins/bad-behavior/") (may not always be accurate on busy sites) (only log requests from this IP address. Your IP is %s) * The links above (apart from Jetpack) go to websites outside the author's control. Caution is advised when testing any new software. .htaccess file may need to be moved 304 Browser caching. Improves site performance by checking if the page has changed since the browser last requested it. 304 support is disabled by default because some hosts have had problems with the headers used in the past. <a href="%s">Jetpack Boost</a> helps speed up your website by generating critical CSS, defering Javascript and much more. <a href="%s">Jetpack</a> provides everything you need to build a successful WordPress website including an image/photo CDN (free) and a video hosting service (paid). <a href="%s">Use Google Libraries</a> allows you to load some commonly used Javascript libraries from Google webservers. Ironically, it may reduce your Yslow score. <a href="%s">WP Crontrol</a> is a useful plugin to use when trying to debug garbage collection and preload problems. <a href="%s">Yahoo! Yslow</a> 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 <a href="%s">GTMetrix</a>. <a href="%s">commonWP</a> does the same job as "Use Google Libraries" and offloads some commonly used static files to an external CDN. <a href="https://codex.wordpress.org/Changing_File_Permissions">This page</a> explains how to change file permissions. <abbr title="Coordinated Universal Time">UTC</abbr> time is <code>%s</code> <acronym title="Use PHP to serve cached files">Simple</acronym> <acronym title="Use mod_rewrite to serve cached files">Expert</acronym> <em>Garbage collection</em> is the simple act of throwing out your garbage. For this plugin that would be old or <em>stale</em> cached files that may be out of date. New cached files are described as <em>fresh</em>. <h4>WP_CACHE constant added to wp-config.php</h4><p>If you continue to see this warning message please see point 5 of the <a href="https://wordpress.org/plugins/wp-super-cache/faq/">Troubleshooting Guide</a>. The WP_CACHE line must be moved up. <h4>WP_CACHE constant set to false</h4><p>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:<br /><br /><code>define('WP_CACHE', true);</code></p> <strong style="color: red">WARNING:</strong> Test some static urls e.g., %s to ensure your CDN service is fully working before saving changes. <strong style="color: red">WARNING:</strong> Your siteurl and homeurl are different. The plugin is using %s as the homepage URL of your site but if that is wrong please use the filter "ossdl_off_blog_url" to fix it. <strong>Advanced users only:</strong> Install an object cache. Choose from <a href="%s">Memcached</a>, <a href="%s">XCache</a>, <a href="%s">eAcccelerator</a> and others. <strong>DO NOT CACHE PAGE</strong> secret key: <a href="%s">%s</a> <strong>Error: WP_CACHE is not enabled</strong> in your <code>wp-config.php</code> file and I couldn’t modify it. <strong>Errors:</strong> %s <strong>Warning!</strong> Cache comments are currently disabled. Please go to the Debug page and enable Cache Status Messages there. You should clear the cache before testing. <strong>Warning!</strong> You attempted to enable compression but <code>zlib.output_compression</code> is enabled. See #21 in the Troubleshooting section of the readme file. <strong>Warning</strong>! Due to the way WordPress upgrades plugins, the ones you upload to the WP Super Cache folder (wp-super-cache/plugins/) will be deleted when you upgrade WP Super Cache. To avoid this loss, load your cache plugins from a different location. When you set <strong>$wp_cache_plugins_dir</strong> to the new location in wp-config.php, WP Super Cache will look there instead. <br />You can find additional details in the <a href="%s">developer documentation</a>. A custom url or permalink structure is required for this plugin to work correctly. Please go to the <a href="options-permalink.php">Permalinks Options Page</a> 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 URIs Activate Jetpack Boost Add Surveys and Polls to your site Add 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 <code># BEGIN WPSuperCache</code> and <code># END WPSuperCache</code>. There are two sections that look very similar. Just below the line <code>%%{HTTP:Cookie} !^.*(comment_author_|%s|wp-postpass_).*$</code> add these lines: (do it twice, once for each section) Additional CNAMES Advanced Age All users of this site have been logged out to refresh their login cookies. Alternatively, you can edit your <code>%s.htaccess</code> file manually and add the following code (before any WordPress rules): Always Cache Filenames An image showing a space shuttle. In the foreground are two graphs in yellow and green Archives Author Pages Automattic Available Plugins Awaiting Moderation Awaiting Moderation is now %s Bad Behavior Bad Behavior support is now %s Bad Behaviour not found. Please check your install. Boost your page speed scores CDN CDN functionality provided by <a href="https://wordpress.org/plugins/ossdl-cdn-off-linker/">OSSDL CDN Off Linker</a> by <a href="http://mark.ossdl.de/">Mark Kubacki</a> CRON System Disabled Cache Contents Cache Delivery Method Cache HTTP headers with page content. Cache Location Cache Rebuild. Cache Restrictions Cache Status Messages Cache Tester Cache Timeout Cache expiry cron job failed. Job will run again in 10 seconds. Cache expiry cron job took more than 30 seconds. You should probably run the garbage collector more often. Cache plugins are PHP scripts you'll find in a dedicated folder inside the WP Super Cache folder (wp-super-cache/plugins/). They load at the same time as WP Super Cache, and before 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 Cached %s seconds ago Cached files are fresh for a limited length of time. You can set that time in the <em>Cache Timeout</em> text box on this page. Cached pages are stored on your server as html and PHP files. If you need to delete them, use the button below. Cached pages since %1$s : <strong>%2$s</strong> Caching Caching Off Caching On Caching disabled for logged in visitors. Caching disabled. Page not cached. Caching has been disabled on this blog on the Network Admin Sites page. Caching is a great start, but there is more to maximize your site speed. Find out how much your cache speeds up your site and make it blazing fast with Jetpack Boost, the easiest WordPress speed optimization plugin developed by Super Cache engineers. Caching is only one part of making a website faster. Here are some other plugins that will help: Cancel Cache Preload Cannot continue... fix previous problems and retry. Cannot delete directory Cannot update .htaccess Category Change Expiration Change the location of your cache files. The default is WP_CONTENT_DIR . /cache/ which translates to %s. Check for stale cached files at this time <strong>(UTC)</strong> or starting at this time every <em>interval</em> below. Check for stale cached files every <em>interval</em> seconds. Check front page every 5 minutes. Check how your web site performance scores for desktop and mobile. Check out the <a href="%s">plugin documentation</a>. 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 <em>600 seconds</em>. Experiment with different values and visit this page to see how many expired files remain at different times during the day. Cleaning up old supercache files. Clear all cache files when a post or page is published or updated. Clear cache on error. Clock: Coarse file locking. You do not need this as it will slow down your website. 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 (<strong>%2$s</strong>) is not writable by the web server. Check its permissions. Contents Could not update %s!</em> WPCACHEHOME must be set in config file. Current Rules Currently logging to: %s Dear User,
WP Super Cache was removed from your blog but the mod_rewrite rules
in your .htaccess were not.
Please edit the following file and remove the code
between 'BEGIN WPSuperCache' and 'END WPSuperCache'. Please backup the file first!
%s
Regards,
WP Super Cache Plugin
https://wordpress.org/plugins/wp-super-cache/ Dear User,
WP Super Cache was removed from your blog or deactivated but some files could
not be deleted.
Debug Delete Delete Cache Delete Cache On All Blogs Delete Cached Pages Delete Expired Delete Super Cache cached files Delete Super Cache cached files (opens in new window) Delete cache of the current page Delete cached file Delete the plugin mod_rewrite rules in %s.htaccess enclosed by <code># BEGIN WPSuperCache</code> and <code># END WPSuperCache</code> and let the plugin regenerate them by reloading this page. Deleting supercache file: <strong>%s</strong><br /> Deleting wp-cache file: <strong>%s</strong><br /> 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 Files Directly 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 <code>wp-content, wp-includes</code>, which will be enforced if this field is left empty. Disable Disable Logging Disable caching for logged in visitors. Disable caching for visitors who have a cookie set in their browser. Disabled Dismiss Display comments at the end of every page like this: Do not cache pages when these cookies are set. Add the cookie names here, one per line. Matches on fragments, so "test" will match "WordPress_test_cookie". (Simple caching only) Do not cache the following page types. See the <a href="https://codex.wordpress.org/Conditional_Tags">Conditional Tags</a> documentation for a complete discussion on each type. Domain Mapping Domain Mapping plugin detected! Please go to the Supercache plugins page and enable the domain mapping helper plugin. Domain Mapping support is now %s Don’t cache pages with GET parameters. (?x=y at the end of a url) Easy Edit <code>%s</code> and add the following line:<br /> <code>define('WP_CACHE', true);</code><br />Otherwise, <strong>WP-Cache will not be executed</strong> by WordPress core. Email me when the garbage collection runs. Email the blog admin when checks are made. (useful for testing) Enable Enable CDN Support Enable Caching Enable Logging Enable caching for all visitors. Enable dynamic caching. (See <a href="%s">FAQ</a> or wp-super-cache/plugins/dynamic-cache-test.php for example code.) Enable logging on the Debug page here. That should help you track down the problem. Enabled Enables or disables plugin to Remove the text "Your comment is awaiting moderation." when someone leaves a moderated comment. Error Error: Configuration file %s could not be loaded. Please reload the page. Error: Configuration file %s is missing. Please reload the page. Error: Configuration file is read only. Please make sure %s is writeable by the webserver. Error: Could not rename temporary file to configuration file. Please make sure %s is writeable by the webserver. Error: The directory containing the configuration file %s is read only. Please make sure it is writeable by the webserver. Exclude if substring Excludes something from being rewritten if one of the above strings is found in the URL. Use a comma as the delimiter like this, <code>.php, .flv, .do</code>, and always include <code>.php</code> (default). Existing direct page Expert caching requires changes to important server files and may require manual intervention if enabled. Expired files are files older than %s seconds. They are still used by the plugin and are deleted periodically. Expiry Time & Garbage Collection Extra homepage checks. (Very occasionally stops homepage caching) FAILED Fast video hosting (paid) Feeds Fetching %s to prime cache: Fetching first copy of %s: Fetching second copy of %s: Files Find out how much Super Cache speeds up your site Fix Configuration Fix problems with the plugin by debugging it here. It will log 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 <em>%1$sabout/</em>, you would enter %1$sabout/ or /about/. The cached file will be generated the next time an anonymous user visits that page. Front Page Front page text GZIP compression is enabled in WordPress, wp-cache will be bypassed until you disable gzip compression. Garbage Collection Garbage collection by this plugin clears out expired and old cached pages on a regular basis. Use <a href="#expirytime">this form</a> to enable it. HH:MM Hide file list Home How long should cached pages remain fresh? Set to 0 to disable garbage collection. A good starting point is 3600 seconds. I’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 Address If it was created by another caching plugin please uninstall that plugin first before activating WP Super Cache. If the file is not removed by that action you should delete the file manually. If that doesn’t work, make sure the file <em>%s/advanced-cache.php</em> doesn’t exist: If the directory does not exist, it will be created. Please make sure your web server user has write access to the parent directory. The parent directory must exist. If the new cache directory does not exist, it will be created and the contents of the old cache directory will be moved there. Otherwise, the old cache directory will be left where it is. If uninstalling this plugin, make sure the directory <em>%s</em> is writeable by the webserver so the files <em>advanced-cache.php</em> and <em>cache-config.php</em> can be deleted automatically. (Making sure those files are writeable is probably a good idea!) If you just installed WP Super Cache for the first time, you can dismiss this message. Otherwise, you should probably refresh the login cookies of all logged in WordPress users here by clicking the logout link below. If you need support for this problem contact your hosting provider. In ’Preload Mode’ regular garbage collection will be disabled so that old cache files are not deleted. This is a recommended setting when the cache is preloaded. In very rare cases two problems may arise on some blogs:<ol><li> The front page may start downloading as a zip file.</li><li> The wrong page is occasionally cached as the front page if your blog uses a static front page and the permalink structure is <em>/%category%/%postname%/</em>.</li></ol> Include directories Install Jetpack Boost Interval garbage collection every 10 minutes with a cache lifetime of 30 minutes (if not configured already). Interval: It 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 in expert mode. You will still be able to simple mode. It appears you have WordPress installed in a sub directory as described <a href="https://codex.wordpress.org/Giving_WordPress_Its_Own_Directory">here</a>. Unfortunately, WordPress writes to the .htaccess in the install directory, not where your site is served from.<br />When you update the rewrite rules in this plugin you will have to copy the file to where your site is hosted. This will be fixed in the future. Jetpack CDN Jetpack Mobile Theme Jetpack Mobile Theme support is now %s Jetpack not found in %s. Install it and enable the mobile theme and this helper plugin to cache visits by mobile visitors. Keep in mind that cache plugins are for advanced users only. To create and manage them, you'll need extensive knowledge of both PHP and WordPress actions. Last Logged to: %s Late init. Display cached files after WordPress has loaded. Less emails, 1 at the start and 1 at the end of preloading all posts. List all cached files List the newest cached pages on this page. Load your homepage in a logged out browser, check the timestamp at the end of the html source. Load the page again and compare the timestamp. Caching is working if the timestamps match. Local time is <code>%1$s</code> Lock Down Lock Down: Logout Make %1$s writable using the chmod command through your ftp or server software. (<em>chmod 777 %1$s</em>) 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) Make known users anonymous so they’re served supercached static files. Make the textbox blank to remove it from the list of direct pages and delete the cached file. Many emails, 2 emails per %d posts. Medium, 1 email per %d posts. Miscellaneous Missing Apache Modules Mobile Browsers Mobile Prefixes Mobile device support. (External plugin or theme required. See the <a href="https://jetpack.com/support/wp-super-cache/wp-super-cache-faq/">FAQ</a> for further details.) Mobile rewrite rules detected Mobile support requires extra rules in your .htaccess file, or you can set the plugin to simple mode. Here are your options (in order of difficulty): Mod Rewrite Rules Mod Rewrite rules must be updated! Mod Rewrite rules updated! Mod rewrite may not be installed! Need Help? Need help? Check out <a href="%1$s">the documentation</a>. It includes installation documentation, a FAQ, and Troubleshooting tips. The <a href="%2$s">support forum</a> is also available. Your question may already have been answered. New Rules Newest Cached Pages: Next scheduled garbage collection will be at <strong>%s UTC</strong> Nginx rules can be found <a href="%s">here</a> but are not officially supported. No Emails Not allowed to edit %s per configuration. Note: Note: if you use Cloudflare or other transparent front-end proxy service this test may fail.<ol><li> If you have Cloudflare minification enabled this plugin may detect differences in the pages and report an error.</li><li> Try using the development mode of Cloudflare to perform the test. You can disable development mode afterwards if the test succeeds.</li></ol> Notice: <em>Expert mode caching enabled</em>. Showing Advanced Settings Page by default. Notice: Simple caching enabled but Supercache mod_rewrite rules from expert mode detected. Cached files will be served using those rules. If your site is working ok, please ignore this message. Otherwise, you can edit the .htaccess file in the root of your install and remove the SuperCache rules. Notification Emails OK Off-site URL Only refresh current page when comments made. Or, the <em>Clock</em> scheduler allows the garbage collection to run at specific times. If set to run hourly or twice daily, the garbage collector will be first scheduled for the time you enter here. It will then run again at the indicated interval. If set to run daily, it will run once a day at the time specified. Other Site Tools 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 <a href="http://php.net/manual/en/zlib.configuration.php">this page</a> for instructions on modifying your php.ini. Page %d: %d (%s) Page 1: %s Page 2: %s Pages Permlink Structure Error Please <a href="%s">rate us</a> and give feedback. Please create %s/wp-cache-config.php from wp-super-cache/wp-cache-config-sample.php Please see entry 16 in the <a href="%s">Troubleshooting section</a> of the readme.txt Please see the <a href="%1$s/wp-super-cache/readme.txt">readme.txt</a> 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! Plugins Preload Preload %s posts. Preload Cache Now Preload has been activated Preload has been restarted.
%s Preload mode (garbage collection disabled. Recommended.) Preload mode is enabled. Supercache files will never be expired. Preload tags, categories and other taxonomies. 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 make sure simple or expert mode is enabled 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. Provides support for <a href="https://wordpress.org/plugins/wordpress-mu-domain-mapping/">Domain Mapping</a> plugin to map multiple domains to a blog. Provides support for <a href="https://wordpress.org/plugins/wptouch/">WPTouch</a> mobile theme and plugin. Provides support for Domain Mapping plugin to map multiple domains to a blog. Provides support for WPTouch mobile theme and plugin. Provides support for the <a href="https://wordpress.org/plugins/jetpack/">Jetpack</a> mobile theme and plugin. PHP caching mode and mobile support will be enabled too. Provides support for the Jetpack mobile theme and plugin. PHP caching mode and mobile support will be enabled too. Rate This Plugin Read Only Mode. Configuration cannot be changed. Read-only: Recommended Recommended Links and Plugins Refresh preloaded cache files every %s minutes. (0 to disable, minimum %d minutes.) Refresh this page to update <em>%s/advanced-cache.php</em> Refresh this page when the file permissions have been modified. Refreshed the following posts: Regenerate cache stats Rejected Cookies Rejected URL Strings Rejected User Agents Remove UTF8/blog charset support from .htaccess file. Only necessary if you see odd characters or punctuation looks incorrect. Requires rewrite rules update. Required 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 Configuration Rewrite Rules Rewrite rules must be updated Rules must be added to %s too: Sample WP-Cache config file (<strong>%s</strong>) does not exist. Verify your installation. Save Save Changes Save Files Save Settings Save Strings Save UA Strings Scheduler Scheduling next preload refresh in %d minutes. Scroll down the Advanced Settings page and click the <strong>Update Mod_Rewrite Rules</strong> button. Search Pages Send me status emails when files are refreshed. Send non-secure (non https) request for homepage Set 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 simple mode and enable mobile support. Settings Simple CDN Simple caching. Since you are using mod_rewrite to serve cache files, you must choose a directory in your web root which is <q>%s</q> and update the mod_rewrite rules in the .htaccess file. Single Posts Site URL Sites that want to serve lots of newly generated data should set the <em>Cache Timeout</em> to 60 and use the <em>Timer</em> scheduler set to 90 seconds. Sites where an external data source updates at a particular time every day should set the timeout to 86400 seconds and use the Clock scheduler set appropriately. Sites with lots of static content, no widgets or rss feeds in their sidebar can use a timeout of 86400 seconds or even more and set the timer to something equally long. Sites with widgets and rss feeds in their sidebar should probably use a timeout of 3600 seconds and set the timer to 600 seconds. Stale files will be caught within 10 minutes of going stale. Skip https URLs to avoid "mixed content" errors Sorry. My blog is locked down. Updates will appear shortly Speed up images and photos (free) Stale cached files are not removed as soon as they become stale. They have to be removed by the garbage collecter. That is why you have to tell the plugin when the garbage collector should run. Strings 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. Submit a blank entry to set it to the default directory, WP_CONTENT_DIR . /cache/. Supercache Uninstall Problems Support for Bad Behavior. (Only WPCache caching supported, disabled compression and requires Bad Behavior in "%s/plugins/bad-behavior/") Tags Test Cache Test your cached website by clicking the test button below. Text 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 <em>Timer</em> scheduler tells the plugin to run the garbage collector at regular intervals. When one garbage collection is done, the next run is scheduled. The URL of your site. No trailing <code>/</code> please. The WP Super Cache configuration file is <code>%s/wp-cache-config.php</code> and cannot be modified. That file must be writeable by the web server to make any changes. The WordPress CRON jobs system is disabled. This means the garbage collection system will not work unless you run the CRON system manually. 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 was created by another plugin or by your system administrator. Please examine the file carefully by FTP or SSH and consult your hosting documentation. The file <code>%s.htaccess</code> 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 simple mode without them but in expert mode, your visitors may see corrupted pages or out of date content however. The following recommended settings will be enabled: The free %1$sJetpack plugin%2$s has a %3$sSite Accelerator%2$s feature that is easier to use than the CDN functionality in this plugin. However files will be cached "forever" and will not update if you update the local file. Files will need to be renamed to refresh them. The %3$sJetpack documentation%2$s explains more about this. The location of the plugin configuration file can be changed by defining the WPCACHECONFIGPATH constant in wp-config.php. If not defined it will be set to WP_CONTENT_DIR. The logout link will log out all WordPress users on this site except you. Your authentication cookie will be updated, but you will not be logged out. 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 <code>/</code> please.<br />Example: <code>%2$s</code>. The pages do not match! Timestamps differ or were not found! The plugin could not update %1$s.htaccess file: %2$s.<br /> The new rules go above the regular WordPress rules as shown in the code below: The plugin detected a bare directory index in your cache directory, which would let visitors see your cache files directly and might expose private posts. The rewrite rules required by this plugin have changed or are missing. The timestamps on both pages match! There are no best garbage collection settings but here are a few scenarios. Garbage collection is separate to other actions that clear our cached files like leaving a comment or publishing a post. These <a href="https://www.wikipedia.org/wiki/CNAME_record">CNAMES</a> 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.<br />Example: %2$s These settings can be modified on the Advanced Settings page. Things you can do: 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. Timer: Timestamps do not match Timestamps not found To serve static html files your server must have the correct mod_rewrite rules added to a file called <code>%s.htaccess</code> Too many cached files, no listing possible. Tracking Parameters Tracking parameters to ignore when caching. Visitors from Facebook, Twitter and elsewhere to your website will go to a URL with tracking parameters added. This setting allows the plugin to ignore those parameters and show an already cached page. Any actual tracking by Google Analytics or other Javascript based code should still work as the URL of the page is not modified. Try out the <a href="%1$s">development version</a> for the latest fixes (<a href="%2$s">changelog</a>). URI Unfortunately, WordPress cannot find the file wp-cron.php. This script is required for the correct operation of garbage collection by this plugin, WordPress scheduled posts as well as other critical activities. Uninstall this plugin on the plugins page. It will automatically clean up after itself. If manual intervention is required, then simple instructions are provided. Update Update Direct Pages Update Mod_Rewrite Rules Update Status Use the <a href="%1$s">Debug tab</a> for diagnostics. Use the <em>Timer</em> or <em>Clock</em> schedulers to define when the garbage collector should run. Username/Password: %s Very fast caching plugin for WordPress. View Mod_Rewrite Rules Visit the <a href="%1$s">support forum</a>. WARNING: attempt to intercept updating of config file. WP Super Cache WP Super Cache Warning! WP 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 <a href="%s">plugin admin page</a> to enable caching. WP Super Cache mod rewrite rules were detected in your %s.htaccess file.<br /> 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 <a href="%s">the admin page</a> to enable and configure the plugin. WP Super Cache: could not delete files WP-Cache WP-Cached WP-Super-Cache WP-Super-Cached WPTouch WPTouch plugin detected! Please go to the Supercache plugins page and enable the WPTouch helper plugin. WPTouch support is now %s Warning Warning! Warning! %s is writeable! Warning! <strong>PRELOAD MODE</strong> activated. Supercache files will not be deleted regardless of age. Warning! Compression is disabled as gzencode() function was not found. Warning! Garbage collection is not scheduled! Warning! PHP Safe Mode Enabled! Warning! The following settings are disabled because Expert caching is enabled. Warning! WP Super Cache caching <strong>was</strong> broken but has been <strong>fixed</strong>! The script advanced-cache.php could not load wp-cache-phase1.php.<br /><br />The file %1$s/advanced-cache.php has been recreated and WPCACHEHOME fixed in your wp-config.php. Reload to hide this message. Warning! WP Super Cache preload was interrupted but has been restarted. Warning! You are not allowed to delete that file Warning! You may not be allowed to use this plugin on your site. Warning! You must set WP_CACHE and WPCACHEHOME in your wp-config.php for this plugin to work correctly: Warning! Your hostname "%s" resolves to %s Warning: do not use a shared directory like /tmp/ where other users on this server can modify files. Your cache files could be modified to deface your website. When Expert cache delivery is enabled a file called <em>.htaccess</em> is modified. It should probably be in the same directory as your wp-config.php. This file has special rules that serve the cached files very quickly to visitors without ever executing PHP. The .htaccess file can be updated automatically, but if that fails, the rules will be displayed here and it can be edited by you. You will not need to update the rules unless a warning shows here. WordPress 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 already have Jetpack installed and %1$sSite Accelerator%2$s enabled on this blog. The CDN here is disabled to avoid conflicts with Jetpack. You already have Jetpack installed but %1$sSite Accelerator%2$s is disabled on this blog. Enable it on the %3$sJetpack settings page%2$s. You are using expert mode to serve cache files so the plugin has added <q>Options -Indexes</q> to the .htaccess file in the cache directory to disable indexes. However, if that does not work, you should contact your system administrator or support and ask for them to be disabled, or use simple mode and move the cache outside of the web root. You attempted to enable compression but `zlib.output_compression` is enabled. See #21 in the Troubleshooting section of the readme file. You can define different CDN URLs for each site on a multsite network. You can edit the file yourself. Add the following rules. You may experience problems running this plugin because SAFE MODE is enabled. You must give the full path to the directory. You must make %s writable to enable this feature. As this is a security risk, please make it read-only 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 <a href="http://php.net/features.safe-mode">safe mode manual page</a> for further details. You or an administrator must disable this. See the <a href="http://php.net/features.safe-mode">safe mode manual page</a> 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: You should check Page 1 and Page 2 above for errors. Your local server configuration may not allow your website to access itself. You should delete these files manually.
You may need to change the permissions of the files or parent directory.
You can read more about this in the Codex at
%s
Thank you. Your WP-Cache config file (<strong>%s</strong>) is out of date and not writable by the Web server. Please delete it and refresh this page. Your cache directory (<strong>%1$s</strong>) did not exist and couldn’t be created by the web server. Check %1$s permissions. Your cache directory (<strong>%1$s</strong>) or <strong>%2$s</strong> need to be writable for this plugin to work. Double-check it. Your comment is awaiting moderation. Your server is configured to show files and directories, which may expose sensitive data such as login cookies to attackers in the cache directories. That has been fixed by adding a file named index.html to each directory. If you use simple caching, consider moving the location of the cache directory on the Advanced Settings page. 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 site is using a very old version of WordPress. When you update to the latest version everyone will be logged out and cookie information updated. 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 <code>wp-content</code> and <code>wp-includes</code> 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 <a href="https://www.google.com/search?q=cdn+origin+pull" target="_blank">origin pull</a>. Zlib Output Compression Enabled! [%1$s] %2$d posts refreshed [%1$s] Cache Preload Started [%1$s] Cache Preload Stopped [%1$s] Refreshing %2$s taxonomy from %3$d to %4$d [%1$s] Refreshing posts from %2$d to %3$d [%1$s] WP Super Cache GC Report [%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. all disable disabled enabled https://automattic.com/ https://wordpress.org/plugins/wp-super-cache/ index.html files have been added in key directories, but unless directory indexes are disabled, it is probably better to store the cache files outside of the web root of %s seconds timezone date formatY-m-d G:i:s PO-Revision-Date: 2023-10-25 10:46:34+0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Plural-Forms: nplurals=1; plural=0;
X-Generator: GlotPress/4.0.0-alpha.11
Language: zh_CN
Project-Id-Version: Plugins - WP Super Cache - Stable (latest release)
确保它们在已有的 WordPress 规则前。 你的站点没有 %1$sJetpack%2$s 但您可以%3$s安装它%2$s。站点加速器功能可在任何 WordPress 站点上免费使用，并提供与其他 CDN 服务相同的优势。你应该试一试！ %s %s 文件 %s 已缓存页面 %s 已过期页面 %s 可被写入。由于存在安全风险，请在页面生成后设置为只读权限。 %s.htaccess 已经被必需的 mod_rewrite 规则更新。请检查它们是否正确。它们应该看上去这样： %s/advanced-cache.php</em> 无法更新。 (仅支持传统模式，并且需要禁用压缩以及确保 <a href="http://www.bad-behavior.ioerror.us/">Bad Behavior</a> 插件在 "%s/plugins/bad-behavior/" 目录中) (在某些繁忙的大型站点上可能会不准确) (仅记录来自该 IP 的请求，您的 IP 是 %s) * 以上链接（Jetpack 除外）指向作者无法控制的网站。 在测试任何新软件时建议小心。 .htaccess文件可能需要被移动 304浏览器缓存。 通过检查自浏览器上次请求页面后页面是否已更改来提高网站性能。 默认情况下禁用304支持，因为某些主机有与过去使用的标头（headers）的问题， <a href="%s">Jetpack Boost</a> 通过生成关键的 CSS、延迟 Javascript 等等来帮助加速您的网站。 <a href="%s">Jetpack</a> 提供您建立一个成功的 WordPress 网站所需要的所有东西包括图像/照片 CDN（免费）和视频托管服务（需付费）。 <a href="%s">使用谷歌图书馆</a>您可以从谷歌服务器加载一些常用的 Javascript 库。讽刺的是，它可能会降低你的Yslow得分。 <a href="%s">WP Crontrol</a> 是一款调试垃圾回收器和预缓存问题的利器。 <a href="%s">Yahoo! Yslow</a> 统计分析页面并能基于一系列高性能规则的方法来提高性能。您能在 <a href="%s">GTMetrix</a> 试用在线工具。 <a href="%s">commonWP</a> 的作用与“使用 Google 库”相同，并将一些常用的静态文件卸载到外部 CDN。 <a href="https://codex.wordpress.org/Changing_File_Permissions">这个页面</a> 讲述了如何修改文件权限。 <abbr title="Coordinated Universal Time">UTC</abbr>时间是<code>%s</code> <acronym title="使用 PHP 生成缓存文件">简单模式</acronym> <acronym title="使用 mod_rewrite 生成缓存文件">专家模式</acronym> <em>垃圾回收器</em> 是一个减少垃圾的工具。因为插件产生的缓存会随着时间推移而<em>过期</em>，因此新生成的缓存文件因此是<em>新鲜</em>的。 <h4>WP_CACHE常量添加到wp-config.php</h4><p>如果您继续看到此警告消息，请参阅<a href="https://wordpress.org/plugins/wp-super-cache/faq/">故障排除指南</a>的第5点。 必须向上移动WP_CACHE行。 <h4>WP_CACHE常量设置为false</h4><p>WordPress使用WP_CACHE常量来加载提供缓存页面的代码。 不幸的是，它被设置为false。 请编辑你的wp-config.php并在最终的require_once命令上面添加或编辑以下行：<br /><br /><code>define('WP_CACHE', true);</code></p> <strong style="color: red">警告：</strong> 请测试一些静态地址比如 %s 以便确保您的 CDN 服务在保存设置前正在工作。 <strong style="color: red">警告：</strong>您的站点地址和主页地址是不同的。这个插件正在使用 %s 作为您的站点的主页地址（URL），但如果这是错误的请使用过滤器 "ossdl_off_blog_url" 来修复。 <strong>只允许高级用户：</strong> 安装对象缓存系统。您可以选择 <a href="%s">Memcached</a>， <a href="%s">XCache</a>， <a href="%s">eAcccelerator</a> 或更多。 <strong>访问这个链接将不会显示缓存内容</strong>： <a href="%s">%s</a> <strong>错误：您的 <code>wp-config.php</code> 文件中 WP_CACHE 未被启用</strong> 并且插件无法变更。 <strong>错误：</strong> %s <strong>警告！</strong>评论缓存目前禁用。请到调试页面并启用缓存状态信息。您应该在测试前清除缓存。 <strong>警告！</strong>您尝试启用压缩但是 <code>zlib.output_compression</code> 参数已被启用。请查看 readme 文件的疑难问题解决部分的第21号解答。 <strong>警告</strong>！由于 WordPress 升级插件的方式，当您升级 WP Super
Cache 时，您上传到 WP Super Cache 文件夹（wp-super-cache/plugins/）的文件将被删除。为了避免这种损失，从不同的位置加载您的缓存插件。当您在 wp-config.php 中设置 <strong>$wp_cache_plugins_dir</strong> 新的位置时，WP Super Cache 将替换它。<br />您能找到更多细节在<a href="%s">开发者文档</a>中。 本插件需要正确的自定义链接或者固定链接结构才能正常工作。请前往 <a href="options-permalink.php">固定链接设置</a> 页面进行配置。 我们发现了.htaccess文件中的规则和插件重写规则之间的不同。这可能是简单的空白差异，建议你比较文件的规则与下面的内容。点击’更新Mod_Rewrite的规则’按钮更新规则。 最简单的方法就是通过 ftp 客户端使用 CHMOD 命令临时修改文件权限。请确保文件全局可被写入，然后就可以了。 已被接受的文件名和拒绝的 URI 激活Jetpack Boost 将调查和投票添加到您的站点 添加跳转页面(Direct Page)： 在这里添加强制禁止缓存的页面的地址关键字。例如，如果您的地址包含年份并且您不想缓存上一年的文章，您可以直接填写 ’/2004/’。WP-Cache 将会搜索所有符合条件的页面并且不缓存它们。 添加想要被缓存的文件名，即使它们出现在上面的被拒绝列表里面。 添加你自己的规则。编辑 %s.htaccess，找到<code># BEGIN WPSuperCache</code>和<code># END WPSuperCache</code>之间的代码块。有两部分看起来非常相似。在 <code>%%{HTTP:Cookie} !^.*(comment_author_|%s|wp-postpass_).*$</code> 下面，加上这些代码：（做两次，每个部分一次） 附加 CNAME 记录 高级 有效时间 本网站的所有用户已注销刷新其登录的Cookie。 另外，您还可以自行编辑您的 <code>%s.htaccess</code> 文件并添加以下代码 (在任何 WordPress 规则之前): 始终缓存文件名 显示航天飞机的图像。前景中有两张黄色和绿色的图 存档 作者页面 Automattic 可用插件 等待修改 %s现正等待修改 Bad Behavior Bad Behavior 兼容%s 没有找到 Bad Behavior 插件。请检查您的安装。 提高您的页面速度分数 CDN CDN功能由<a href="https://cn.wordpress.org/plugins/ossdl-cdn-off-linker/">OSSDL CDN Off Linker</a> 开发者 <a href="http://mark.ossdl.de/">Mark Kubacki</a>开发。 CRON 计划任务已禁用 缓存内容 缓存实现方式 缓存包含页面内容的 HTTP 头（headers）文件。 缓存位置 缓存重建。 缓存限制 缓存状态消息 缓存测试 缓存超时时间 清理到期缓存计划任务执行失败，将会在10秒后重试。 缓存到期检查任务已经执行了不少于30秒。您可能需要更经常地运行垃圾回收期。 缓存插件是 PHP 脚本，您可以在 WP Super Cache 文件夹（wp-super-cache/plugins/）内的一个专用文件夹中找到。他们与 WP Super Cache 同时加载，并且在常规 WordPress 插件前加载。 缓存重建。当新缓存生成时调用缓存文件给匿名用户。 缓存统计信息不是自动生成的，您需要点击下面的链接来重新生成。 缓存统计已于 %s分钟前生成。 已缓存 %s秒前已缓存 缓存都是有一定的新鲜时间的，您可以在本页的 <em>缓存过期时间</em> 文本框进行设置。 缓存的页面都以html和PHP文件的形式存储在您的服务器。如果您想要删除它们，请使用下面的按钮。 从 %1$s 已缓存的页面：<strong>%2$s</strong> 缓存功能 禁用缓存功能 启用缓存功能 已登录访客禁用缓存。 缓存已禁用。 页面未缓存。 在该博客的站点网络管理页面上缓存功能已被禁用。 缓存是一个很好的开始，但要最大限度地提高您的网站速度，还有更多的方法。看看你的缓存对你的网站有多大的帮助，用Jetpack Boost使它变得快如闪电，这是Super Cache工程师开发的最简单的WordPress速度优化插件。 缓存只是让站点运行更快的一种方法，这里有一些其它插件提供类似功能： 取消预加载缓存 无法继续... 清修复之前遇到的问题然后重试。 无法删除目录 无法更新 .htaccess 文件 分类 修改过期设置 更改缓存文件的位置。默认值是WP_CONTENT_DIR. /cache/ 即%s。 每当到了您设定的 <strong>(UTC)</strong> 时间或者任务间隔检查过期的缓存文件。 每隔 <em>interval</em> 秒定期检查过期的缓存文件。 每5分钟检查一次首页。 检查您的网站在桌面和移动设备上的性能得分。 查看<a href="%s">插件文档</a>。 检查和删除过期文件是昂贵的，但这也使昂贵远离他们。在一个非常繁忙的站点，您应该设置过期时间为 <em>600 秒</em>在一天中多次去试验不同的值并访问这个页面去看看有多少过期文件。 正在清理过期的 supercache 文件。 当有新文章或页面的发布或更新时清除之前的缓存文件。 出错时清除缓存。 时间： 粗略的（Coarse）文件已锁定。您不需要这个文件，因为它将拖慢您的网站。 评论审核已启用。您的评论可能需要一段时间后才能被显示。 压缩页面以便让来访者更快浏览。 压缩默认已禁用，因为有些主机对压缩过的文件处理有问题。勾选或取消勾选该功能会清除缓存。 设置文件已变更，有些数值可能是错误的。请通过 "设置" 菜单重新加载。 配置文件丢失，%1$s目录（<strong>%2$s</strong>）不是Web服务器可写的。请检查它的权限。 内容 无法更新 %s！必须设置</em> WPCACHEHOME。 当前规则 目前正在登录：%s 尊敬的用户，
WP Super Cache高速缓存已从您的博客删除，但在你的.htaccess mod_rewrite并未删除。请编辑以下文件，并删除“BEGIN WPSuperCache'和'END WPSuperCache”之间的代码。请先备份文件！
%s
问候，WP Super Cache插件
https://wordpress.org/plugins/wp-super-cache/ 亲爱的用户，
WP Super Cache 已经从您的博客中删除或禁用，但有些文件
无法删除。
调试 删除 删除缓存 删除所有博客上的缓存 删除已缓存页面 删除已过期文件 删除 Super Cache 插件的缓存文件 删除 Super Cache 插件的缓存文件 (新窗口中打开) 删除当前页面的缓存 删除已缓存文件 删除插件的 mod_rewrite 规则，它们是 %s.htaccess 文件中从 <code># BEGIN WPSuperCache</code> 开始到 <code># END WPSuperCache</code> 结束的代码块，随后请刷新本页来重建规则。 正在删除 supercache 的相关文件： <strong>%s</strong><br /> 正在删除 wp-cache 的相关文件： <strong>%s</strong><br /> 对开发者：为了使您自己的插件与锁定功能兼容，请检查 "WPLOCKDOWN" 常量。以下代码将会确保您的插件遵守 WPLOCKDOWN 设置。 直接缓存的文件 直接缓存文件是直接由你博客所处的%s所创建的文件。如果你期待一个文章或页面的访客达到Digg或Slashdot的水平，，此功能才有用。 匹配静态文件要包含的目录。使用逗号作为分隔符。默认值为<code>wp-content，wp-includes</code>，如果该字段为空则强制执行。 禁用 禁用日志 禁用登录访客的缓存。 禁用在浏览器中设置了cookie的访客的缓存。 已禁用 取消 像这样的方式显示每页末尾的评论： 设置这些cookie时不要缓存页面。在此处添加cookie名称，每行一个。匹配片段，所以“test”将匹配“WordPress_test_cookie”。（仅限简单缓存） 不要缓存例如下列格式的页面。请见 <a href="https://codex.wordpress.org/Conditional_Tags">Conditional Tags</a> 文档查看所有格式的具体说明。 Domain Mapping 已检测到 Domain Mapping 插件！请前往本插件的设置首页启用 Domain Mapping 插件支持。 Domain Mapping 兼容%s 不要为 GET 请求缓存。(地址结尾为?x=y) 通用 编辑 <code>%s</code> 并添加如下内容：<br /> <code>define('WP_CACHE', true);</code><br /否则，<strong>WP-Cache 将不会被执行</strong>。 当垃圾回收器运行时发送邮件通知我。 当有检查时发送邮件提醒站点管理员。(对测试十分有用) 启用 开启 CDN 支持 启用缓存 启用日志 为所有访客启用缓存。 启用动态缓存。（有关示例代码，请参阅<a href="%s">FAQ</a> 或 wp-super-cache/plugins/dynamic-cache-test.php。） 在这里启用调试页面的日志记录。这会帮助您跟踪问题。 已启用 启用或禁用该插件以便移除当新的待审核评论产生时的 "您的评论正在等待审核。" 提示。 错误 错误：%s 配置文件无法加载，请刷新页面。 错误：%s 配置文件丢失，请刷新页面。 错误：配置文件为只读，请确保 %s 等文件可写。 错误：临时文件无法重命名成配置文件，请确保 %s 等文件可写。 错误：包含 %s 等配置文件的目录为只读，请确保该目录可写。 如果是之前有则排除 如果以上的字符串中有任何一个符合，那么将不会被写入至重写规则中。请使用半角逗号隔开，例如 <code>.php, .flv, .do</code>,，并且无论如何不要删去 <code>.php</code> (默认)。 已存在的跳转页面 专家缓存模式需要改变重要的服务器文件并且如果启用可能需要手动干预。 到期文件是那些存在时间大于%s秒的文件。它们仍在被调用并会定期被删除。 到期时间和垃圾回收器 首页额外检查。 (极少数情况下会停止对首页的缓存) 失败 快速视频托管（需付费） Feeds 正在抓取 %s 的初始缓存： 抓取 %s 的第一份缓存拷贝： 抓取 %s 的第二份缓存拷贝： 文件 了解Super Cache对您的网站有多大的加速作用 修复设置 通过在这里调试来修复故障，调试功能会在缓存文件目录下生成日志。 为了更好的访问体验，您应该启用 "手机设备支持" 或者删除 .htaccess. 文件中的手机重写规则。请查找 "2.0\ MMP|240x320" 文本并删除它们。 例如：为了缓存 <em>%1$sabout/</em>，您需要访问 %1$sabout/ 或 /about/。缓存文件将会在下次匿名用户来访时再次生成。 首页 首页文字 WordPress 已启用 GZIP 压缩，wp-cache 将会自动忽略直到您禁用 gzip 压缩。 垃圾回收器 这个插件的垃圾回收通过定期清除出过期老的缓存页面。使用 <a href="#expirytime">此表单</a> 启用它。 小时:分钟 隐藏文件列表 主页 哪些缓存页面是没有过期的？设置为0可以禁用垃圾回收器。建议数值为3600。 我有 99% 的把握：这不是 WP Super Cache 的 Bug，这种情况只会在极其罕见的情况下发生。如果您仍然不放心，我建议您每5分钟做一次对站点的简单检查，以便验证站点是否运行正常。如果产生任何问题，您会收到系统发送的邮件通知。 IP 地址 如果它是由另一个缓存插件创建的，请在激活 WP Super Cache 之前先卸载该插件。 如果该操作未删除文件，则应手动删除文件。 如果不能工作，请确保文件 <em>%s/advanced-cache.php</em> 不存在： 如果该目录不存在，它将被创建。请确保您的Web服务器用户有写入访问父目录的权限，父目录必须是已经存在的。 如果新的缓存目录不存在，它将被创建，旧的缓存目录的内容将被移动到那里。否则，旧的缓存目录将被留在原处。 如果卸载这个插件，请确保目录<em>%s</em>是有Web服务器写入权限，<em>advanced-cache.php</em>和<em>cache-config.php</em>文件可被自动删除。（建议保持这些文件可写！） 如果刚才第一次安装了WP Super Cache，你可以关闭此消息。否则，你应该可以点击下面的注销链接刷新所有记录在这里的WordPress用户的登录的Cookie。 如果您需要此问题的支持，请与您的主机提供商联系。 在’预缓存模式’中常规垃圾回收器将被禁用目的是旧缓存文件不被删除。在预缓存模式下这是推荐设置。 在某些情况下，有以下2个问题可能会发生：<ol><li>加载首页时会变成 zip 档案下载。</li><li> 如果您的博客使用静态首页，并且固定链接结构类似于 <em>/%category%/%postname%/</em> ，某些错误的页面会被当做首页进行缓存。</li></ol> 包括目录 安装Jetpack Boost 每10分钟进行一次间隔垃圾收集，缓存生存期为30分钟（如果尚未配置）。 任务间隔： 貌似 mod_rewrite 模块尚未安装。也许情况并不是这样，尤其是当您不使用 Apache 作为服务器程序的时候。请检查 mod_rewrite 模块是否被加载。这对于 Super Cache 的静态文件的调用是必需的。不过您可以使用 PHP 缓存模式或者传统模式运行本插件。 按<a href="https://codex.wordpress.org/Giving_WordPress_Its_Own_Directory"></a>描述，您在一个子目录下安装了WordPress。但是WordPress写入的是安装目录下的.htaccess，而不是在你网站目录。<br />当你更新这个插件的重写规则时，你需要复制该文件到您的网站目录。该问题将在未来解决。 Jetpack CDN Jetpack 移动主题 Jetpack移动主题支持现在是%s %s中未找到Jetpack。请安装它并启用移动主题和这一插件，进行移动访问的高速缓存。 请牢记本缓存插件仅供高级用户使用。为了创建和管理他们，您将需要广泛的 PHP 与 WordPress 操作知识。 最后登录：%s 稍后初始化。在 WordPress 加载后显示缓存文件。 少量邮件，缓存第一篇发送1封邮件，缓存结束时发送再1封邮件。 列出所有已缓存的文件 在该页列出所有最新的缓存页面。 它会在一个已经登出的浏览器环境中加载首页并检查 html 文件结尾的时间戳，然后再次加载页面并对比时间戳。如果时间戳相符则缓存正在工作。 本地时间是 <code>%1$s</code> 锁定 锁定： 注销 将 %1$s 通过 chmod 或者 ftp 客户端设置为可被写入(<em>chmod 777 %1$s</em>) 并刷新本页。这只是一个临时的操作，您需要随后恢复该文件之前的只读权限。(将之前括号内的777改为755，并执行修改后的命令) 让已知用户匿名使他们浏览的内容是缓存文件。 如果文本框留空，将会移除直接页面列表中内容的并删除缓存文件。 大量邮件，每 %d 个帖子 2 封邮件。 适量邮件，每 %d 个帖子 1 封电子邮件。 杂项 找不到 Apache 模块 手机浏览器 手机前缀 支持移动设备。(需要外部插件或主题。更多详情，请参阅 <a href="https://jetpack.com/support/wp-super-cache/wp-super-cache-faq/"> 常见问题</a>）。 检测到针对手机的重写规则 若要对手机用户进行配置，需要额外添加规则到 .htaccess 文件中，或者您启用传统模式。这是您的选择(有些困难)： Mod Rewrite 规则 Mod Rewrite 规则必须被更新！ Mod Rewrite 规则已更新！ Mod rewrite 模块可能未安装！ 需要帮助？ 需要帮助？请查看 <a href="%1$s">文档</a>。其中包括安装文档、常见问题和故障排除提示。<a href="%2$s">支持论坛</a>也可供使用。您的问题可能已经有人回答过了。 新规则 最新的已缓存页面： 下次垃圾收集计划任务将会在 <strong>%s UTC</strong> 开始 Nginx 规则能在<a href="%s">这里</a>查阅，但是它不被官方支持。 不发送邮件 每次配置不允许编辑%s。 提示： 注意：如果您使用 Cloudflare 或者其他透明前端代理服务，这个测试可能失败。<ol><li> 如果您启用了 Cloudflare 的压缩服务，这个插件可能检测到不同的页面并报告一个错误。</li><li> 尝试使用 Cloudflare 的开发模式去执行测试。您可以在测试成功后禁用开发模式。</li></ol> 注意：由于 <em>Mod_rewrite 模式或者传统模式已启用</em>，默认将显示高级设置选项卡。 注意︰ PHP缓存已启用，但检测到Supercache mod_rewrite规则。将使用这些规则提供缓存的文件。如果您的网站工作正常，请忽略此消息。否则为您可以编辑您的安装的根目录中的.htaccess文件并删除SuperCache规则。 邮件通知 OK Off-site URL 当某页面有新评论时，只刷新该页面的缓存。 或者，<em>定时</em>计划程序允许垃圾回收在特定时间运行。如果设置为每小时一次或两次运行，垃圾收集器将首先安排您在此处输入的时间。然后它会在指定的时间再次运行。如果设置为每天运行，它会每天在指定时间运行一次。 其他站点工具 PHP 正在压缩发送到来访者的数据。建议禁用该功能，因为本插件已经缓存了压缩后的输出数据而不是重复压缩多次它们。同时请查看 readme 文件的疑难问题解决部分的第21号问题。查看 <a href="http://php.net/manual/en/zlib.configuration.php">这个页面</a> 以了解配置 php.ini 的介绍。 页面 %d: %d (%s) 第一页： %s 第二页： %s 页面 固定链接结构出错 请<a href="%s">评价我们</a>并给出反馈。 请从 wp-super-cache/wp-cache-config-sample.php 创建 %s/wp-cache-config.php 请查看 readme.txt 中 <a href="%s">疑难问题解决部分</a> 的第16号问题 请查看 <a href="%1$s/wp-super-cache/readme.txt">readme.txt</a> 以了解卸载流程。请在文件中搜索 "How to uninstall WP Super Cache"以便快速浏览。 请访问 %1$s 以清除您的站点的首页缓存，该缓存是错误的或者缺失文字 "%2$s"！ 由于您的首页正在被加载，请自行访问 %s 以清除首页的缓存！ 插件兼容 预缓存 预缓存 %s 篇文章。 立即预加载缓存 预加载已激活 预缓存已经重新启动。
%s 预缓存模式（垃圾回收器已禁用。推荐。） 预缓存模式已启用。Supercache 文件将永不过期。 预缓存标签，分类以及其他。 预缓存将会创建大量新文件，并且会将所有文章进行缓存。如果您有10000篇以上文章，不建议您使用该功能，尤其是在共享主机上。 缓存预加载已禁用。请确保简单或专家模式已启用或者联系您的主机管理员。 如果您启用锁定，那么它将会为站点运行高峰时期做好准备。当这项功能启用时，新评论或文章将不会立即刷新至已缓存的静态文件。 <a href="https://cn.wordpress.org/plugins/wordpress-mu-domain-mapping/">点击查看 Domain Mapping 插件对同主机多站点的支持</a>。 <a href="https://cn.wordpress.org/plugins/wptouch/">点击查看 WPTouch 的手机主题和插件本身的支持</a>。 提供对映射多个域名到一个博客的 Domain Mapping 插件的支持。 提供对 WPTouch 移动主题和插件的支持。 支持<a href="https://cn.wordpress.org/plugins/jetpack/">Jetpack</a>移动主题和插件。PHP缓存模式和移动的支持也将被启用。 提供对 Jetpack 移动主题和插件的支持。PHP 缓存模式和移动支持也将被启用。 给插件评个分吧！ 只读模式。设置无法更改。 只读： 推荐 有用的链接和插件 每%s分钟刷新预缓存文件(设置为0则禁用，至少%d分钟。) 刷新本页以便更新 <em>%s/advanced-cache.php</em> 当文件权限更改后请刷新本页。 以下文章已被刷新： 重新生成缓存统计信息 Cookies被拒绝 URL字符串被拒绝 已拒绝的用户代理(User Agent) 移除 .htaccess 文件中的 UTF8/blog 字符集。这个功能只适用于当您发现文件中字符不正确时。本功能需要更新重写规则。 这是必需的以便能够正确调用缓存文件。 该模块的作用是设定 supercache 页面的缓存信息。没有该模块，IE7用户将只会看见旧页面。 恢复默认设置 重写（Rewrite）规则 重写规则必须被更新 规则必须也被添加至 %s ： 样品WP-Cache配置文件<strong>（%s）</strong>不存在。检查您的验证。 保存 保存修改 保存文件 保存设置 保存 保存用户代理(UA)字段 计划 下次预缓存任务将在%d分后开始。 滚动查看高级选项卡，找到并点击 <strong>更新 Mod_Rewrite 规则</strong> 按钮。 搜索页面 当缓存文件刷新完毕后发送邮件通知。 发送不安全的(非 https) 首页请求 设定缓存文件的到期时间。没有该模块时，当来访者刷新或者留下评论时可能不会看到新页面。 设置到期时间为0秒以便禁用垃圾回收器。 设置插件为传统模式并且启用手机支持。 设置 简单的CDN 简单的缓存。 由于您使用mod_rewrite服务缓存文件，你必须选择在Web根目录<q>%s</q>选择一个文件夹并在.htaccess文件中更新mod_rewrite规则。 单一文章 站点地址（URL） 有大量新数据产生的站点应该设置<em>缓存超时时间</em>为60并设置<em>定时器</em>时间为90秒。 每天有固定更新产生的站点应该设缓存超时时间为86400秒并正确设置时钟时间。 有大量静态内容且在侧边栏没有挂件和 rss 输出的站点，应该设置超时时间为86400秒或更长并设置定时器为一个很长的时间。 在侧边栏有挂件和 rss 输出的站点应该设置超时时间为3600秒，并设置定时器为600秒。过期缓存将会在10分钟内随时被收集。 忽略 https 地址以避免 "mixed content" 错误 抱歉，本博客目前处于锁定中，稍后会进行更新。 加速图像与照片（免费） 过期的缓存文件并会被立刻删除。它们会被垃圾回收器清除。这就是您需要对垃圾回收器进行配置的原因。 HTTP ’中的字符串；浏览器’ 防止WP-Cache缓存网络机器人的http头, 蜘蛛, 网络爬虫’的请求。请注意超级缓存文件仍然会被发送给这些代理。 如果提交空白条目会将其设置恢复为默认值，WP_CONTENT_DIR . /cache/。 Supercache 卸载问题 对 Bad Behavior 的支持。（只有 WPCache 缓存支持，禁用压缩并在 "%s/plugins/bad-behavior/" 中需要 Bad Behavior） 标签 测试缓存 点击下面的测试按钮测试缓存效果。 搜索您的首页有文字。如果不填该处文字，缓存将被清除。留空以禁用。 感谢您的升级。 <em>定时器</em> 告诉插件间隔多久运行垃圾回收器。当一次回收完毕时，下次任务将会被设计划。 您的站点地址（URL）。请不要在结尾加<code>/</code>。 WP Super Cache设置文件<code>%s/wp-cache-config.php</code>无法改写。该文件必须设置为服务器可写才能进行改写。 WordPress 的 CRON 计划任务已禁用。这意味着除非您手动运行 CRON 计划任务，否则垃圾回收系统将无法运行。 由于首页缺失 "%2$s" ，所有缓存已被清除。请访问 %1$s 以检查缓存是否已被清除。 由于首页正在被加载，您的博客的所有缓存已被清除。请访问 %s 以检查缓存是否已被清除。 文件%s是由另一个插件或系统管理员创建的。 请通过FTP或SSH仔细检查文件，并查阅您主机的帮助文档。 <code>%s.htaccess</code> 文件无法被服务器变更。请使用 chmod 命令或 ftp 客户端来修正权限。 缺少以下Apache模块。 插件将在没有它们的情况下以简单模式工作，但在专家模式下，访客可能会看到损坏的页面或过时的内容。 将启用以下建议设置： 免费的 %1$sJetpack 插件%2$s具有%3$s站点加速器%2$s功能，该功能比此插件中的 CDN 功能更易于使用。但是，文件将被“永久”缓存，即使更新本地文件，也不会更新缓存。需要重命名文件才能刷新它们。 %3$sJetpack 文档%2$s解释了更多相关信息。 通过在wp-config.php中定义WPCACHECONFIGPATH常量，可以更改插件配置文件的位置。如果未定义，则将其设置为WP_CONTENT_DIR。 该注销链接将注销除你之外的所有的WordPress用户。您的身份验证cookie将被更新，但你不会被注销。 自您上次安装该插件之后mod_rewrite规则有变更。你必须删除旧的supercache规则才能更新新的规则。在您编辑.htaccess之后再刷新本页。如果您想手动更新，修改下面这行：%1$s，让它变成这样:%2$s。唯一的变化只是"HTTP_COOKIE"变成"HTTP:Cookie"，"wordpressuser"变成"wordpress"。这是WordPress2.5的变更，但如果你敢于尝试的话，这是向后兼容的。 这个新的URL替换%1$s用来重写，不要用<code>/</code>结尾，<br />例如<code>%2$s</code>。 页面不相符！时间戳有差异或者不存在！ 这个插件不能更新 %1$s.htaccess 文件： %2$s。<br />新规则超过常规的
WordPress 规则，如以下代码所示： 该插件检测到您的缓存目录的目录索引，这将让访问者看到你的缓存文件，可能会暴露一些私密的文章。 插件需要的重写规则已被更改或者缺失。 两个页面的时间戳相符！ 没有十分完美的垃圾回收器设置，不过它已被单独分离出来，这样清理缓存文件就像留下一条评论或者发布文章一样简单。 这些<a href="https://www.wikipedia.org/wiki/CNAME_record">CNAMES</a>将用于代替%1$s进行重写（除了上面的场外网址）。 使用逗号作为分隔符。 对于具有大量静态文件的页面，这可以提高浏览器性能。 可能还需要在CDN上配置CNAMEs。<br />示例：%2$s 可以在“高级设置”页面上修改这些设置。 您可以做的： 预缓存的功能是缓存所有已发布的页面和文章。它会创建 supercache 静态文件，这样的话，未知用户(包括搜索引擎蜘蛛)将会获得缓存后的页面。这将帮助您的站点的 Google PR 提升，因为 Google 会把网站的响应速度作为评判网站的标准。 这将不会影响电脑用户，但是手机用户将会访问未缓存的页面。 定时器: 时间戳不匹配 时间戳未找到 如果要使缓存页面生效，您的服务器必须要有包含正确的 mod_rewrite 规则的 <code>%s.htaccess</code> 文件 缓存文件太多，没有列表可用。 追踪参数 缓存时要忽略的跟踪参数。来自Facebook、Twitter和其他网站的访问者将访问添加了跟踪参数的URL。此设置允许插件忽略这些参数并显示已缓存的页面。Google Analytics或其他基于Javascript的代码的任何实际跟踪都应该仍然有效，因为页面的URL没有被修改。 尝试<a href="%1$s">开发版本</a>，查看最近的修复信息(<a href="%2$s">更新日志</a>)。 URI 不幸的是，WordPress 找不到文件 wp-cron.php。此脚本是这个插件进行垃圾收集的正确操所需，WordPress安排文章，以及其他关键的活动。 在插件页面上卸载这个插件，它会在结束后自动清理。如果需要手动介入，会有简单说明。 更新 更新直接链接页面 更新 Mod_Rewrite 规则 更新 使用<a href="%1$s">调试选项卡</a>诊断问题。 使用 <em>定时器</em> 或 <em>时钟</em> 选项来设定垃圾回收器何时应该运行。 用户名/密码：%s WordPress的快速缓存插件。 查看 Mod_Rewrite 规则 访问<a href="%1$s">支持论坛</a>。 警告：尝试拦截配置文件的更新。 超级缓存 WP Super Cache警告！ WP Super Cache 已经检查您的博客的首页。如果您想禁用，请访问 %s 。 WP Super Cache 已禁用。请去 <a href="%s">插件管理首页</a> 开启缓存功能。 在%s.htaccess文件中，检测到WP Super Cache的mod_rewrite规则。<br /> 点击下面链接查看添加到该文件中的行。如果您已经升级插件，请确保这些规则相一致。 WP Super Cache 需要设置。请前往 <a href="%s">插件管理页面</a> 设置。 WP Super Cache: 无法删除文件 WP-Cache WP-Cached WP-Super-Cache WP-Super-Cached WPTouch 已检测到 WPTouch 插件！请前往插件设置首页启用 WPTouch 插件支持。 WPTouch 兼容%s 警告 警告! 警告！ %s 可被写入！ 警告！<strong>预缓存模式</strong> 已激活！Supercache 的缓存文件由于缓存的有效时间而不会被删除。 警告！ 压缩未启用，因为没找到gzencode() 函数。 警告！没有计划进行垃圾回收！ 警告！PHP 安全模式已启用！ 警告！ 由于启用了专家级缓存，因此禁用以下设置。 警告！WP Super Cache缓存<strong>被打破</strong> ，但<strong>已修复</strong>！该脚本advanced-cache.php无法加载WP-cache-phase1.php。 <br /><br />wp-config.php文件中的 %1$s/advanced-cache.php已被重新创建并且WPCACHEHOME已被修复。刷新可隐藏此消息。 警告！WP Super Cache 预缓存被中断并已重启。 警告！您不被允许删除这个文件 警告！ 您可能无权在此站点上使用该插件。 警告！为了使这个插件正确工作，您必须设置 WP_CACHE 与 WPCACHEHOME 在您的 wp-config.php 文件中： 警告！您的主机 "%s" 被解析至 %s 警告：不要使用像/tmp/这样的共享目录，此服务器上的其他用户可以在其中修改文件。您的缓存文件可能会被修改以破坏您的网站。 当专家缓存模式启用，一个名为 <em>.htaccess</em> 的文件将被修改。它应该是与您的 wp-config.php 在相同的目录中。这个文件有特殊规则可以给访客快速生成缓存文件而不需要执行 PHP。这个 .htaccess 文件能被自动更新，但是如果它失败了，这个规则将被显示在这里并且您可以编辑它。您不需要去更新这个规则，除非一个警告显示在这里。 WordPress 已被锁定。当产生新评论时，Super Cache 的静态文件将不会被检测到。 WordPress 没有被锁定。新的评论将会像往常一样刷新 Super Cache 的静态文件。 可写的： 您已在此博客上安装了 Jetpack 并启用了%1$s站点加速器%2$s。禁用此处的 CDN 以避免与 Jetpack 冲突。 您已经在此博客上安装了 Jetpack ，但%1$s站点加速器%2$s没有启用。在 %3$sJetpack 设置页面%2$s上启用它。 您正在使用专家模式来提供缓存文件，因此插件已将<q>选项 - 索引</q>添加到缓存目录中的.htaccess文件以禁用索引。 但是，如果这不起作用，您应该联系您的系统管理员或支持人员并要求禁用它们，或者使用简单模式并将缓存移到Web根目录之外。 您试图启用压缩但 `zlib.output_compression` 已启用。在 readme 文件的故障排除部分查阅 #21。 您可以对多站点中的每个站点定义不同的 CDN 服务地址。 您可以自己编辑该文件。添加下面的规则。 由于启用了安全模式,在插件运行时您可能会遇到问题。 您必须提供完整路径。 你必须让%s可写入才能启用此功能。由于这是一个安全隐患，您的网页生成后请将其设置为只读模式。 您或管理员可以通过更改插件脚本的组所有者以使其与Web服务器用户的组所有者相匹配来使其工作。 还必须更改%s/cache/目录的组所有者。 有关详细信息，请参阅<a href="http://php.net/features.safe-mode">安全模式手册页面</a>。 您或者管理员必须禁用该功能。更多信息请访问 <a href="http://php.net/features.safe-mode">PHP 安全模式手册</a> 。很遗憾这个操作不能在 .htaccess 文件中修改，您必须修改 php.ini 文件。 您应该通过 ftp 客户端或者以下命令更改 %s 的权限并确保它被严格限制： 您应该在出错前检查页面1和页面2。您的本地服务器设置可能不允许您的网站读取。 您可以手动删除这些文件。
您可能需要更改该文件或父目录的权限。
您可以在 Codex 上阅读更多关于 %s 方面的信息
谢谢。 您的WP-Cache配置文件(<strong>%s</strong>) 已过时，而不是由Web服务器可写的。请删除它，并刷新此页面。 您的缓存目录 (<strong>%1$s</strong>) 不存在且 Web 服务器无法创建。请检查 %1$s 的权限设置。 您的缓存目录 (<strong>%1$s</strong>) 或者 <strong>%2$s</strong>需要被设置为可写入权限。请检查有关设置。 您的评论正在等待审核。 您的服务器配置为显示文件和目录，这可能会暴露敏感数据，比如在缓存目录的登录cookie，被袭击者利用。这已得到修复，在每个目录下的文件夹加入了index.html文件。如果你使用PHP或旧的缓存，可考虑在高级设置页面，调整缓存目录的位置。 在 PHP 代码读取或者写入文件之前，您的服务器程序将会检查其属主。 您的服务器认为您的主机解析至 %s。有些服务比如垃圾回收器和定时发布功能将无法正常工作。 您的网站使用的是很旧版本的WordPress。当你更新到最新版本后，所有用户都将被登出并更新相应cookie信息。 您的网站可能使用了大量的静态文件。例如图片、Javascript和CSS这些静态文件通常可以从其他网站或CDN提供服务。因此，该插件将您网站的<code>wp-content</code>和<code>wp-includes</code>目录中的任何链接（PHP文件除外）替换为您提供的URL。这样，您可以将所有的静态内容复制到特定主机上，或者通过<a href="https://www.google.com/search?q=cdn+origin+pull" target="_blank">origin pull</a>将文件镜像到CDN。 Zlib 输出压缩已启用！ [%1$s] %2$d 篇文章已刷新 [%1$s] 预缓存已开始 [%1$s] 预缓存已停止 [%1$s] 正在刷新 从 %3$d 到 %4$d 的 %2$s 分类法 [%1$s] 正在刷新从 %2$d 到 %3$d 的文章 [%1$s] [%1$s] WP Super Cache 垃圾回收器报告 [%s] 预缓存完成 [%s] 首页检查！ [%s] 首页已被 gzip 压缩！缓存已清除！ [%s] 首页已经被 gzip 压缩！请清除缓存！ [%s] 首页不正确！缓存已清除！ [%s] 首页不正确！请清除缓存！ [%s] 预缓存可能已失去响应。 全部 禁用 已禁用 已启用 https://automattic.com/ https://wordpress.org/plugins/wp-super-cache/ 已在关键目录增加了index.html文件，但除非目录索引被禁用，最好还是在Web根目录%s之外来存储缓存文件。 秒 Y-m-d G:i:s