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

Adding a Smarty template view

Even if we could directly return the raw HTML code to display in the hookDisplayFooterBefore($params) function, we will do this by respecting the model-view-controller (MVC) concept. We will now use Smarty to generate the HTML view. First, we need to create a Smarty template that will be fetched by the module to return the right HTML output. We will now create a /modules/whreinsurance/views/templates/hook/whreinsurance.tpl file containing the HTML code of the module output. As we saw before, all the Smarty templates used inside the display hook calls must be stored inside the /modules/whreinsurance/views/templates/hook/ folder. If you plan to have multiple display hook calls, you can call the .tpl file by the name of the hook calling. If you plan to use only one display hook, it is recommended by the PrestaShop developer documentation to call the .tpl file by the technical name of the module. It is not mandatory; it is just good practice.

One example...