PrestaShop 1.4
Child pages
  • Coding a theme

Versions Compared

Old Version 4

changes.mady.by.user Xavier Borderie

Saved on

compared with

New Version Current

changes.mady.by.user Alexandra Even

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of contents

Table of Contents
maxLevel

...

3

Coding a theme

PrestaShop's theme system is based on a template engine, called Smarty, which allows web-designers and developers to easily build their own theme, with little technical knowledge.

...

  • All themes have their files located in the /themes root folder.
  • Each theme has its own sub-folder, in the main themes folder.
  • Each theme is made of template files (/.tpl), image files (.gif, .jpg, .png), one or more CSS files (/.css), and sometimes even JavaScript files (.js).
  • Each theme has a preview.jpg image file in its folder, enabling the shop-owner to see what the theme looks like directly from the back-office, and select the theme appropriately.

...

Info

The /css, /img and /js folder are optional, the module theme can perfectly work without them, it's up to you to create them.

...

All of your theme's text string should be enclosed in a Smarty function, like so:

Code Block

{l s='My Text'}

This will enable anyone to translate the theme into his own language, using the internal translation tool, which you can find in the PrestaShop back-office, under the "Tools" tab and its "Translation" sub-tab. In the "Modify translations" section, use the drop-down menu, choose "Back Front Office translation", then click on the flag of the language you wish to translate strings into. All the backfront-office strings will then be displayed, and the strings for your theme are those whose sections are not prefixed with "Admin*"..

h3 Transmitting data to a PrestaShop theme

The following graphic explains how data is transmitted from PrestaShop's core to its theme. Using the l() method enables the theme to display its text in the chosen language, if it has been translated beforehand.

Image Added

Best practices

