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

Defining a module

Before creating our first module, let’s define it. All the modules have a public name in regular language, such as "Hello Word", as well as a technical name that must be written without spaces and contain only lowercase alphanumerical characters.

How do we choose the technical name for our module?

Even if the only constraint for the technical name is that it must contain only lowercase alphanumeric characters, we need to choose a meaningful one and find a solution to make it unique, as we don’t want two modules to have the same technical name.

One nice solution to ensure uniqueness is to prefix the technical name with the initials of the author company (so for Web Helpers, the prefix could be wh). This prefix is then followed by the main words of the module’s regular name.

For our example "Hello World" module, we will use the "whhelloworld" technical name.

Technically, a module is a PHP file containing...