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

Discovering how an FO controller works

As seen in the previous chapter, the best way to understand how things work is by studying a practical example. Why not continue our explanation with the reverse engineering of the content management system (CMS) front controller displaying the content of CMS pages or categories? Those pages can be used, for example, for legal notices or information pages.

This FO controller is called CmsControllerCore and is defined in the /controllers/front/CmsController.php file.

The front controllers still rely on the legacy core because the migration to Symfony has not started yet for FO objects. That’s why routing is managed by Dispatcher, which matches URL rewriting rules with FO controllers.

In our example, when a CMS page URL is called, the CmsControllerCore class is instantiated. The first method to be called by Dispatcher is run().

First, when browsing the /controllers/front/CmsController.php file, we can see that the CmsControllerCore...