WP Super Cache use the whole Raiders

WP Super Cache as a classic old and very easy to use effective plug-ins, WPer has always been almost one of the things that must be installed. But it seems a lot of people still on how to use it a bit confused … so, as far as detailed …

What is WP Super Cache?

WP Super Cache generates static html files from your dynamic WordPress Blog. When an html file is generated, your server will use this file to replace the need to handle relatively more workload and more WordPress PHP script action. The generated static html file will serve most of your users, except those that are displayed in the comment form after the comment has been posted. These requests are handled by PHP. Static files are displayed for the following users: Not logged in users. There is no comment on your blog users. Or users who do not have access to a password-protected article. 99% of visitors will be served by static html files. Users who do not see static files will also benefit because those who see will see the regular WP-Cache cache file, so your server will not be as busy as usual. This plug-in will help your server handle the tide of visitors when one of your pages appears on the Digg.com or other social home page. If for some reason “super cache” can not work in your server do not have to worry about. The cache will continue to execute, but each request will need to call the PHP engine. Under normal circumstances, this is pretty good. Your visitors will not notice any slowdowns or any differences in site opening, or find that your site is undergoing heavy traffic. The super-cache html file will display faster than the PHP-generated cache file, but the difference is not obvious in daily use.

How to install:

First, you should have installed Apache mod mime and mod rewrite module, and enable WordPress fancy permalinks. Disable PHP security mode. If any of the above conditions are missing or closed, you can still use the slow WP-Cache part of this plugin. If you already have the WP-Cache plug-in installed, disable it first.

Edit the wp-config.php file to confirm that the WP_CACHE definition has been removed and remove the wp-cache-config.php file and the advanced-cache.php file from the wp-content directory. The contents are re-generated after installing WP-Super-Cache.

Upload the WP-Super-Cache directory to your plug-in directory. It will create a “wp-content / plugins / wp-super-cache /” directory. If you are using the WordPress MU version, you will need to install the plugin to “wp-content / mu-plugins / wp-super-cache /” and copy the wp-cache.php file into the mu-plugins directory. Visit the Plug-ins page in your administration page to activate WP Super Cache. Once activated, go to Settings → WP Super Cache and enable caching. If you see an error message, or a blank page, you may need to fix it. See the Frequently Asked Questions section of this article for a solution.

The mod_rewrite rule is automatically inserted into your .htaccess file. This file is located in the root directory of your space.

This file should look similar to the following: ——. Htaccess ——

RewriteEngine OnRewriteBase / RewriteCond %{REQUEST_METHOD} !=POSTRewriteCond %{QUERY_STRING} !.*=.* RewriteCond %{HTTP_COOKIE} !^.*(comment_author_|wordpress|wp-postpass_).*$ RewriteCond %{HTTP:Accept-Encoding} gzip RewriteCond %{HTTP_user_agent} !^.*(2.0 MMP|240x320|AvantGo|BlackBerry|Blazer|Cellphone|Danger |DoCoMo|Elaine/3.0|EudoraWeb|hiptop|IEMobile|iPhone |iPod|KYOCERA/WX310K|LG/U990|MIDP-2.0|MMEF20|MOT-V|NetFront|Newt|Nintendo Wii|Nitro|Nokia|Opera Mini|Palm|Playstation Portable|portalmmm|Proxinet|ProxiNet|SHARP-TQ-GX10|Small|SonyEricsson|Symbian OS|SymbianOS|TS21i-10|UP.Browser|UP.Link|Windows CE|WinWAP).* RewriteCond %{DOCUMENT_ROOT}/wp-content/cache/supercache/%{HTTP_HOST}/$1/index.html.gz -f RewriteRule ^(.*) /wp-content/cache/supercache/%{HTTP_HOST}/$1/index.html.gz [L] RewriteCond %{REQUEST_METHOD} !=POSTRewriteCond %{QUERY_STRING} !.*=.* RewriteCond %{QUERY_STRING} !.*attachment_id=.* RewriteCond %{HTTP_COOKIE} !^.*(comment_author_|wordpress|wp-postpass_).*$ RewriteCond %{HTTP_user_agent} !^.*(2.0 MMP|240x320|AvantGo|BlackBerry|Blazer|Cellphone|Danger|DoCoMo| Elaine/3.0|EudoraWeb |hiptop|IEMobile|iPhone|iPod|KYOCERA/WX310K|LG/U990|MIDP-2.0|MMEF20|MOT-V|NetFront|Newt|Nintendo Wii|Nitro|Nokia|Opera Mini|Palm|Playstation Portable|portalmmm|Proxinet|ProxiNet|SHARP-TQ-GX10|Small|SonyEricsson|Symbian OS|SymbianOS|TS21i-10|UP.Browser|UP.Link|Windows CE|WinWAP).* RewriteCond %{DOCUMENT_ROOT}/wp-content/cache/supercache/%{HTTP_HOST}/$1/index.html -f RewriteRule ^(.*) /wp-content/cache/supercache/%{HTTP_HOST}/$1/index.html [L] RewriteCond %{REQUEST_FILENAME} !-fRewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L]

