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

Technical requirements

You will need the following elements to create our template and asset overrides:

  • Any code editor to create our overrides
  • An (S)FTP client to browse files and folders (only if you work on a remote server – not necessary if you work on a local server)
  • A web browser to test our overrides
  • A working PrestaShop installation (v1.7.x minimum) with a theme or a child theme active

Note

Before starting our explanations, all the examples presented in this chapter can be applied to a theme or a child theme. You can apply these principles if you create your own theme or also if you create a child theme. It will work in both cases.

The following information can be applied only to the FO templates and assets. It will be only used to customize the FO pages and make the modules look like the rest of the active theme or child theme.

Let’s dive now into our practical example!

Imagine that you have installed the whrelaycarrier...