Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
litespeed_wiki:cache:lscwp:configuration:purge_all_button [2017/02/20 16:12] Johathan Kagan [Purge Front Page] |
litespeed_wiki:cache:lscwp:configuration:purge_all_button [2019/04/12 18:45] Lisa Clarke [LiteSpeed Cache for WordPress Management: Purge] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== A Note On The Purge Buttons ====== | + | ====== LiteSpeed Cache for WordPress Management: Purge ====== |
| - | In the LiteSpeed Cache Management page, one might be wondering what gets purged when they press the various purge buttons. This page will provide a brief detailing of all the various buttons. | + | Once you have LiteSpeed Cache for WordPress configured and customized to your liking, you can turn your attention to managing the cache itself. Ideally, there should be very little actual cache management required. If you set your configuration correctly, the cache should function like a well-oiled machine. |
| - | ===== Purge Front Page ===== | + | Still, there are times when you might want to take matters into your own hands for whatever reason. This section will help you to successfully manage your cache manually. |
| - | This button will purge the front page. It may be useful if one thinks the page is out of date and needs immediate updating. | + | {{:litespeed_wiki:cache:lscwp:lscwp-management-purge.png?nolink|}} |
| - | == In Multisite Installations == | + | ===== Purge Front Page ===== |
| + | Press this button to purge only the front page of your site. | ||
| - | If this button is pressed in the network admin, the main site's front page will be purged. | + | Multi-site: pressing this button in the network admin will result in only the main site’s front page being purged. |
| - | ===== Purge All ===== | + | ===== Purge Pages ===== |
| - | This button will purge all cache entries //related to the WordPress installation//. This means that if a page is cached on the site using another Web Application, it will not purge those cache entries. | + | This button will purge all cache entries that belong to pages. Don’t let the use of the word “page” confuse you here. For this button (and this button only) “page” refers to the WordPress Page post type. Everywhere else, “page” is used in the context of individual entries in a “full-page cache.” |
| - | + | ||
| - | == In Multisite Installations == | + | |
| - | + | ||
| - | Purging all in the network admin will trigger the purge all functionality on all multisite blogs. | + | |
| ===== Purge Error Pages ===== | ===== Purge Error Pages ===== | ||
| + | These buttons allow you to purge 403, 404, and 500 error pages. | ||
| - | This button will purge error pages. It allows the selection of the types of error pages to purge. The error pages, 403 and 500, will be purged by default if not de-selected, but one can also select to purge 404 error pages as well. | + | Multi-site: If one of these buttons is pressed in the network admin, the main site's error pages will be purged. |
| - | == In Multisite Installations == | + | ===== Purge All - LSCache ===== |
| + | This button will purge all cache entries related to the current WordPress installation. This means that if a page is cached on the site using a different web application (for instance, a separate WordPress blog or a XenForo forum), it will //not// purge those cache entries. | ||
| - | If this button is pressed in the network admin, the main site's error pages will be purged. | + | If you have the crawler running, the Purge All button will also purge any crawled pages and reset the sitemap. |
| - | ===== Empty Entire Cache ===== | + | Multi-site: pressing this button in the network admin will trigger the "Purge All - LSCache" functionality on all of the network’s sites. |
| - | This button will purge all the cache entries stored where this site is stored, including other web applications. This should only be used when something goes wrong. | + | ===== Purge All - CSS/JS ===== |
| - | == In Multisite Installations == | + | This button will purge all of the minified and combined JavaScript and CSS files that were cached as a result of the settings in the **[[litespeed_wiki:cache:lscwp:configuration:minification|Optimize]]** tab. |
| - | In multisite installs, this option is not available in the single site admins. | + | |
| - | ===== Purge List ===== | + | ===== Purge All - Opcode Cache ===== |
| + | This button clears the opcode cache, not to be confused with LSCache, which is a separate thing. Opcode cache stores compiled PHP code, not complete pages. | ||
| - | This button will purge a list of pages. The available list types are: Category, Tag, Post ID, and URL. The list of the selected type should be input one per line in the text area above the button. | + | ===== Purge All ===== |
| - | + | This button combines all other "Purge All" buttons. It purges everything, with a few exceptions: it does //not// purge Critical CSS or Placeholders. | |
| - | ===== How purging the cache works ===== | + | ===== Empty Entire Cache ===== |
| - | + | This is one of those buttons that should only be used when you have a problem that can’t be solved any other way. Press it to purge all of the cache entries for the entire site, including those entries from other web applications. | |
| - | == The Short Description == | + | |
| - | The purge all button purges the cache stored at the storage path set for that virtual host. If the WordPress installation is a multi-site installation, everything will be purged for all sites. | + | |
| - | + | ||
| - | == The Detailed Explanation == | + | |
| - | The LiteSpeed Cache Plugins for WordPress works by notifying the server when a page is cacheable. This means that the Purge All button needs to notify the server to purge its cache. | + | |
| - | In LSWS, the server/vhost configurations lets the admin decide where the cache data should be stored. A storage path at the server level is required for the cache to work. By default, if the virtual host does not set a storage path, it will use the server’s storage path and create a subdirectory for each virtual host listed using its domain name. | + | Multi-site: this option is only made available in the network admin. Individual site admins do not have the ability to clear the entire cache. |
| - | Based on this configuration, the purge all button will purge all content under the cache storage path associated with the virtual host. | + | ===== Purge By... ===== |
| + | This area allows you to purge a list of pages. The available list types are: Category, Post ID, Tag,and URL. The list of the selected type should be input one-per-line in the text area above the **Purge List** button. | ||