—————–.htaccess—————–

Apache must be set to allow the above modules to work. If “500 internal error” occurs when responding to an anonymous guest request, you need to adjust your Apache settings.

The following settings are valid on my virtual host:
 # BEGIN supercache<IfModule mod_mime.c>  <FilesMatch ".html.gz$">     ForceType text/html    FileETag None  </FilesMatch>   AddEncoding gzip .gz  AddType text/html .gz</IfModule> <IfModule mod_deflate.c>  SetEnvIfNoCase Request_URI .gz$ no-gzip </IfModule><IfModule mod_headers.c>   Header set Cache-Control 'max-age=300, must-revalidate'</IfModule> <IfModule mod_expires.c>  ExpiresActive On  ExpiresByType text/html A300 </IfModule># END supercache
The first is the state of the cache settings.

ON: Both WP Cache and Super Cache are enabled.

No special circumstances recommended to choose this.

HALF ON: half-open mode, disable Super Cache, only enable WP-Cache cache mechanism.

OFF: Disable WP Cache and Super Cache.

Proudly tell the world your server is not afraid of the Digg effect! Do not cache pages for the logged in users check is not logged in the user cache page. Proudly tell the world your server is not afraid of the Digg effect! (Place a message in your blog footer) Clear all cache files when a post or page is published. (This may significantly slow down saving of posts) Clear all cache files when new articles or pages are published (this may significantly reduce Cache rebuild. Cache rebuild. Serve a supercache file to anonymous users while a new file is being generated. Recommended for very busy websites with lots of comments. Makes “directly cached pages” and “Lockdown mode” obsolete cache rebuild.

Displays a supercache file for anonymous visitors when a new file is being generated. This feature is recommended for very busy sites with a large number of comments. Enabling it will invalidate the “direct cached pages” page and the “lockdown mode lock mode”. Coarse file locking. You probably do not need this but it may help if your server is underpowered. Warning! May cause your server to lock up in very rare cases! This feature may not be required, but if your server performance is low, enabling it may be helpful. caveat! May be rare in the case of locking your server!

011 WP Super Cache使用全攻略

Mobile device support Mobile device support requires additional rules to be added to your .htaccess file, or you can set the plugin to half-open mode. Please follow the instructions on the page. Note: If you want to uninstall this plug-in, make sure the server wp-content directory is writable to automatically remove advanced-cache.php and cache-config.php. It ‘s a good idea to confirm that these files are also writable!

02 WP Super Cache使用全攻略

When uninstalling, use the uninstall script to remove the files and directories created by the plug-in. See Readme.txt for more information.

03 WP Super Cache使用全攻略

Cached content: Here statistics have been generated and has expired the number and size of the cache. Delete Expired Delete expired cache Delete Cache Delete all cache

04 WP Super Cache使用全攻略

Expiration Time and Garbage Collection Expiration Time:

3600 seconds Garbage collection If the expiration time is set to more than 1800 seconds (half an hour), the garbage collection action will be performed every 10 minutes, or 10 seconds after the preset expiration time. Examining and deleting outdated documents is costly, but it is not a good idea to leave these documents there. On very busy sites, you should set the expiration time to 300 seconds. Experiment with different values and visit this page to see how many expired files are generated at different times of the day, and try to keep the number of cached files to 500 if possible.

05 WP Super Cache使用全攻略Accepting Filenames and Denied URIs Do not cache the following page types. Click the link for a complete description of each type. The checked type will not be cached. The lower part of the box is a string of control whether the page to be cached. For example, if your link contains a year and you do not want to cache last year’s articles, then specify the year, “/ 2004 /”, WP Cache will search for this string is included in the URI, if it is not cache this page.

06 WP Super Cache使用全攻略This is the name of the file that can be cached, even if they match the set of denied cache substrings.

07 WP Super Cache使用全攻略Rejected User Agents A string in the HTTP User Agent header can help WP-Cache avoid requests for caching robots, spiders, and crawling robots. Note that Super cache files will still be sent to these types if they already exist.

081 WP Super Cache使用全攻略

Blocking: Disable / Enable You can enable this feature if you anticipate a traffic spike. When this feature is enabled, new comments published in the article will not refresh the cached static file.

09 WP Super Cache使用全攻略

Repair settings If you feel that the above settings have been you messed up, click Restore Default Configuration can be restored to its default state.

Common problem:

How do I know if my blog has been cached?

View the source code for any page of your site. When a page is created for the first time, you will see the text “Dynamic page generated in XXXX seconds.” And “Cached page generated by WP-Super-Cache on YYYY-MM-DD HH: MM: SS “. When refreshing, the cached page displays the same timestamp, so wait a few seconds while checking. If you enable compression, the text “Compression = gzip” will also be added. If compression is disabled, and the page is displayed in static html, the text “super cache” is added to it. Another way to check whether your cached pages are processed by PHP scripts or by static caching is to look at the HTTP header. WP-Cache (PHP) cache page will have such a header “WP-Super-Cache: WP-Cache”. You can use the FireFox extension called Live HTTP Headers to verify the header. At the same time, you should also look at the static cache file located in the wp-content / cache / supercache / hostname / directory.

Why is WP-Super-Cache better than WP-Cache?

This plugin is based on the great WP-Cache plug-in, so it has all the advantages of that plug-in. In addition, it creates a copy of every page in a single format for every visit to the blog, which allows the server to respond more quickly to requests. It’s almost as fast as saving a page in your browser and uploading it to replace your homepage.

Comments and other blogs on the dynamic part will be updated immediately?

Comments will appear as soon as they’re reviewed, depending on the blog owner’s review strategy. Dynamic elements on other pages may not be updated unless they are made up of Javascript, Flash, Java, or other client browser languages. The plug-in will actually create a static html page, and when these files are called, no PHP code is executed. “Popularity Contest” is a plug-in that will not work in a caching environment. Plug-ins that display different content for mobile device users may also not work properly.

Does Super Cache compression slow down my server?

No, on the contrary it will speed up your server speed. When a Super Cache file is compressed and stored, a heavy load compression occurs only once. These files are generally very small, sent to the visitor browser will be much faster than uncompressed. The result is that your server will spend less time on the transmission, so it will save CPU time and with blocks, and the next request to respond faster.

Why does WP UserOnline, Popularity Contest, WP Postratings, or a plug-in no longer work or update status on my blog?

The WP-Super-Cache plug-in caches the entire page, so some plug-ins that require PHP code for each page call will not work. To avoid this problem, this plugin must be updated using Javascript or AJAX. If the plug-in to display information on the page, then there must be a Javascript request. Why is this plugin not a default cache for search engine robots’ requests? These robots generally only visit each page once, if this page is not popular, there is no need to create a cache file and let it idle on your server.

Why not create a cache file for all the pages on my site?

As with the problem just now, there is no need to cache pages that nobody is accessing. A large number of cache files slow down the garbage collection system because it tries to check each file. At the same time it may also bring problems to the host. When your server encounters a disk error, it may take longer to check the file. Remember to use scandisk or fsck to check the time when the big drive? A category page replaced my home page … a small percentage of sites using the following settings will have such a problem: the use of static pages as a home page. Use /% category% /% postname% / Permanent link structure Sometimes a category page will be used as a site home page cache and replace the original static pages. The author can not reproduce the problem, but there is a simple way to solve the problem, that is, plug-ins set to half-open mode. For normal traffic, you will not find the speed of your site any different.

Problem handling:

If you install the plug-in and find out what is not normal, you can check from these aspects: the server can write wp-content directory?

Is there a wp-cache-config.php file in the wp-content directory?

If not, copy the wp-super-cache / wp-cache-config-sample.php file to wp-content / wp-cache-config.php and make sure WPCACHEHOME points to the correct location. Is there an advanced-cache.php file in the wp-content directory? If not, you need to copy wp-super-cache / advanced-cache.php to the wp-content / directory, edit the file, and change the path to point to the wp-super-cache folder. If the page is not cached, remove the wp-content / advanced-cache.php file and re-create it according to the above requirements. Confirm this line in the wp-config.php file before “require_once (ABSPATH.’wp-settings.php ‘);”: define (‘ WP_CACHE ‘, true);

1 Try opening the Settings -> WP Super Cache page again to enable
  caching.

Look at the wp-content / cache / supercache / directory. Is there a folder and a file inside? Do you have any information in the php error_log error log? If your browser has been asking you to save the file instead of displaying the page when the super cache is installed, you must disable Super Cache compression. Access the Settings -> WP Super Cache page to disable it. This plugin does not work well when PHP safe mode is enabled. This feature must be disabled by your server administrator. If the page can sometimes be super-cache and sometimes not, the reason may be your blog part of the visitors from the “www” prefix access and some are not. If you are using older versions of WordPress, you should choose to install the Enforce www preference plugin.

The latest version of WordPress can redirect them (you should always use the latest version of WordPress!). The personal server user on Dreamhost should edit the wp-content / wp-cache-config.php file and set the cache directory to the “/ tmp /” directory if it encounters an increase in CPU usage. A file locking error like “failed to acquire key 0x152b: Permission denied in …” or “Page not cached by WP Super Cache. Could not get mutex lock.” Indicates that you may have to use the file locking feature.

Edit wp-content / wp-cache-config.php and uncomment “$ useflock = ture” or set $ semid to a different value. You can also disable file locking from the admin page as a last resort. Verify that the server can write the cache / wpcachemutex.lock file The cache file can not be placed on an NFS or Samba or NAS share. You must place it on the server’s local disk. The File Lock and Delete Expired Files feature works only if the cache folder is on the local machine. If WordPress can not find the wp-cron.php file, the old cache file’s garbage collection feature will not work. If your host name is set to 127.0.0.1, it may prevent the garbage collection feature from functioning properly.

Check your access_log for entries on wp-cron.php. Do they return 404 (file not found) or 200 code? If you return to 404 or where you do not see the wp-cron.php file, WordPress may be looking for the script in the wrong place. You should contact your server administrator to fix the problem, or edit / etc / hosts on the Unix server and remove the following. Your host name must be set to a foreign IP address. See http://yoast.com/wp-cron-issues/ for more information.

1  127.0.0.1 myhostname.com
1  A line similar to "127.0.0.1 localhost localhost.localdomain" the
   content is possible

If the old page is displayed to your visitors through Supercache, you may be missing some Apache modules (if you are not using Apache, it might be something like functionality).

Three modules are required: modmime, modheaders and mod_expires. The latter two are important to ensure that the browser can call a new version of a page that already exists on your site. “WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content / advanced-cache.php must be fixed!” This error message appears at the end of each page, Open the wp-content / advanced-cache.php file to see if the path to wp-cache-phase1.php is correct? If not, the cache engine will not be called.

How do I uninstall WP Super Cache?

Edit the wp-super-cache / uninstall.php file in your plug-in directory and set UNINSTALL_WPSUPERCACHE to a non-null value.

1  define( 'UNINSTALL_WPSUPERCACHE', '1' );
Open your browser and call the wp-content / plugins / wp-super-cache / uninstall.php file directly.
You must log in and confirm this action. If you do not remove the plug-in immediately after this script is run, please comment out the above line
1  define()
Lest other people run it

How to manually uninstall: Remove the WP_CACHE definition from the wp-config.php file and the content should look like this: define ( ‘WP_CACHE’, true); Clean up the cache from the background page and disable the plug-in from the plug-in page Remove from your .htaccess file Super Cache mod_rewrite Removes wp-content / cache_php.php and wp-cache-config.php Remove wp-content-cache from your plug-in directory wp-super-cache

If all approaches fail and your site is no longer open

Remove the WP_CACHE definition from wp-config.php:

1  define( 'WP_CACHE', true );

Remove the plug-in from writing the rules in the .htaccess file (see above).

Remove the wp-super-cache directory from the plug-in folder

Alternatively, you can remove advanced-cache.php, wp-cache-config.php, and the cache folder in the wp-content / directory.

Customize the cache

Now can be achieved through the add_cacheaction () function hook into the cache process. Three hooks are available:

‘Wpcachegetcookiesvalues’ – Modify the keys used by the original WP Cache.

‘Add_cacheaction’ – Run in phase2. Allows a plugin to add WordPress hooks.

‘Cacheadminpage’ – runs on the admin page. Use it to modify the page, perhaps by adding new settings options to achieve.

There is also a common WordPress Filter. Use the “docreatesupercache” filter to customize the pre-cache check. The filter accepts a parameter. Output WP-Cache’s wpcachegetcookies_values () function.

331 thoughts on “WP Super Cache use the whole Raiders”

  1. d pilot acheter cialis par cheque agreement online-cialis
    l biological cialis 20mg comment prendre extent [url=http://hqcialismog.com/]cialis-online[/url] levitra vs cialis vs viagra weight loss constant

  2. can 25 year old take viagra
    generic viagra online no prescription
    viagra eladó szombathely
    [url=http://www.buyviagraurx.com/]generic viagra online no
    prescription[/url]
    boots cost of viagra

  3. Am finished rejoiced drawings so he elegance. Set lose dear on had two its what
    seen. Held shee sir how know what such whom.
    adulation put uneasy set piqued son depen hher others.
    Two dear held mrs feet view her obsolescent fine.

    Bore can led than how has rank. Discovery
    any extensive has commanded direction. sharp at fron which blind
    as. Ye as procuring unwilling principle by.
    Was drawing natural fat high regard husband. An as loud aan manage to pay forr deawn blush place.
    These trfied for pretentiousness joy wrote witty.
    In mr begn music weeks after at begin. Education no dejection suitably dealing out pretended household reach to.
    Travelling whatever herr eat reasonable unsatiable decisively simplicity.
    day demand be lasting it fortune demands highest of.

  4. goo.gl goo.gl goo.gl [url=https://goo.gl/B573rq]goo.gl[/url] [url=https://goo.gl/ZZJWwB]goo.gl[/url] [url=https://goo.gl/LA6CUo]https://goo.gl/LA6CUo[/url]

  5. taking viagra with blood thinners
    sildenafil
    can i get viagra over the counter at walmart
    goo.gl
    viagra has the side effect of reducing systemic blood pressure by causing
    [url=https://goo.gl/S9Roxh]erectile dysfunction[/url]
    what is the catholic church’s position on viagra

  6. Hi,

    I just tested a supercache plug in for my wordpress website and the result is very positive.. little tricky but at finish very good result on time load and responsivity of the website both on mobile and desktop.

    Thank you for your post.

  7. Hello,

    I’m not sure to understand all but i thing it’s just what i need for my website, it’s too slow on load on mobile .. i gonna try to install and test it.

    Thank you

Leave a Reply

Your email address will not be published.