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 Both sides next revision
litespeed_wiki:cache:litemage2:troubleshooting [2019/11/12 16:50]
Jackson Zhang [Page Cache should be enabled under Cache Management]
litespeed_wiki:cache:litemage2:troubleshooting [2019/11/12 19:45]
Lisa Clarke [Enable debug "Yes and set X-LiteMage-Debug response headers"] Copyedited
Line 42: Line 42:
 {{ :​litespeed_wiki:​cache:​litemage2:​litemage-pagecache-enable.png?​800 |}} {{ :​litespeed_wiki:​cache:​litemage2:​litemage-pagecache-enable.png?​800 |}}
  
-==== Enable debug "Yes and set X-LiteMage-Debug response headers"​ ==== +==== EnableDebug ​"Yes and set X-LiteMage-Debug response headers"​ ==== 
-Staring from LiteMage 2.1.0, LiteMage introduces ​the "X-LiteMage-Debug response headers" ​feature ​and it will make your troubleshooting easier.  When you tried everything in the wiki but you still could not see ""​X-LiteSpeed-Cache:​ hit,​litemage"​ header, you might consider to enable this debug feature to find out more information.+LiteMage 2.1.0 and above includes ​the **X-LiteMage-Debug response headers** feature, designed to make troubleshooting easier. ​
  
-To enable this, you will need to go to Magento Admin -> Stores ​-> Advanced ​-> LiteMage Cache -> Developer Settings ​-> Enable Debug -> ''​Yes and set X-LiteMage-Debug response headers''​. You can also add your IP to "Log Debug Messages Only for Listed IPs" ​field to show such debug header to your IP only.  ​+When you try everything in the wiki but you still are not seeing an ''​X-LiteSpeed-Cache:​ hit,​litemage''​ header, ​enable this debug feature ​to collect more information. 
 + 
 +Navigate ​to **Magento Admin > Stores > Advanced > LiteMage Cache > Developer Settings**, and set **Enable Debug** to ''​Yes and set X-LiteMage-Debug response headers''​. You can also add your IP to to the **Log Debug Messages Only for Listed IPs** field to show the debug header to your IP only.  ​
 {{ :​litespeed_wiki:​cache:​litemage2:​litemage2-enable-debug-response-headers1.png?​800 |}} {{ :​litespeed_wiki:​cache:​litemage2:​litemage2-enable-debug-response-headers1.png?​800 |}}
  
-Then when you browse your site and use the browser developer tool to check the header:+Once enabled, ​you can browse your siteand use the browser'​s ​developer tool to check the header:
  
 {{ :​litespeed_wiki:​cache:​litemage2:​litemage2-enable-debug-response-headers2.png?​800 |}} {{ :​litespeed_wiki:​cache:​litemage2:​litemage2-enable-debug-response-headers2.png?​800 |}}
  
-Headers show:+In this case, the **Headers** show:
   x-litemage-debug-cc: ​   x-litemage-debug-cc: ​
   x-litemage-debug-info:​ Layout has uncacheable blocks mgs_gdpr_login_header,​ wishlist-link-header,​ wishlist_header,​ wishlist_header, ​   x-litemage-debug-info:​ Layout has uncacheable blocks mgs_gdpr_login_header,​ wishlist-link-header,​ wishlist_header,​ wishlist_header, ​
Line 59: Line 61:
   x-litemage-debug-vary:​   x-litemage-debug-vary:​
   ​   ​
-which tells you ''​Layout has uncacheable blocks mgs_gdpr_login_header,​ wishlist-link-header,​ wishlist_header,​ wishlist_header,​  +The info ''​Layout has uncacheable blocks mgs_gdpr_login_header,​ wishlist-link-header,​ wishlist_header,​ wishlist_header,​  
-  captcha-header'' ​and these blocks ​cause the page uncacheable. ​You may need to consider ​to disable ​such blocks or modify ​the template to make them ''​cacheable''​.+  captcha-header'' ​tells you that there are five blocks ​which are causing ​the page to be uncacheable. ​If you want to cache the page, you will either ​need to disable ​to blocksor modfiy ​the template to make them ''​cacheable''​.
 ==== Page is not cachable because of "​cacheable"​ is set to "​false"​==== ==== Page is not cachable because of "​cacheable"​ is set to "​false"​====
 If you followed every step in the installation wiki and still do not see the ''​X-LiteSpeed-Cache:​ hit,​litemage''​ header for that page/for all pages, it is likely that the page is non-cacheable due to a setting from another plugin. If you followed every step in the installation wiki and still do not see the ''​X-LiteSpeed-Cache:​ hit,​litemage''​ header for that page/for all pages, it is likely that the page is non-cacheable due to a setting from another plugin.
  • Admin
  • Last modified: 2020/07/08 19:33
  • by Lisa Clarke