Differences

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

--- litespeed_wiki:cache:litemage:troubleshooting:logged-in-logout_banner_disappear [2017/05/04 16:18]
Michael Alegre Improved code formatting and moved into <code> blocks.
+++ litespeed_wiki:cache:litemage:troubleshooting:logged-in-logout_banner_disappear [2017/05/04 20:54] (current)
Michael Alegre [Issue 3: The Case of The Disappearing Banner]
@@ Line 1: / Line 1: @@
-===== A LiteMage troubleshooting case study =====
+====== A LiteMage Troubleshooting Showcase ======
-In this troubleshooting case study, we will show you multiple issues(including "Loggin/logout" issue, "compare" issue and "banner" disappears issue), troubleshooting processes and recommended solutions to fix them. We assume you might have been already familiar with Magento Layouts, blocks and templates and you know how to make proper change to them. You can read more from Magento 1.x Developer Reference located [[http://devdocs.magento.com/guides/m1x/magefordev/mage-for-dev-4.html|here]].
-==== Issue 1: Login/Logout issue ====
+In this troubleshooting showcase, we will be looking at a case where a Magento site was having login/logout issues, comparison issues, and disappearing banner issues as well as the troubleshooting processes and recommended solutions to fix them.
-At Home page, there is one section at the top which says **"Welcome Login or Create an Account"**. With LiteMage enabled, If a user is logged in, it shows "Welcome Sam! Login or Create an Account" While it should show "Welcome, Sam Logout!". Some time, LiteMage caches " Welcome, hole login or create account " if no one is logged in or it caches "Welcome, hole Logout" if a user is logged in. In that case, for other users which just opened the home page, it shows, "Welcome, Logout".
-The user uses theme SM Market. It looks like a template problem. Basically, we need to punch a hole for that piece of info together with the login button, with welcome tag. Please refer [[litespeed_wiki:cache:litemage:troubleshooting:checking-hole-punching|this]] on how to check hole punching.
+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]].
-Global PHP variables can not be initialized in header.phtml and social.phtml, update those two files:
+==== Issue 1: Login/Logout ====
+On the home page, there is a "Welcome/Login/Create an Account" section at the top. If a user logs in, we expect to see something like ''Welcome, Sam! Logout''. With LiteMage installed, we were instead seeing ''Welcome Sam! Login or Create an Account.'' In this case, LiteMage cached ''Welcome, <punched_hole>! Login or Create an Account'' for a logged out user and served that to the logged in user.
+This issue was also happening in reverse! LiteMage would instead cache ''Welcome, <punched_hole>! Logout'' for a logged in user, serving ''Welcome, ! Logout'' to non-logged in users.
+Looking further, we see that the user uses the SM Market theme. It looks like a template problem.
+We need to punch a hole for that piece of info along with the login button and welcome tag. (**[[litespeed_wiki:cache:litemage:troubleshooting:checking-hole-punching|How to check hole punching]]**)
+Since LiteMage processes these ESI blocks in small chunks, some global PHP variables initialized in header.phtml and social.phtml were not available in these chunks. These two files needed to be updated to initialize them:
 <code>
@@ Line 14: / Line 22: @@
 </code>
-by adding the following to the top of the template(please be aware that that Varable name could be different to the example):
+The following was added to the top of the two templates
 <code>
@@ Line 22: / Line 30: @@
 </code>
