Some Magento site ESI blocks show abnormal content after Magento store maintenance.
The user forgot to disable LiteMage during store maintenance. During maintenance, the Magento site couldn't be accessed (a 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.
Flush all LiteMage caches and rebuild the cache. Go to Magento Admin Panel, navigate to System > Cache Management and click Flush All LiteMage Cache.
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:
RewriteCond %{REQUEST_URI} !^/(media|skin|js)/
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_FILENAME} !-l
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 the LiteMage cache and the cost to rebuild it.