Differences

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

Link to this comparison view

Next revision
Previous revision
Last revision Both sides next revision
litespeed_wiki:cache:lscjoomla:configuration:advanced [2018/06/01 15:22]
Lisa Clarke created
litespeed_wiki:cache:lscjoomla:configuration:advanced [2020/02/03 16:52]
Lisa Clarke Copyediting last two sections
Line 1: Line 1:
 ====== LiteSpeed Cache for Joomla Advanced Settings ====== ====== LiteSpeed Cache for Joomla Advanced Settings ======
 You can set up ESI here (a must if you are trying to cache an ecommerce site), give yourself the ability to clear the cache from a secure link outside of Admin, set a different TTL for the homepage, and set up LSCache to save separate views for mobile and desktop. You can set up ESI here (a must if you are trying to cache an ecommerce site), give yourself the ability to clear the cache from a secure link outside of Admin, set a different TTL for the homepage, and set up LSCache to save separate views for mobile and desktop.
- +{{ :​litespeed_wiki:​cache:​lscjoomla:​configuration:​lscjoomla-settings-advanced2.png?800 |}}
-{{:​litespeed_wiki:​cache:​lscjoomla:​lscjoomla-settings-advanced.png?direct&800|}}+
  
 ===== ESI Feature Enabled ===== ===== ESI Feature Enabled =====
  
-LiteSpeed'​s implementation of ESI (Edge Side Includes) brings caching to the next level by allowing you to mix public and private content on a single page, and still serve that page from cache. ESI is an important aspect of any ecommerce ​caching strategy.+LiteSpeed'​s implementation of ESI (Edge Side Includes) brings caching to the next level by allowing you to mix public and private content on a single page, and still serve that page from cache. ESI is an important aspect of any eCommerce ​caching strategy.
  
-ESI is enabled by defaultbut you can turn it off, if you don't need it.+ESI must be enabled both in the plugin and at the server level. ​ESI is enabled by default ​in the plugin (but you can turn it off, if you don't need it). The ESI feature is //​disabled//​ by default at the server level. You will need to [[litespeed_wiki:​cache:​common_installation:​shared-enable-individually|enable ESI in LiteSpeed Enterprise]] before using ESI-related features in the plugin. 
 + 
 +**Please Note**: OpenLiteSpeed does not support ESI, so you cannot use this feature with OpenLiteSpeed 
  
 Want to learn more about ESI? [[https://​blog.litespeedtech.com/​2017/​09/​06/​wpw-esi-and-litespeed-cache/​|This blog post]] explains it from a WordPress point of view, but the concepts are the same for Joomla. Anywhere you see the word "​widget,"​ just think "​module."​ Want to learn more about ESI? [[https://​blog.litespeedtech.com/​2017/​09/​06/​wpw-esi-and-litespeed-cache/​|This blog post]] explains it from a WordPress point of view, but the concepts are the same for Joomla. Anywhere you see the word "​widget,"​ just think "​module."​
Line 38: Line 39:
  
 If the cache was successfully cleared, you will see the confirmation message, ''​All LiteSpeed Cache Purged!''​. If the cache was successfully cleared, you will see the confirmation message, ''​All LiteSpeed Cache Purged!''​.
 +
 +===== Web interface to purge all LiteSpeed Cache =====
 +
 +To manually purge all LiteSpeed Cache from the web interface, click the **Web interface to purge all LiteSpeed Cache** URL. You can bookmark this URL to avoid logging into the Joomla backend in the future.
 +
 +===== Web Web interface to rebuild all LiteSpeed Cache =====
 +
 +To manually start the crawler to rebuild all LiteSpeed Cache, click the **Web interface to rebuild all LiteSpeed Cache** URL. You can also [[litespeed_wiki:​cache:​lscjoomla:​crawler|set up a cron job]] to do this periodically. ​
  • Admin
  • Last modified: 2020/07/14 17:07
  • by Lisa Clarke