Child pages
  • Templates & layouts
Skip to end of metadata
Go to start of metadata

PrestaShop template file are based on the Smarty 3 template engine.

All template files must be stored in the theme’s templates/ subfolder. For instance, the default theme has its template files in the following folder: /themes/classic/templates.

Directory structure

Templates are then split between various subfolders.

FolderDescription
_partialsCode shared across the whole site like, header, footer or notifications.
catalogProduct page, product/brand/supplier listing, search results and such.
checkoutCart, delivery options, payment options, order confirmations and such.
cmsAll the static content: contact, sitemap, CMS pages and such.
customerEverything about the customer’s account and its data.
errorsAll the error templates: not found, server error, forbidden and such.
layoutsThe theme layouts: 1, 2 or more columns, full width, everything is possible.

Template files should be written so that a single .tpl can generate a whole HTML page – unless they are inside a _partials folder or subfolder (see our coding standard, linked from the Prologue chapter of this documentation).

Templates

We make a clear difference between templates and layout:

  • A template extends a layout.
  • The layout holds the global organization of the page.
  • A template is specific to a feature: the product page for example.

There are many templates is a PrestaShop theme. The main ones includes:

  • index.tpl for the home page.
  • catalog/product.tpl for the product page.
  • catalog/listing/product-list.tpl for any product list page.
  • checkout/cart.tpl for the detailed cart.
  • checkout/checkout.tpl for the checkout process.

Specific templates

If you’re working on a big store with many languages, you may need to change the layout of the page depending on the language.

For example, you may want a different product page for American customers and Japanese ones. In this case you have to create new product.tpl template and place it in the right folder.

When searching for a template, PrestaShop will check many location to determine which file should be used. It makes it easy to have a different template for a given locale or a specific entity id.

With the Product page, the core will check the following locations (in order) and return the first template found:

  • Example with a product with ID = 3 and locale = en-US
    1. en-US/catalog/product-3.tpl
    2. catalog/product-3.tpl
    3. en/US/catalog/listing/product.tpl
    4. catalog/listing/product.tpl
  • Another example with category template for the category with ID = 9 and locale = en-US.
    1. en-US/catalog/listing/category-9.tpl
    2. catalog/listing/category-9.tpl
    3. en/US/catalog/listing/category.tpl
    4. catalog/listing/category.tpl
    5. en-US/catalog/listing/product-list.tpl
    6. catalog/listing/product-list.tpl

This feature is mostly made for developers working on a custom template for a customer.

Layouts

The layout is the organization of the page, the way in which the parts of your design are arranged. The typical example is the sidebar: is there a sidebar on your category page or is your product listing is taking the whole space?

With PrestaShop 1.7, users are given the ability to change the layout of each page independently. As a template developer, it is your role to ensure that your theme is compatible.

What’s in a layout file

The layout is the very top level of the template inheritance tree. Basically, it holds the opening and closing <html> tags.

Typical layout files look like the following snippet. This one is a full file.

<!doctype html>
<html lang="{$language.iso_code}">

<head>
  {block name='head'}
    {include file='_partials/head.tpl'}
  {/block}
</head>

<body id="{$page.page_name}" class="{$page.body_classes|classnames}">

  {hook h='displayAfterBodyOpeningTag'}

  <main>

    <header id="header">
      {block name='header'}
        {include file='_partials/header.tpl'}
      {/block}
    </header>

    <section id="wrapper">
      <div class="container">

        {block name='breadcrumb'}
          {include file='_partials/breadcrumb.tpl'}
        {/block}

        {block name="left_column"}
          <div id="left-column">
            {if $page.page_name == 'product'}
              {hook h='displayLeftColumnProduct'}
            {else}
              {hook h="displayLeftColumn"}
            {/if}
          </div>
        {/block}

        {block name="content_wrapper"}
          <div id="content-wrapper">
            {block name="content"}
              <p>Hello world! This is HTML5 Boilerplate.</p>
            {/block}
          </div>
        {/block}

      </div>
    </section>

    <footer id="footer">
      {block name="footer"}
        {include file="_partials/footer.tpl"}
      {/block}
    </footer>

  </main>

  {hook h='displayBeforeBodyClosingTag'}

  {block name='javascript_bottom'}
    {include file="_partials/javascript.tpl" javascript=$javascript.bottom}
  {/block}

</body>

</html>

From there, each part of the theme will do its job and replace content inside these bricks, keeping the same organization.

Remember to define as many blocks as possible.

  • No labels