Differences

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

Link to this comparison view

Both sides previous revision Previous revision
litespeed_wiki:cache:litemage:troubleshooting:turning-on-maintenance-mode [2016/05/09 21:02]
Long Hu
litespeed_wiki:cache:litemage:troubleshooting:turning-on-maintenance-mode [2017/05/08 14:07] (current)
Lisa Clarke
Line 1: Line 1:
-====== Site Abnormal After Store Maintenance with LiteMage Enabled ======+~~NOTOC~~ 
 +======Site Abnormal After Store Maintenance with LiteMage Enabled======
  
-**Problem**: Some Magento site ESI blocks ​showing ​abnormal content after Magento store maintenance+====Problem==== 
 +Some Magento site ESI blocks ​show abnormal content after Magento store maintenance.
  
-**Cause**: User forgot to disable LiteMage during store maintenance. During maintenance,​ Magento site couldn'​t be accessed (return ​503 error) while LiteMage ​is still working ​if not disabled. If any site page caches ​are refreshed during this period, the wrong content from backend ​will be cached and be served ​later, which caused the problem.+====Cause==== 
 +The user forgot to disable LiteMage during store maintenance. During maintenance, ​the Magento site couldn'​t be accessed (503 error was returned) while LiteMage ​was still working. If any site page caches ​were refreshed during this period, the wrong content from backend ​would have been cached and would later be served ​erroneously.
  
-**Solution**: Flush All LiteMage ​Caches ​and rebuild the cache. Go to Magento Admin Panel and navigate to System > Cache Managementclick "Flush All LiteMage Cache".+====Solution==== 
 +Flush all LiteMage ​caches ​and rebuild the cache. Go to Magento Admin Panelnavigate to **System > Cache Management** and click **Flush All LiteMage Cache**.
  
-**Notes**: Please disable LiteMage during store maitenance period. Or use the following alternatives if your maintenance won't affect the site content:+====Notes==== 
 +Please disable LiteMage during ​the store maitenance period, or use the following alternatives if your maintenance won't affect the site content:
  
-During maintenance,​ add the following rewrite rule to the beginning of your .htaccess” file to have all requests for /index.php redirected to /​errors/​503.php:​+During maintenance,​ add the following rewrite rule to the beginning of your .htaccess file to have all requests for /index.php redirected to /​errors/​503.php:​
  
   RewriteCond %{REQUEST_URI} !^/​(media|skin|js)/​   RewriteCond %{REQUEST_URI} !^/​(media|skin|js)/​
Line 17: Line 22:
   RewriteRule .* errors/​503.php [L, E=Cache-Control:​no-cache]   RewriteRule .* errors/​503.php [L, E=Cache-Control:​no-cache]
  
-Once maintenance has been completed, either remove or comment out this rewrite rule to restore your site back to it’s normal state. In this way you can avoid the purge of LiteMage cache and the cost to rebuild ​cache. +Once maintenance has been completed, either remove or comment out this rewrite rule to restore your site back to it’s normal state. In this way you can avoid the purge of the LiteMage cache and the cost to rebuild ​it.
- +
- +
- +
  • Admin
  • Last modified: 2017/05/08 14:07
  • by Lisa Clarke