Differences

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

Link to this comparison view

Next revision
Previous revision
Next revision Both sides next revision
litespeed_wiki:cache:litemage:troubleshooting:logged-in-out-with-missing-banner [2017/05/04 21:11]
Michael Alegre created
litespeed_wiki:cache:litemage:troubleshooting:logged-in-out-with-missing-banner [2017/05/05 18:55]
Lisa Clarke [Issue 2: Punching A Bigger Hole While Still Purging Private Sections]
Line 7: Line 7:
 ==== Issue 1: Logged In/Out ==== ==== Issue 1: Logged In/Out ====
  
-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.+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 reverseLiteMage would instead ​cache ''​Welcome, ​<​punched_hole>​! Logout'' ​for logged in userserving ''​Welcome, ! Logout'' ​to non-logged ​in users.+This issue was also happening in reverseLiteMage would cache **Welcome, ​Sam! Logout** for logged in Samand then serve **Welcome, ! Logout** to different ​logged ​//​out// ​users.
  
-Looking further, we see that the user uses the SM Market theme. It looks like a template problem.+Looking further, we saw that these cases were all occurring on sites that used the SM Market theme. It looked ​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]]**)+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.
  
-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: +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: 
  
-<​code>​ +**/​home/​user1/​public_html/​domain1.com/​app/​design/​frontend/​sm_market/​default/​template]#​** ''​vi page/​html/​header.phtml''​ 
-/​home/​user1/​public_html/​domain1.com/​app/​design/​frontend/​sm_market/​default/​template]#​ vi page/​html/​header.phtml +**/​home/​user1/​public_html/​domain1.com/​app/​design/​frontend/​sm_market/​default/​template]#​** ''​vi page/​html/​social.phtml''​
-/​home/​user1/​public_html/​domain1.com/​app/​design/​frontend/​sm_market/​default/​template]#​ vi page/​html/​social.phtml +
-</​code>​+
    
-The following was added to the top of the two templates+The following was added to the top of the two template files:
  
 <​code>​ <​code>​
Line 30: Line 28:
 </​code>​ </​code>​
  
-according to our **[[litespeed_wiki:​cache:​litemage:​troubleshooting:​uninitialized-php-vars-injected-block|Uninitialized PHP Vars In Injected Blocks]]** page.+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 ==== ==== Issue 2: Punching A Bigger Hole While Still Purging 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**. ​+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 see "​compare"​ in a toplinks block, so we add "compare" ​to **Additional Purge Tags for "​toplinks"​ Blocks** as well.+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 |}} {{ :​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]]**.+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]].
  
  
  • Admin
  • Last modified: 2017/05/05 19:10
  • by Lisa Clarke