Differences

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

--- litespeed_wiki:cache:litemage:troubleshooting:general [2016/02/19 21:54]
Michael Alegre [Logged In Usernames/Cart Items Being Shown On Other User's Pages]
+++ litespeed_wiki:cache:litemage:troubleshooting:general [2016/05/06 21:56] (current)
Long Hu [Pop-ups Will Sometimes Not Appear]
@@ Line 38: / Line 38: @@
 </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.
+Similarly, for SM themes (such as sm-maxshop yttheme):
+<code>
+if (empty($var_yttheme)) {
+        include (dirname(dirname(__FILE__)).'/sm/yt_prepar.php');
+}
+</code>
+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 66: / Line 73: @@
 ==== Magento Connect “Exception during cache and session cleaning” Error ====
-When using the Magento Connect manager with certain browsers you may receive an "Exception during cache and session cleaning" error message in the Magento Connect output frame when attempting to either install or reinstall LiteMage. If this occurs, your Magento site will become stuck in maintenance mode and therefore be inaccessible.
+When using the Magento Connect manager with certain browsers you may receive an "Exception during cache and session cleaning" error message in the Magento Connect output frame when attempting to either install or reinstall LiteMage. If this occurs, LiteMage will still be installed but your Magento site will become stuck in maintenance mode and therefore be inaccessible.
 The reason for this is that when Magento Connect attempts to install any new modules to your store, it first creates a "maintenance.flag" file in the root directory. The presence of this file signals that your site is now in maintenance mode and changes can be safely made. Under normal circumstances this file should be automatically deleted once the installation has completed, but certain errors (such as this one) can cause Magento Connect to halt before reaching the removal step.
@@ Line 133: / Line 140: @@
 You may find that after enabling LiteMage Cache, your sites header, footer, and other dynamically loaded blocks (or the LiteMage specific options under System > Cache Management in the Magento Admin Panel) disappear.
-This is caused by mistakenly attempting to disable LiteMage by disabling "Litespeed_Litemage" under System > Configuration > ADVANCED > Advanced instead of setting "Enable LiteMage Cache" to "No" under System > Configuration > LITEMAGE CACHE > LiteMage Configuration. By doing the former, you are disabling the LiteMage Modules output but not LiteMage itself. LiteMage is still enabled and punching holes on your page, but with it's output disabled, it is unable to output the ESI response to your sites frontend, resulting in those blocks appearing "missing".
+This is caused by mistakenly attempting to disable LiteMage by disabling "Litespeed_Litemage" under System > Configuration > ADVANCED > Advanced > Disable Modules Output, instead of setting "Enable LiteMage Cache" to "No" under System > Configuration > LITEMAGE CACHE > LiteMage Configuration. By doing the former, you are disabling the LiteMage Modules output but not LiteMage itself. LiteMage is still enabled and punching holes on your page, but with it's output disabled, it is unable to output the ESI response to your sites frontend, resulting in those blocks appearing "missing".
-To fix this simply navigate to System > Configuration > ADVANCED > Advanced, set "Litespeed_Litemage" to "Enable", and click "Save Config" at the top right of the page.
+To fix this simply navigate to System > Configuration > ADVANCED > Advanced > Disable Modules Output, set "Litespeed_Litemage" to "Enable", and click "Save Config" at the top right of the page.
 ==== Turning On Maintenance Mode While LiteMage Is Enabled ====
-If your Magento sites root directory, where index.php is located, contains a file named “maintenance.flag”, your Magento site is currently in [[https://www.siteground.com/tutorials/magento/maintenance-mode.htm|maintenance mode]] and should display a 503 error page.
+If your Magento sites root directory, where index.php is located, contains a file named “maintenance.flag”, your Magento site is currently in [[https://www.siteground.com/tutorials/magento/maintenance-mode.htm|maintenance mode]] and would display a 503 error page. In the browser you will get a message saying "Service Temporarily Unavailable" with the detailed explanation "The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later."
 However, if a page is currently cached, LSWS will serve the cached copy instead, as it won't reach the backend to know that the site is in maintenance mode. This is often undesirable as the cached versions of these pages may become invalidated during maintenance and anything involving the backend will not work.
@@ Line 147: / 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 165: / 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 214: / Line 221: @@
 Lastly, in order for LiteMage's crawler to properly crawl your multiple currencies/stores, you must also **add "/litemage_walker/" to your auto switcher's disabled user agents list**.
-**For example:** In Extendware's Store / Currency Switcher, you can disable auto-switching for any user agents matching an inputted regular expression. Simply navigate to Disabled User Agents >> User Agent RegExp and add "/litemage_walker/".
+**For example:** In Extendware's Store / Currency Switcher, you can disable auto-switching for any user agents matching an input regular expression. Simply navigate to Disabled User Agents >> User Agent RegExp and add "/litemage_walker/".
@@ Line 236: / 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.