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

Managing the model the modern way

As we saw in previous chapters, the model interactions in the legacy controllers were handled by the ObjectModel child classes. In versions of PrestaShop above v1.7.6, modules can use the Doctrine ORM linked to Symfony. In the Doctrine language, we designate the model object as an entity.

Creating the callback request entity

To sum up how the Doctrine way of creating a model works, we have to follow these steps:

  1. Create the src/ folder at the root of your module folder. This is the folder that will contain all the Symfony classes that we will create and use.
  2. Create a composer.json file at the root of your module folder to handle autoloading classes in our module with a defined namespace following the PSR-4 standard, using the src/ folder as the root of our namespace.
  3. Create a table manually via the install() function. We can’t use the Doctrine command-line tools to manage table creation as we are used to doing with a normal...