Differences

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

--- litespeed_wiki:cache:litemage2:troubleshooting [2018/08/17 13:50]
Jackson Zhang
+++ litespeed_wiki:cache:litemage2:troubleshooting [2019/11/12 21:14]
Jackson Zhang
@@ Line 41: / Line 41: @@
 {{ :litespeed_wiki:cache:litemage2:litemage-pagecache-enable.png?800 |}}
+==== EnableDebug "Yes and set X-LiteMage-Debug response headers" ====
+LiteMage 2.1.0 and above includes the **X-LiteMage-Debug response headers** feature, designed to make troubleshooting easier.
+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 |}}
+Once enabled, you can browse your site, and use the browser's developer tool to check the header:
+{{ :litespeed_wiki:cache:litemage2:litemage2-enable-debug-response-headers-2.png?800 |}}
+In this case, the **Headers** show:
+  x-litemage-debug-cc:
+  x-litemage-debug-info: Layout has uncacheable blocks mgs_gdpr_login_header, wishlist-link-header, wishlist_header, wishlist_header,
+  captcha-header
+  x-litemage-debug-tag:
+  x-litemage-debug-vary:
+The info ''Layout has uncacheable blocks mgs_gdpr_login_header, wishlist-link-header, wishlist_header, wishlist_header,
+  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 blocks, or modfiy the template to make them ''cacheable''.
 ==== 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.