Book Image

Practical Module development for Prestashop 8

By : Louis AUTHIE
Book Image

Practical Module development for Prestashop 8

By: Louis AUTHIE

Overview of this book

After version 1.7, PrestaShop underwent a host of changes, including migration to a Symfony-based system from an outdated legacy code. This migration brought about significant changes for developers, from routine maintenance to module development. Practical Module Development for PrestaShop 8 is curated to help you explore the system architecture, including migrated and non-migrated controllers, with a concise data structure overview. You’ll understand how hooks enable module customization and optimize the CMS. Through the creation of seven modules, you’ll learn about the structure of modules, hook registration, the creation of front-office controllers, and Symfony back-office controllers. By using Doctrine entities, services, CQRS, grids, and forms, you’ll be guided through the creation of standard, payment and carrier modules. Additionally, you'll customize and override themes to achieve your desired e-commerce store look. By the end of this book, you’ll be well equipped to provide modern solutions with PrestaShop that meet client requirements.
Table of Contents (23 chapters)
Part 1 – Understanding How PrestaShop is Structured and How It Works
Part 2 – How to Create Your Own Modules
Part 3 – Customizing Your Theme
Appendix – Module Upgrade, The Hooks Discovery Tool, and Multi-Store Functions

Registering/unregistering a module to a hook and implementing a module’s behavior on a hook execution

Even if we will study deeply the modules’ definitions later in this book, please consider that a module will be defined by a class extending the Module class defined in the /classes/module/Module.php file.

When we install our module in the PrestaShop BO UI, it runs the install() method of our Module class. And this is precisely where we want to register our module to the hooks. It can be done with the help of the registerHook($hook_name, $shop_list = null) method of the parent Module class, where $hook_name has to be the string name of the hook to register with, and $shop_list has to be the integer array of shop IDs in the case of a multistore.

For example, if we want to register to the displayTop hook (which enables us to display HTML content at the top of our FO pages in the header), we will simply define our install method as follows:

public function install...