====== A LiteMage Troubleshooting Showcase ====== In this troubleshooting showcase, we will be looking at a case where a Magento site was having logged in/out issues, comparison issues, and disappearing banner issues. We will go over the troubleshooting processes and recommended solutions to fix them. It is assumed that you are already familiar with Magento Layouts, blocks, and templates as well as how to make proper changes to them. You can find out more from the [[http://devdocs.magento.com/guides/m1x/magefordev/mage-for-dev-4.html|Magento 1.x Developer Reference]]. ==== Issue 1: Logged In/Out ==== On the home page, there is a Welcome/Login/Create an Account section at the top. If a user named Sam logs in, we expect to see **Welcome, Sam! Logout**. With LiteMage installed, we were instead seeing **Welcome Sam! Login or Create an Account**. In this case, LiteMage cached the **Login or Create an Account** text for a logged //out// user and served that to logged //in// Sam. This issue was also happening in reverse. LiteMage would cache **Welcome, Sam! Logout** for logged in Sam, and then serve **Welcome, ! Logout** to different logged //out// users. Looking further, we saw that these cases were all occurring on sites that used the SM Market theme. It looked like a template problem. LiteMage [[litespeed_wiki:cache:litemage:troubleshooting:checking-hole-punching|punches holes]] for user-specific information like "Sam," the login button, and the welcome tag. The resulting ESI blocks are processed in small chunks. With this particular template, some global PHP variables initialized in header.phtml and social.phtml were not available in these small chunks. The two template files needed to be updated to initialize them: **[app/design/frontend/sm_market/default/template]#** ''vi page/html/header.phtml''\\ **[app/design/frontend/sm_market/default/template]#** ''vi page/html/social.phtml'' The following was added to the top of the two template files: if (empty($var_yttheme)) { include (dirname(dirname(__FILE__)).'/sm/yt_prepar.php'); } Problem solved! See [[litespeed_wiki:cache:litemage:troubleshooting:uninitialized-php-vars-injected-block|Uninitialized PHP Vars In Injected Blocks]] for more detailed information about this type of issue. ==== Issue 2: Punching A Bigger Hole While Still Purging Private Sections ==== Once the initialization problem was solved, we needed to punch a big hole instead of small one. Logging into the Magento Admin and entering LiteMage config, we added ''header'' in **Customized Block Names for "toplinks" Tag**. We also saw "compare" in a toplinks block, so we added ''compare'' to **Additional Purge Tags for "toplinks" Blocks** as well. {{ :litespeed_wiki:cache:litemage:troubleshooting:litemage-see-minicompare-tag-add-purge.png?nolink |}} For more info on this step, check out [[litespeed_wiki:cache:litemage:troubleshooting:logged-in-user-info-shown-to-others|Logged In Usernames/Cart Items Shown On Other User's Pages]]. ==== Issue 3: The Case of The Disappearing Banner ==== Upon fixing the logged in/out issue, we discovered the banner had disappeared from the homepage! The header template includes logic to check if it is displaying on a frontend page or not. If it is not a frontend page, then the banner will not display. This stopped us from simply punching a big hole for the header, like we did earlier. We needed to go back and "fix" the login links. After making a copy of header4.phtml, the header style file, we opened it to begin modifying. **[app/design/frontend/sm_market/default/template/page/html]** ''vi header4.phtml'' Inside we could see the "log in" link mixed into the header template. That logic needed to be taken out and put in its own block/template so we could both hole punch it as a private block AND keep the rest of the header publicly cached.

getChildHtml('welcome') ?> getAdditionalHtml() ?>

getLayout()->createBlock('cms/block')->setBlockId('v4-call-us')->toHtml()) { ?> getLayout()->createBlock('cms/block')->setBlockId('v4-call-us')->toHtml(); ?>
We copied the code inside ''
'' and moved it into our new welcomelogin.phtml file. **[app/design/frontend/sm_market/default/template/page/html]#** ''vi welcomelogin.phtml'' helper('customer')->isLoggedIn() ){ ?> " class="btn-head" href="getUrl('customer/account/login/') ?>"> __("Login"); ?> __("or"); ?> " class="btn-head" href="getUrl('customer/account/logout') ?>"> __("Logout"); ?> isLoggedIn()) if(!$this->helper('customer')->isLoggedIn() ){ ?> " class="btn-head" href="customer/account/create/"> __("Create an Account"); ?> We then added our new “welcomelogin” block to the header block... **[app/design/frontend/sm_market/default/layout]#** ''vi page.xml'' …. …. After welcome block ...and updated the header4.phtml file to reference the new "welcomelogin" block where the "log in" logic used to be:

getChildHtml('welcome') ?> getAdditionalHtml() ?>

getLayout()->createBlock('cms/block')->setBlockId('v4-call-us')->toHtml()) { ?> getLayout()->createBlock('cms/block')->setBlockId('v4-call-us')->toHtml(); ?>
Finally we went back to our LiteMage Configuration in the Magento Admin Panel and added ''welcomelogin'' to **Customized Block Names for "welcome" Tag**. Voila! The banner is back and LiteMage is operating at 100%. ==== Need Help? ==== Are you running into complicated LiteMage issues? Does the above showcase seem too overwhelming to tackle on your own? In cases such as these we recommend engaging with our experienced LiteMage Support Engineers/LiteMage Developers for a formal investigation and **[[litespeed_wiki:cache:litemage:support_tiers|support services]]**. This service is fully refundable if we cannot get LiteMage completely working for your site.