A PrestaShop module consists of a main PHP file with as many other PHP
files as needed, as well as the necessary template (
.tpl) files and
interface, whether to the customer (on the front office) or to the
merchant (on the back office).
Any PrestaShop module, once installed on an online shop, can interact
with one or more “hooks”. Hooks enable you to hook/attach your code to
the current View at the time of the code parsing (i.e., when displaying
the cart or the product sheet, when displaying the current stock, etc.).
Specifically, a hook is a shortcut to the various methods available from
Module object, as assigned to that hook.
For security reasons, during validation, we do not accept any call to another website/API in order to retrieve code that will later be executed on server or client.
Modules are the ideal way to let your talent and imagination as a developer express themselves, as the creative possibilities are many and you can do pretty much anything with PrestaShop’s module API.
PrestaShop 1.7 was built so that modules that were written for PS 1.6 could work almost as-is – save for minor changes and a cosmetic update, the template files being in need of adapting to the 1.7 default theme.
The major module development changes in PrestaShop 1.7 are explained in details in this Build article, and are integrated into this updated documentation. If you already know how to create a module that works with PS 1.6, we strongly advise you to read that article from top to bottom in order to get up to speed with 1.7 development.
A few native modules have been split between 1.6 & 1.7 versions of PrestaShop, as listed here:
|Original module for PrestaShop 1.6||Updated module for PrestaShop 1.7|
PrestaShop’s modules are found in the
/modules folder, which is at the
root of the PrestaShop main folder. This is true for both default
modules (provided with PrestaShop) and 3rd-party modules that are
Modules can also be part of a theme if they are really specific to it.
In that case, they would be in the theme’s own
/modules folder, and
therefore under the following path:
Each module has its own sub-folder inside the
/cache/class_index.php file contains the link between the class
and the declaration file. If there is a caching issue, this file can
safely be deleted.
/config/xml folder contains the list of all the base modules:
default_country_modules_list.xml must_have_modules_list.xml tab_modules_list.xml
When the store’s front-end doesn’t quite reflect your changes and emptying the browser’s cache is not effective, you should try emptying the following folders: