Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
litespeed_wiki:cache:litemage:troubleshooting:logged-in-logout_banner_disappear [2017/05/04 20:43] Michael Alegre [Issue 1: Login/Logout] |
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 7: | Line 7: | ||
| ==== Issue 1: Login/Logout ==== | ==== Issue 1: Login/Logout ==== | ||
| - | On the home page, there is a **"Welcome Login or 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, <hole> login or create 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 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, <hole> Logout" for a logged in user, serving "Welcome, Logout" to non-logged in users. | + | 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. | Looking further, we see that the user uses the SM Market theme. It looks like a template problem. | ||
| Line 35: | Line 35: | ||
| ==== 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 needed 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**. | + | 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**. |
| We also see "compare" in a toplinks block, so we add "compare" to **Additional Purge Tags for "toplinks" Blocks** as well. | We also see "compare" in a toplinks block, so we add "compare" to **Additional Purge Tags for "toplinks" Blocks** as well. | ||
| Line 46: | Line 46: | ||
| ==== Issue 3: The Case of The Disappearing Banner ==== | ==== Issue 3: The Case of The Disappearing Banner ==== | ||
| - | At this point we have fixed the Login/logout issue. Great! Except now the banner has disappeared from the homepage. | + | At this point we have fixed the login/logout issue. Great! Except now the banner has disappeared from the homepage. |
| 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. | 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. | ||