Here is a non-exhaustive list of best practices that you should follow when creating a theme:

  1. Do not mix XHTML and PHP code.
  2. Do not mix XHTML and CSS code, put the CSS code in a separate .css file.
  3. Always validate your XHTML and CSS code using the W3C validators: XHTML validator, CSS validator.
  4. Do not make SQL queries from a PHP controller ({{.php file at the root of PrestaShop); prefer the use of existing methods from the PrestaShop classes, or create new methods for these classes.
  5. Always check if a method you need does not already exist in the available classes.
  6. Always make sure to produce a clear and readable code, making it easy to maintain for anyone.
  7. Do comment your code, in English.
  8. When editing the theme on a production site, always first put the shop in maintenance mode via the back-office.
  9. Use modern browsers, such as Firefox, Google Chrome or Opera, and make sure your friends do too.
  10. Whenever possible, use CSS sprites (follow-up article).
  11. If you wish to thank PrestaShop team for its hard work, please consider donating, or spread the good word!

Customizing the default theme

Follow the following steps below to create your own theme out of the PrestaShop default theme.

...

That being said, it is highly discouraged to directly change the files for the default theme, the reason being that this could introduce news new bugs and no way to go back. You need to keep the default theme intact, so that you can switch between your theme and the default one in order to find out if the issue you are seeing is tied to your theme, or to a bug in another part of PrestaShop.

...

File or folder

Description

preview.jpg

This image is used as a preview in the "Theme" selector in the "Preferences" > "Appearance" sub-tab. This image is mandatory, as without it the them theme cannot be selected. It should obviously reflect the theme's design, and not its logo or designer's name...

404.tpl

Used when the requested page is not found (HTTP error 404).

address.tpl

Used when adding or editing a client street address.

addresses.tpl

Used when listing a client's street addresses.

authentication.tpl

Used when identifying a user, or creating a new user account.

best-sales.tpl

Used to list all best sale.

breadcrumb.tpl

Used to find the navigation path, or breadcrumb trail.

category.tpl

Used to list all products in a given category.

category-tree-branch.tpl

Used only by the Category block.

category-cms-tree-branch.tpl

...

cms.tpl

Used for informational pages ("Tools" > "CMS" sub-tab).

contact-form.tpl

Used by the contact form.

discount.tpl

Used when listing all discount tickets for a single client.

errors.tpl

Used when displaying errors. Potentially called by all of the pages.

footer.tpl

Page footer.

guest-tracking.tpl

Used when a visitor has no know known account on the site, but wants his order to be tracked – and therefore needs to create an account or log in.

header.tpl

Page header

history.tpl

Used when lsiting the order history of a client.

identity.tpl

Used when a client edits his/her personal information.

index.php

Blank file, prevents visitors to view the content of the folder.

index.tpl

Welcome page.

maintenance.tpl

Used when the site is in maintenance mode.

manufacturer.tpl

Used when listing all products from a single manufacturer.

manufacturer-list.tpl

Used when listing all manufacturers.

my-account.tpl

Weclome Welcome page for a client's account.

new-products.tpl

Used when listing the products that were last added to the cart.

order-address.tpl

Used during the order process: Step 1, choosing the addresses (delivery, billing).

order-carrier.tpl

Used during the order process: Step 2, choosing the carrier mode.

order-confirmation.tpl

Used during the order process: Last step, confirming the order (after payment).

order-detail.tpl

Used to display the content of a client's order.

order-follow.tpl

Used when a client needs to ask for a product return.

order-opc.tpl

...

order-opc-new-account.tpl

...

order-payment.tpl

Used during the order process: Step 3, choosing the payment mode.

order-return.tpl

Used to display a client product return details.

order-slip.tpl

Used to display a client's credit slips.

order-steps.tpl

Order process progress bar.

pagination.tpl

Used by all pages that list products. Displays the pagination button, enable to skip to the next/previous page of products.

password.tpl

Used when a client needs to change his password.

prices-drop.tpl

Used to list all current promotions.

product.tpl

Used to display details for a single product.

product-list.tpl

Used by all pages that list products. Displays the actual products list.

product-sort.tpl

Used by all pages that list products. Displays a menu enabling to sort and filter products.

products-comparison.tpl

...

scenes.tpl

Used to display a scene's details within a product category.

search.tpl

Used to list results from a search query.

shopping-cart.tpl

Used to list products in a client's cart.

shopping-cart-product-line.tpl

Used to display from a single cart row.

sitemap.tpl

Used to display the site map.

store_infos.tpl

...

stores.tpl

...

supplier.tpl

Used to list all the products from a single supplier.

supplier-list.tpl

Used to list all suppliers.

thickbox.tpl

Used to zoom a product's picture.

/cache

...

/css

Contains all style sheet files for the theme. The global.css file deals with the layout for most of the site. Unless you know exactly what you are doing, you should leave these files alone.

/img

Contains all of the theme's images. You should replace these images with your own adequate creations. If you do not know what to make of it, you should leave the original files.

/js

Contains all of the theme's JavaScript files. Unless you know exactly what you are doing, you should leave these files alone.

/lang

Contains all translation files. These are generated by the back-office translation tool, and should not be edit directly. If a translation needs editing, go to the back-office, "Tools" tab, "Translation" sub-tab, "Modify translation" section, and choose "Front office translations".

A few advices

Firebug, Dragonyfly Dragonfly et al.: your work as a front-end developer can greatly helped with the right tools at hand, provided you test your design in a modern browser that provides such tools, either through a module (Firefox's FireBug) or directly embedded (Opera's Dragonfly, Chrome & Webkit's Web Inspector). Learn to master them, and you will quickly be amazed by their usefulness.

...

preview.jpg file: Once your design is complete, you can create the preview image file. Take a screen shot, then resize it to 180px width in order to use it instead of the default preview.jpg file. You can either used the screenshot tool provided by your OS (Windows' Snipping Tool, OS X's Cmd+Shift+4 key combo), or install a browser extension, such as Firefox's FireShot or Screengrab.

Layered navigation: In order for a theme to be compatible with layered navigation, the /themes/themename/product-list.tpl file must have its product list area be encapsulated within a tag with the "product_list" id; otherwise, the layered navigation will not be able to update the product list.

Code Block
<div id="product_list">

...or...

<ul id="product_list">

Integration: where the hooks and modules are

...