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

Overriding a module JavaScript asset from a (child) theme

Still with the whrelaycarrier module, let’s trigger an alert displaying the Thanks for the choice! message on a pickup relay line click, on the modal box. The expected behavior would look like this:

Figure 15.5 – The alert box displayed on a pickup point line click after the ajax process

Figure 15.5 – The alert box displayed on a pickup point line click after the ajax process

As a reminder, the JavaScript code defining the modal box behavior can be found in the /modules/whrelaycarrier/views/js/checkout.js file.

By following the same method presented in the previous sections, for both templates and CSS file overrides, if we create a /themes/childclassicwh/modules/whrelaycarrier/views/js/checkout.js file, it will replace the original JavaScript file and will be executed instead.

So, let’s do it and copy and paste the original JavaScript content and replace the $('#whrelaycarrier_points>div>ul>li').click(function(){…}) selector event...