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)
Part 1 – Understanding How PrestaShop is Structured and How It Works
Part 2 – How to Create Your Own Modules
Part 3 – Customizing Your Theme
Appendix – Module Upgrade, The Hooks Discovery Tool, and Multi-Store Functions

Creating a modern BO controller containing a grid to list all the requests

As customer service members may need to review the saved callback requests, we need a new page in the BO of our PrestaShop. Let’s use Symfony to create a brand-new BO controller the modern way.

Creating a modern admin controller

Let’s create a BO admin controller in our module. The standard process for this starts with the creation of a class extending the FrameworkBundleAdminController class in the src/Controller folder of your module.

To apply this process to our module, let’s create the /modules/whcallback/src/Controller/AdminWHCallbackRequestController file. While there is no specification for the naming of a controller, it is important to use a comprehensive one anyway. A good practice could be to prefix it with Admin because of its BO destination and to suffix it with Controller because it is a BO controller.

The newly created controller will contain the following code...