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

Building assets with Webpack

Here are the steps for building a process with Webpack:

  1. Please empty the /themes/classic/assets/css/ and /themes/classic/assets/js/ folders to make sure that the output files will be generated by us.
  2. From the /themes/classic/_dev/ folder, please execute the npm run build command.
  3. If you go to the /themes/classic/assets/ folder, you will find the compiled CSS and images/fonts in the /themes/classic/assets/css/ folder and the compiled JavaScript in the /themes/classic/assets/js/ folder. That works and saves us a lot of compiling commands!
  4. In the same way, if we execute the npm run watch command, it does the same thing, but we see that it repeats the process when an entry file is saved. That will enable us to code and preview without having to retype the compiling command all the time. It’s a nice tool during long coding tasks.

Feel free to test it again with our Customer Callback Request module available at this URL: https...