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

Link to this comparison view

Both sides previous revision Previous revision
Next revision Both sides next revision
litespeed_wiki:cache:litemage:customization:specialized-front-page-footer [2015/12/21 17:39]
Michael Alegre removed
litespeed_wiki:cache:litemage:customization:specialized-front-page-footer [2015/12/21 17:04] (current)
Michael Alegre
Line 1: Line 1:
 +====== Using A Specialized Footer On Your Front Page ======
 +Some websites use a specialized footer containing extra information (usually for SEO purposes) on their front page. This is usually done by determining if the current page is the homepage in the footer template and then treating that footer differently. This dynamic logic makes the footer cache unfriendly, as LiteMage will punch a hole for the "​footer"​ block as a public block. This means that whichever version of the footer, specialized or not, LiteMage encounters first will be be the version that is served on every page.
 +**For Example:**
 +  <?php
 +  $page = Mage::​app()->​getFrontController()->​getRequest()->​getRouteName();​
 +  $isHomepage = false;
 +  if($page == '​cms'​){
 +       ​if('​home'​ == Mage::​getSingleton('​cms/​page'​)->​getIdentifier()){
 +            $isHomePage = true;
 +       }
 +  }
 +  if($isHomepage):​ ?>
 +       <​div class="​footer_bottom_text_container">​
 +            <div class="​footer_bottom_text">​
 +                 <?​php echo $this->​getLayout()->​createBlock('​cms/​block'​)->​setBlockId('​footer_bottom_text'​)->​toHtml() ?>
 +            </​div>​
 +       </​div>​
 +  <?php endif; ?>
 +  ​
 +**Solution:​** Have the homepage specially handled so that the "​footer"​ hole will not be punched there. The first step in accomplishing this is to remove the dynamic portion of the footer block to allow the public "​footer"​ ESI block to continue being punched for other pages. Removing this dynamic code will also have the positive side effect of improving footer render time.
 +  - Copy the footer template to a new file as "​homefooter.phtml"​. As this will only be used for the home page, there is no need to keep the added home page logic and the content can instead be added directly.<​code><​div class="​footer_bottom_text_container">​
 +       <​div class="​footer_bottom_text">​
 +            <?php echo $this->​getLayout()->​createBlock('​cms/​block'​)->​setBlockId('​footer_bottom_text'​)->​toHtml() ?>
 +       </​div>​
 +  </​div></​code>​
 +  - Update "​footer.phtml"​ by removing the aforementioned logic as this will only be used for non home pages only.
 +  - Identify the footer block section of the layout XML file currently in use. Copy the full footer block section, including all sub blocks used.
 +  - In the Magento Admin Panel, navigate to CMS >> Pages and click edit to edit the home page.
 +    - Navigate to Design >> Page Layout >> Layout Update XML
 +    - Add the copied footer block XML here with the following modification:​ \\ <​code> ​    <​remove name="​footer"/>​
 +<​reference name="​root">​
 +     <​block type="​page/​html_footer"​ name="​homefooter"​ as="​footer"​ template="​page/​htm/​homefooter.phtml">​
 +       ...
 +     </​block>​
 +</​reference></​code>​ This removed the old footer block and added the newly created homefooter.phtml template for the home page.
 +**Note:** The block name used here has to be unique, but the alias must remain the same as to not interfere with any applied logic. Thus, it is important to include: <​code>​name="​homefooter"​ as="​footer"</​code>​
 +**Note:** **Blocks HTML output** should remain disabled under System >> Cache Management in the Magento Admin Panel.
  • Admin
  • Last modified: 2015/12/21 17:04
  • by Michael Alegre