Differences

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

--- litespeed_wiki:cache:litemage:troubleshooting:general [2016/05/06 18:39]
Long Hu [3rd Party Store/Currency Auto Switcher Not Redirecting To Correct Page]
+++ litespeed_wiki:cache:litemage:troubleshooting:general [2016/05/06 21:56] (current)
Long Hu [Pop-ups Will Sometimes Not Appear]
@@ Line 45: / Line 45: @@
 </code>
-Alternatively you can remove footer block injection. This however will slow down page loading time as well as increase cache size and is hence not recommended.
+Alternatively you can remove footer block injection from LiteMage config.xml. This however will slow down page loading time as well as increase cache size and is hence not recommended.
 ==== JavaScript global variable problem ====
@@ Line 154: / Line 154: @@
 **1. You need to purge LiteMage Cache after maintenance**\\
-During maintenance, go to the Magento Admin Panel and navigate to System > Configuration > LITEMAGE CACHE > LiteMage Configuration, and set “Enable LiteMage Cache” to “No”. This will disable and automatically purge LiteMage Cache. Then, after removing the maintenance.flag file, re-enable LiteMage by changing “Enable LiteMage Cache” back to “Yes”.
+After maintenance, go to the Magento Admin Panel and navigate to System > Cache Management > Flush All LiteMage Cache
 **2. You do not need to purge LiteMage Cache after maintenance**\\
@@ Line 172: / Line 172: @@
 When using LiteMage in conjunction with a JS/CSS Compressor (such as the [[http://potatocommerce.com/compressor.html|PotatoCommerce Compressor]]), you may notice that some pop-ups, such as the list of items contained in a customer’s shopping cart, may not appear when being moused over for example.
-The reason this is happening is because JS/CSS Compressors create and store a separate compressed file. As the cart (in this example) is a private block, LiteMage punches a hole there. Now when the page is loaded, the cart is served from LiteMage, which the compressor does not know about, meaning the javascript will not be processed by the compressor correctly. Because of this, when you mouse over the cart, javascript will not be properly triggered and nothing will be displayed.
+The reason this is happening is because JS/CSS Compressors create and store a separate compressed file. As the cart (in this example) is a private block, LiteMage punches a hole there. Now when the page is loaded, the cart content is served from LiteMage ESI response, which the compressor does not know about, meaning the javascript will not be processed by the compressor correctly. Because of this, when you mouse over the cart, javascript will not be properly triggered and nothing will be displayed.
 But What about the times that the pop-up does appear? It is possible that javascript somewhere else on your web page is being triggered and properly resetting the pop-up.
@@ Line 243: / Line 243: @@
 </code>
-Since LiteMage con only punch a hole on a block defined through a layout file, the dynamically generated content here will not be recognized. You can however create a new block containing this logic and define that block in the layout file with a unique name. Once you have done this you can then add this new block name to the **Customized Block Names for "toplinks" Tag** list.
+Since LiteMage can only punch a hole on a block defined through a layout file, the dynamically generated content here will not be recognized. You can however create a new block containing this logic and define that block in the layout file with a unique name. Once you have done this you can then add this new block name to the **Customized Block Names for "toplinks" Tag** list.
 ==== Need Additional Support? ====
 If you need any additional support or help installing, configuring, or troubleshooting LiteMage for your Magento store, have a look at our [[litespeed_wiki:cache:litemage:troubleshooting:support|LiteMage Support]] page.