Notice: You are browsing the documentation for PrestaShop 9, which is currently in development.
You might want to read the documentation for the current version, PrestaShop 8. Read the current version of this page
PrestaShop was conceived so that third-party modules could easily build upon its foundations, making it an extremely customizable e-commerce software.
PrestaShop’s customization is based on four possibilities:
Themes are explored in full in the Themes section.
Modules, hooks and the override system are explored in this page and in the Modules section.
You should be familiar with PHP and Object-Oriented Programming before attempting to write your own module.
You can learn PHP here:
You can learn Object-Oriented programming here:
A module is an extension to PrestaShop that enables any developer to add the following:
Overriding is a system in itself. PrestaShop uses completely object-oriented code. One of the advantages of this is that, with the right code architecture, you can easily replace or extend parts of the core code with your own custom code, without having to touch the core code.
Your code thus overrides the core code, making PrestaShop behave as you prefer it to.
It is however not recommended to use an override in a module that you intend to distribute (for instance through the PrestaShop Addons marketplace), and they are forbidden in partner modules. Keep them for your own shop.
Until PrestaShop 1.6, PrestaShop was based on a 3-tier architecture:
This is the same principle as the Model>View>Controller (MVC) architecture, only in a simpler and more accessible way.
A 3-tier architecture has many advantages:
/themes folder without having to understand or even read a single line of PHP code.A model represents the application’s behavior: data processing, database interaction, etc.
It describes or contains the data that have been processed by the application. It manages this data and guarantees its integrity.
A view is the interface with which the user interacts.
Its first role is to display the data that has been provided by the model. Its second role is to handle all the actions from the user (mouse click, element selection, buttons, etc.), and send these events to the controller.
The view does not do any processing; it only displays the result of the processing performed by the model, and interacts with the user.
The Controller manages synchronization events between the Model and the View, and updates both as needed. It receives all the user events and triggers the actions to perform.
If an action requires the modification of data, the Controller “asks” the Model to modify the data and, in return, the Model informs the View that the data has been changed, so that the View can update itself.
While all versions of PrestaShop up to 1.6 took pride in only using a custom architecture, it was decided to incorporate the Symfony PHP framework starting with PrestaShop 1.7.
The driving idea is that we want our code to be more robust, more modular, and fully testable. The 1.6 architecture, inherited from version 1.5 and years of PrestaShop development, is not getting any younger, and its age is really starting to show.
Using a proven and popular open-source framework will allow us to focus on our core business code (managing a cart, handling orders, calculating prices and taxes, generating invoices, etc.) with greater efficiency, while enjoying the stability of a globally recognized framework.
In the documentation, we will refer to the 1.6 framework as the “legacy” framework, as this is a popular designation used in the software world.
Here is a small guide to help you navigate the software.
The Front Office is an application being powered by PHP and Smarty.
The frontend relies on controllers you can find in the directory controllers/front
and PrestaShop classes that contain the business logic, mainly from the classes folder.
The views and the Javascript come from the installed theme that you will find in themes/. You can have multiple themes available on a shop but only one is enabled and in use.
If the Multistore feature is enabled, each shop can use a different theme.
When you visit / on your shop, you are being returned to the Homepage.
The HTTP request you sent was received by the Dispatcher which found the right Front controller (the IndexController for Homepage).
This IndexController returned an HTTP response containing an HTML document rendered by Smarty.
The Back Office is a large application powered by PHP and Smarty for the legacy part and by PHP, Symfony, and Twig for the migrated part.
The legacy backend relies on controllers which you can find in the directory controllers/admin. It also relies on PrestaShop classes that contain the business logic, mainly from the classes folder.
For legacy pages, the views and the Javascript can be found in admin-dev/themes/default.
The Symfony backend relies on the controllers you can find in src/PrestaShopBundle/Controller/Admin and PrestaShop logic that mostly comes from the src folder, and also some classes files.
For migrated pages, you can find the views in src/PrestaShopBundle/Resources/views/Admin.
The Javascript can be found in admin-dev/themes/new-theme/js.
When you visit /admin{x}/index.php?controller=AdminCarriers&token={y} on your shop, you are being returned to the Carriers Back Office page.
The HTTP request you sent was received by the Back Office Dispatcher which found the right Admin controller (the AdminCarriersController).
This AdminCarriersController returned an HTTP response containing an HTML document rendered by Smarty.
The Admin controllers use a generic system to choose what Smarty template to use. Generic templates to display forms and listings are available and the controller provides the structure configuration (for example it controls what columns and rows are displayed).
When you visit /admin-{xxx}/index.php/configure/shop/preferences/preferences?_token={yyy} on your shop, you are being returned to the Preferences Back Office page.
The HTTP request you sent was received by Symfony and the kernel that handled your request.
Symfony found the right Back Office controller, matching your URL, the PreferencesController.
The PreferencesController returned an HTTP response containing an HTML document rendered by Twig.