Content and footer of magento front end is not displaying except header

Content and footer of magento front end is not displaying except header

August 6, 2026 · Illustrated author avatarBy Stefan Bogdanescu
Content and footer of magento front end is not displaying except header

Are you facing a frustrating issue where your Magento frontend displays only the header and navigation menu, omitting crucial elements like content and footer? You’re not alone—this common problem can be easily resolved with some strategic troubleshooting. Let’s dive into this hair-pulling conundrum and find a solution that won’t make you bald before noon.

Step 1: Verify Your Layout XML

The first port of call is the layout XML file associated with your current page. Check if the necessary handles for displaying content and footer are enabled. Open app/design/frontend/<YourTheme>/layout/checkout_index_index.xml or the corresponding file for your specific page, and ensure you have something like this:

<layout version="0.1.2">
  <default>
    <reference name="root">
      <block type="checkout/login" template="checkout/login.phtml" />
    </reference>
    <!-- Add these lines if missing -->
    <reference name="content">
      <block type="core/template" template="page/html/content.phtml"/>
    </reference>
    <reference name="before_body_end">
      <block type="core/text_html" name="global.scripts" as="global_scripts" agent="Mage_Core_Model_Layout_Update" template="page/js/global.phtml"/>
    </reference>
  </default>
</layout>

If the content and before_body_end references are missing, add them back. This ensures that the content area and footer scripts are included in your layout.

Step 2: Inspect Your Template Files

Next, let’s look at the actual templates responsible for rendering the content and footer:

  1. Content template: Check if app/design/frontend/<YourTheme>/template/page/html/content.phtml exists and contains the necessary PHP logic to render the page content.
<div class="col-main">
  <?php echo $this->getChildHtml('content'); ?>
</div>
  1. Footer template: Verify that app/design/frontend/<YourTheme>/template/page/html_footer.phtml is intact and includes the footer HTML structure:
<div class="footer-container">
  <div class="col-main">
    <?php echo $this->getChildHtml('global_footer') ?>
  </div>
</div>

If either of these files or their respective logic is missing, restore them from your theme’s original package or a fresh Magento installation as a backup.

Step 3: Check Your Configuration

Ensure that your theme configuration is properly set up. Open app/design/frontend/<YourTheme>/etc/view.xml and look for the following:

<default>
  <layout>
    <updates>
      <!-- Verify that the XML file we checked earlier (e.g., checkout_index_index.xml) is listed here -->
      <checkout_index_index translate="label" module="checkout">
        <label>Checkout Default</label>
        <file>checkout_index_index.xml</file>
      </checkout_index_index>
    </updates>
  </layout>
</default>

If the layout file isn’t specified or has an incorrect path, update it to reflect your actual XML file location.

Step 4: Flush Cache and Reindex

Finally, flush all Magento cache using the command line:

php bin/magento cache:flush

And reindex the database for optimal performance:

php bin/magento indexer:reindex

Clear browser cache to ensure you’re seeing the updated content.

Conclusion

In most cases, resolving this issue comes down to ensuring that your layout XML references are intact and pointing to the correct template files. If you’ve verified all the steps above and are still facing issues, it might be time to reach out to a Magento expert or contact our support team at Laravel Company for more personalized assistance.

Remember that Magento themes often include complex overrides, so always compare your modified files against the original theme package or backup. With these troubleshooting steps, you should now be able to display both content and footer on your Magento frontend—giving you back precious hair and saving your morning routine from further distress!

Checkout Themes Errors JavaScript

Our network