Differences

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

--- litespeed_wiki:cache:litemage:installation [2017/09/14 18:28]
Jackson Zhang [Updating]
+++ litespeed_wiki:cache:litemage:installation [2018/10/01 21:15]
Jackson Zhang [Turn On/Off LiteMage in Magento Configurations]
@@ Line 57: / Line 57: @@
 ===== LiteMage Extension for Magento Installation =====
-The LiteMage extension for Magento needs to be installed for each Magento installation. Varnish cache and other full page caches must also be disabled ( including Magento built in full page cache ).
+The LiteMage extension for Magento needs to be installed for each Magento installation. Varnish cache and other full page caches must also be disabled ( including Magento built in full page cache ). Normally locate the xml file for the modules located at app/etc/modules/, For example, Extendware_EWPageCache.xml,  and change ''<active>true</active>'' to ''<active>false</active>''. Alternatively, you can rename the xml to other name such as adding ''.disable'' to it: ''mv Extendware_EWPageCache.xml Extendware_EWPageCache.xml.disable''. You will need to go to system->cache management-> Configuration (refresh the configuration) and flush the cache storage .
   Note: Updating LiteMage will overwrite LiteMage's config.xml file; be sure to backup your
@@ Line 90: / Line 91: @@
   * Once LiteMage Cache is enabled, a “Flush LiteMage Cache” button will show up under System -> Cache Management. If you click “Flush Magento Cache” or “Flush Cache Storage”, it will automatically flush LiteMage Cache as well.
   * For LiteMage to work correctly, you must have both "Configuration" and "Layouts" enabled under System -> Cache Management. If you are using Magento Enterprise, you must also disable "Page Cache".
+  * LiteSpeed doesn't need anything from "Blocks HTML output" and it can be either enabled or disabled according to your need.
 {{ :litespeed_wiki:cache:magento-cache-management-li-80-e.png?nolink |}}
@@ Line 119: / Line 121: @@
 Use your browser's developer tool to check the response header for the HTML file. This can usually be done by right clicking on the page and selecting some form of “Inspect”. Then click on the “Network” tab in the inspector and reload the page. If you see **“X-LiteSpeed-Cache: hit,litemage”** in the response header for the HTML file(usually listed first), then the page is being served by LiteMage Cache. You should see **"X-Litespeed-Cache:miss"** for the first time visit page, then if you refresh the page, you should see **“X-LiteSpeed-Cache: hit,litemage”**. If this is not the case, please verify if there is any step missed from above, or try [[litespeed_wiki:cache:litemage:troubleshooting|this wiki]] for troubleshooting steps.
+If you see something like ''x-litespeed-cache-control:public,max-age=86400'' and ''x-litespeed-tag'' after refresing a few times but still no '' x-litespeed-cache:miss,litemage'' or ''x-litespeed-cache:hit,litemage'', the common reason is a cache root permission problem. virtual host cache root is normally set to ''/home/$USER/lscache'' and it should be owned by ''nobody:user'' instead of ''user:user''.  If somehow you manually created this directory with ''user:user'' ownership, or you manually changed it to ''user:user'' ownership, there will be a cache module write permission issue as described above. You may also encounter the issue with some old cache files. To fix the problem, remove the ''/home/$USER/lscache'' folder completely and restart the web server. The cache root folder (normally ''/home/$USER/lscache'') will be created with correct ownership and permissions automatically during the restart. After restart, you should see the ''x-litespeed-cache:hit,litemage'' header.
 You can setup [[litespeed_wiki: cache:litemage:troubleshooting:warmup|cache warmup]] to warmup your litmage to ensure visitors' browsing served from cache instead of backend php and avoid "X-Litespeed-Cache:miss".