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 the module’s initial structure

Knowing our technical name (whreinsurance), we can now create our /modules/whreinsurance module folder. As explained in the previous chapter, we need to create a /modules/whreinsurance/whreinsurance.php file containing the module class definition, the /modules/whreinsurance/index.php file for security reasons, and the logo in the /modules/whreinsurance/logo.png file.

The /modules/whreinsurance/index.php file can be filled with the usual security content, as explained in the last chapter.

In the previous Hello World! module, we only defined a little text as an output sent to the hook. Now, we want to create a more elaborate module; that’s why we want to generate HTML via a Smarty template. We also want to use a style sheet to define the CSS styles.

Where do we store the CSS and the Smarty template files?

For all the view templates and assets (such as images, .css files, and .js files), we store them inside the views/...