Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
litespeed_wiki:cache:lscwp:configuration:general [2018/03/29 20:07]
Lisa Clarke Adjusted title
litespeed_wiki:cache:lscwp:configuration:general [2018/11/27 20:06] (current)
Lisa Clarke Added Automatically Upgrade option
Line 13: Line 13:
 ===== Default Public Cache TTL ===== ===== Default Public Cache TTL =====
  
-//​604800// ​between 30 or more.+//​604800// ​
  
 This TTL setting controls most of the pages. All the other TTLs are for specific pages/types of pages. This TTL setting controls most of the pages. All the other TTLs are for specific pages/types of pages.
Line 21: Line 21:
 ===== Default Private Cache TTL ===== ===== Default Private Cache TTL =====
  
-//​1800// ​between 60 and 3600.+//​1800// ​
  
-This TTL setting determines how long private pages are cached.+This TTL setting determines how long private pages are cached. Possible values are between 60 and 3600.
  
 ===== Default Front Page TTL ===== ===== Default Front Page TTL =====
-//​1800// ​30 or more.+//1800//
  
 This TTL setting controls the front page. Note that this can be triggered by the is_front_page() check or a third party plugin chose to use the front page TTL for the page (for example, the WooCommerce shop page). This TTL setting controls the front page. Note that this can be triggered by the is_front_page() check or a third party plugin chose to use the front page TTL for the page (for example, the WooCommerce shop page).
Line 33: Line 33:
  
 ===== Default Feed TTL ===== ===== Default Feed TTL =====
-//0// 0 or more. 0 indicates do not cache, < 30 seconds will be set to 30.+//0//
  
-This TTL setting controls the feeds. Feeds are a great way for readers to stay up to date on blog entries. They are generally set up to pull from the blog in intervals, which, without caching, could cause a constant load on the server. Cached feed pages are purged on update and on comment, so they are guaranteed to remain up to date.+This TTL setting controls the feeds. Feeds are a great way for readers to stay up to date on blog entries. They are generally set up to pull from the blog in intervals, which, without caching, could cause a constant load on the server. Cached feed pages are purged on update and on comment, so they are guaranteed to remain up to date. Possible values are 0 or more. 0 indicates do not cache, < 30 seconds will be set to 30.
  
 ===== Default 404 TTL ===== ===== Default 404 TTL =====
  
-//​3600// ​0 or more. 0 indicates do not cache, < 30 seconds will be set to 30.+//3600//
  
 This TTL controls the pages that return 404. This may be random URLs visited or intentional 404s, but all pages returning a 404 status will use this value. This TTL controls the pages that return 404. This may be random URLs visited or intentional 404s, but all pages returning a 404 status will use this value.
  
-The default value is 3600, for one hour. There is no real recommended value for this TTL because it depends on what happens to the site. If visiting 404 pages is a common occurrence, it may help to cache the page for at least a short period. If 404 pages are intentional,​ it may help to cache the page for a longer period of time, because it is an expected visit. One matter of concern is disk size. Since 404 is for not found, there are an unlimited amount of pages that could be cached. This could be detrimental for the disk usage.+The default value is 3600, for one hour. There is no real recommended value for this TTL because it depends on what happens to the site. If visiting 404 pages is a common occurrence, it may help to cache the page for at least a short period. If 404 pages are intentional,​ it may help to cache the page for a longer period of time, because it is an expected visit. One matter of concern is disk size. Since 404 is for not found, there are an unlimited amount of pages that could be cached. This could be detrimental for the disk usage. Possible values are 0 or more. 0 indicates do not cache, < 30 seconds will be set to 30.
  
 ===== Default 403 TTL ===== ===== Default 403 TTL =====
  
-//​3600// ​0 or more. 0 indicates do not cache, < 30 seconds will be set to 30.+//3600//
  
 This TTL controls the pages that return 403. This TTL controls the pages that return 403.
  
-The default value is 3600, for one hour. Pages returning 403 are usually intentional,​ so it may be worth while to have a longer TTL for this setting.+The default value is 3600, for one hour. Pages returning 403 are usually intentional,​ so it may be worth while to have a longer TTL for this setting. Possible values are 0 or more. 0 indicates do not cache, < 30 seconds will be set to 30.
  
 ===== Default 500 TTL ===== ===== Default 500 TTL =====
  
-//​3600// ​0 or more. 0 indicates do not cache, < 30 seconds will be set to 30.+//3600//
  
 500 Errors are a more severe error. Caching this page may mask an issue within WordPress, so that may not be desired. 500 Errors are a more severe error. Caching this page may mask an issue within WordPress, so that may not be desired.
  
-The default value is 3600, for one hour. +The default value is 3600, for one hour.  Possible values are 0 or more. 0 indicates do not cache, < 30 seconds will be set to 30.
  
 +===== Automatically Upgrade =====
 +//OFF//
 +
 +You can have this plugin upgrade automatically any time a new version is available. This saves you the effort of having to manually execute an update. If this option is enabled, your site will get LSCWP updates within a few hours of the new versions going live in the WordPress Plugin Directory. This delay is intentional,​ as it gives us time to make sure that there are no serious problems with the update.
 +
 +Automatic Upgrade only works if you have WP-Cron enabled. (WP-Cron is enabled in WordPress by default, so if you don't know whether it's enabled on your site, it probably is.)
 
litespeed_wiki/cache/lscwp/configuration/general.txt · Last modified: 2018/11/27 20:06 by Lisa Clarke