Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
litespeed_wiki:cache:common:cache-tag-prefix-conflicts [2017/06/01 14:42]
Lisa Clarke Added background and further details to better explain the issue
litespeed_wiki:cache:common:cache-tag-prefix-conflicts [2017/06/01 14:46] (current)
Lisa Clarke [Managing Cache Tag Prefix Conflicts]
Line 1: Line 1:
-====== Managing Cache Tag Prefix ​Conflicts ======+====== Managing Cache Tag Conflicts ======
 Cache Tag Prefix conflicts can pop up when you have multiple instances of the same web application with [[litespeed_wiki:​cache#​litespeed_cache_plugins_by_application|LSCache plugins]] enabled and using the same cache root (as in a WordPress site at ''/​public_html/''​ and another one at ''/​public_html/​wp2/''​).  ​ Cache Tag Prefix conflicts can pop up when you have multiple instances of the same web application with [[litespeed_wiki:​cache#​litespeed_cache_plugins_by_application|LSCache plugins]] enabled and using the same cache root (as in a WordPress site at ''/​public_html/''​ and another one at ''/​public_html/​wp2/''​).  ​
 **Note**: This is not relevant for a single multi-site WordPress install. **Note**: This is not relevant for a single multi-site WordPress install.
 ===== The Problem ===== ===== The Problem =====
-Of particular concern is the cache tag, which is the same across all instances of a particular app. In single-site install of Wordpress, for example, it's always ''​b1_''​. The cache tag is used to group together pages from the app. As such, it is in control of which pages are purged from cache.+The cache tag is the same across all instances of a particular app. In each single-site install of Wordpress, for example, it's always ''​b1_''​. The cache tag is used to group together pages from the app. As such, it is in control of which pages are purged from cache.
  
-**Example**:​ One WordPress installation at ''<​nowiki>​www.example.com/</​nowiki>'' ​and and another WordPress installation at ''<​nowiki>​www.example.com/​store/</​nowiki>''​.+**Example**:​ One WordPress installation at ''<​nowiki>​www.example.com/</​nowiki>''​ and another WordPress installation at ''<​nowiki>​www.example.com/​store/</​nowiki>''​.
  
-In a situation where you might want to purge your entire Example Blog from cache, and you press that button, LSCache interprets the command as “purge everything with the cache tag  ''​b1_''​” and out goes your entire Example Blog cache //and your Example Store cache as well//, because it also has the ''​b1_''​ tag.+In a situation where you might want to purge your entire Example Blog from cache, LSCache interprets the command as “purge everything with the cache tag  ''​b1_''​” and out goes your entire Example Blog cache //and your Example Store cache as well//, because it also has the ''​b1_''​ tag.
  
 ===== The Solution ===== ===== The Solution =====
-To differentiate one instance of the app from another, you can give each installation its own unique **Cache Tag Prefix**.+To differentiate ​pages of one instance of the app from the pages of another ​within the cache, you can give each installation its own unique **Cache Tag Prefix**.
 ==== In WordPress ==== ==== In WordPress ====
 In the WP-Admin panel, navigate to **LiteSpeed Cache ->  Settings -> Advanced**, as depicted below: In the WP-Admin panel, navigate to **LiteSpeed Cache ->  Settings -> Advanced**, as depicted below:
  • Admin
  • Last modified: 2017/06/01 14:42
  • by Lisa Clarke