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

Installing and testing our child theme example

Now that we have created a child theme to extend the classic theme, let’s try it!

Just like all the themes, we can install and change the theme’s settings via the Design | Theme & Logo BO page. If we go to this page from our BO, we should find this screen:

Figure 14.1 – The theme installation interface

Figure 14.1 – The theme installation interface

By clicking on the Use this theme button, it will activate our child theme. If we go to our FO index page after activating the child theme, nothing should have changed; it just displays all the content from the parent Classic theme.

To test the explained concepts presented in the last section of this chapter, please add the /themes/childclassicwh/templates/index.tpl file containing this code:

{extends file='parent:page.tpl'}
    {block name='page_content_container'}
      TEST
    {/block...