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

Designing the general architecture of this module

This module will be bigger than the previous ones, which is why it is better to think about the technical design before getting deep into the code. First, let’s define the data structure.

Defining the data structure

As a blog category is defined by a localized title, we will use a Doctrine Entity for the blog category containing a date add field and a date update field. We will also have to create another Doctrine lang category entity containing the title localized field as a string, linked to the Lang entity with a many-to-one relationship, and linked to the previous blog category with a many-to-one relationship too.

We will have to create a table named prefix_whblog_category in the database with the following structure:

...

Column name

Column type

id_category

int (primary autoincrement)