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 our module design

As we learned in Chapter 8, Reinsurance Block Module, we need to make sure that before we do any coding, we know exactly what we want to create.

As mentioned in the introduction, we want to create a module enabling customers to send their first name, last name, and phone number to customer services to receive a phone call back. We want customer services to be able to set the maximum number of hours before a callback via a configuration form inside the BO. Customer services will receive all the request notifications by email and will be able to find all of them as a list on a BO page, as well as being able to delete any request manually.

A mockup of the form we want to present in the footer of the FO pages could look as follows:

Figure 9.1 – A simple mockup of a callback form

Figure 9.1 – A simple mockup of a callback form

A mockup of the configuration form in the BO for our module could look as follows:

Figure 9.2 – A mockup of the configuration page for our module

Figure 9.2 – A mockup of...