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)
1
Part 1 – Understanding How PrestaShop is Structured and How It Works
8
Part 2 – How to Create Your Own Modules
16
Part 3 – Customizing Your Theme
Appendix – Module Upgrade, The Hooks Discovery Tool, and Multi-Store Functions

Creating a Widget to promote our module anywhere on the FO

First, let’s define what a widget is. From version 1.7 of PrestaShop, the new concept of widgets appeared. Any module can implement a widget interface by adding use PrestaShop\PrestaShop\Core\Module\WidgetInterface; to its main module class and using class ModuleClassName extends Module implements WidgetInterface for the main module class definition.

Following this interface, we have to implement the two following functions:

public function renderWidget($hookName, array $configuration);
public function getWidgetVariables($hookName, array $configuration);

If we don’t declare any hookNameOfTheHook($params) functions in our module, the renderWidget() function will be triggered by the hook’s name provided via the $hookName argument. The $configuration argument will contain the params of the hook trigger.

The getWidgetVariables() function will be used to compute the data to assign to the template...