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

Discovering the hook ObjectModel child object

Hooks are referenced in the database and are represented in the core via the Hook class defined in the /classes/Hook.php file.

The fields describing a hook in the prefix_hook table are as follows:

  • The name column is used in the code as the string identifying the hook; it must be unique.
  • The title column is the short text describing the hook.
  • The description column is the longer text to define what the hook does.
  • The position column is a Boolean always equal to true. It is not used anymore but stays in the code.
  • The active column is a Boolean equal to false if the hook is not active, and equal to true if the hook is active.

As hook names can become long and hard to remember, a prefix_hook_alias table enables you to add an alias string to a hook in a one-to-one relationship between a hook and an alias.

Also, hooks have a many-to-many relationship with the Module object. This relationship is materialized...