-according to [[litespeed_wiki:cache:litemage:troubleshooting:uninitialized-php-vars-injected-block|this wiki]].
+according to our **[[litespeed_wiki:cache:litemage:troubleshooting:uninitialized-php-vars-injected-block|Uninitialized PHP Vars In Injected Blocks]]** page.
+==== Issue 2: Punching A Bigger Hole While Still Purging Private Sections ====
-==== Issue 2: Punch a bigger hole and but still purge private sections ====
+Now that the initialization problem is solved, we need to punch a big hole instead of small one. Logging into the Magento Admin and entering LiteMage config, we add "header" in **Customized Block Names for "toplinks" Tag**.
-After initialization problem resolved, we need to punch a big hole instead of small one. In MagentoAdmin LiteMage config, enter "header" in Customized Block Names for "toplinks" Tag.
+We also see "compare" in a toplinks block, so we add "compare" to **Additional Purge Tags for "toplinks" Blocks** as well.
-We do see "compare" on toplinks blocks, hence we need to put "compare" in Additional Purge Tags for "toplinks" Blocks.
+{{ :litespeed_wiki:cache:litemage:troubleshooting:litemage-see-minicompare-tag-add-purge.png?nolink |}}
-{{ :litespeed_wiki:cache:litemage:troubleshooting:litemage-see-minicompare-tag-add-purge.png?600 |}}
-Please refer to [[litespeed_wiki:cache:litemage:troubleshooting:logged-in-user-info-shown-to-others|this wiki]] for details.
+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: banner disappear issue ====
-The above solutions fixed Loggin/logout user showing wrong info issue. But due to the changes, the banner disappears from homepage.
-After further investigation, we found out the header template includes logic to check if it's frontend or not. If it is frontend, then it show banner. So we cannot simply punch a big hole for the header.
-The solution is go back to fix the login links. We basically needs to single out the logic and put it in its own block so we can hole punch it as a private block. The rest can be publicly cached.
+==== Issue 3: The Case of The Disappearing Banner ====
-Copy original files as .bak.
+At this point we have fixed the login/logout issue. Great! Except now the banner has disappeared from the homepage.
-Header style selection is “header4”
+After some further investigation, we found that the header template included 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 stops us from simply punching a big hole for the header, like we did earlier.
-Inside [app/design/frontend/sm_market/default/template/page/html]vi header4.phtml, We can see the logged-in link is mixed in the header template. We need to take that logic out and put in its own block and template, so we can punch a hole for that block.
+We now needed to go back and "fix" the login links.
+After making a copy of ''header4.phtml'', the header style file, we open it to begin modifying.
+<code>
+[app/design/frontend/sm_market/default/template/page/html]vi header4.phtml
+</code>
+Inside we can see the "log in" link mixed into the header template. That logic needs to be taken out and put in its own block/template so we can both hole punch it as a private block AND keep the rest of the header publicly cached.
 <code>
@@ Line 94: / Line 107: @@
 </code>
-We call the new block “welcomelogin”.
+We copy the code inside ''<div class="login-regis">'' and move it int our new welcomelogin.phtml file.
-Modify layout file [app/design/frontend/sm_market/default/layout]# vi page.xml
-Insider header block we add our new “welcomelogin” block:
-<code>
-<block type="page/html_header" name="header" as="header">
-….
-…. After welcome block
-<block type="core/template" name="welcomelogin" as="welcomelogin" template="page/html/welcomelogin.phtml"/>
-</code>
-Move the logic out of the header4.phtml and put in our new welcomelogin.phtml
 <code>
@@ Line 133: / Line 133: @@
 </code>
-Update header4.phtml, referensing the new welcomelogin block:
+We now add our new “welcomelogin” block in the header block...
+<code>
+[app/design/frontend/sm_market/default/layout]# vi page.xml
+<block type="page/html_header" name="header" as="header">
+….
+…. After welcome block
+<block type="core/template" name="welcomelogin" as="welcomelogin" template="page/html/welcomelogin.phtml"/>
+</code>
+...and update the header4.phtml file to reference the new "welcomelogin" block where the "log in" logic used to be:
 <code>
@@ Line 164: / Line 175: @@
 </code>
-Go to Magento admin panel LiteMage Configuration, add “welcomelogin” to Customized Block Names for "welcome" Tag. Banner shows up.
+Finally we go back to our LiteMage Configuration in the Magento Admin Panel and add “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 real-time, the situation may be more complicated than the above showcase, or the above may be too overwhelming, you might want to engage our experienced LiteMage Support Engineer/LiteMage Developer for professional investigation and fix them, It is fully refundable if we can not make your litemage work. Please check [[litespeed_wiki:cache:litemage:support_tiers|our support here]].
+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.