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

The FO Smarty templates

We saw in Chapter 3, The Front Office, that the initContent() method of the front controllers was fetching the Smarty template of the active theme, with this code in the CMS FO controller example:

    ['entity' => 'cms', 'id' => $this->cms->id]

In this example, the code will fetch the /themes/classic/templates/cms/page.tpl file to generate the HTML view for the CMS page FO controller.

Remember that if you are not familiar with Smarty, you can go to the official documentation website via this URL:

Let’s study the code of this template example:

{extends file='page.tpl'}

This line tells Smarty that this view is a child of the /themes/classic/templates/page.tpl file (the parent view). The following lines in this child template override the parent view: