如何覆盖PrestaShop 1.7.7的模块类？——ps_facetedsearch模块MySQL类覆盖及链式类依赖疑问

Great question! Let's break this down clearly—you don't need to touch every class in the call chain. Only the MySQL class you want to modify needs your attention, thanks to PrestaShop's dependency injection system. Here's how to do it:

Core Takeaway: No Need to Rewrite the Entire Call Chain #

You do not have to extend or modify every linked class (like the Search class that uses MySQL). PrestaShop's service container lets you swap out specific implementations without altering the classes that depend on them. The Search class will automatically use your overridden MySQL class once you set it up correctly.

Step-by-Step Implementation #

1. Create Your Custom MySQL Class #

First, make a new class in your own custom module (using a custom module is better than modifying core/module files directly—avoids losing changes on updates) that extends the original MySQL class:

// Path: mystore/modules/my_custom_facet/src/Adapter/CustomMySQL.php
namespace MyCustomFacet\Adapter;

use PrestaShop\Module\PsFacetedSearch\Adapter\MySQL as OriginalMySQL;

class CustomMySQL extends OriginalMySQL
{
    // Override only the methods you need to change
    public function getProductCount($filters)
    {
        // Your custom logic here
        // Example: Modify the query before executing
        $originalCount = parent::getProductCount($filters);
        // Adjust the result if needed
        return $originalCount;
    }
}

2. Override the Service Definition #

ps_facetedsearch registers its MySQL class as a service in PrestaShop's container. You need to overwrite that service definition in your module's services.yml to use your custom class:

# Path: mystore/modules/my_custom_facet/config/services.yml
services:
    prestashop.module.ps_facetedsearch.adapter.mysql:
        class: MyCustomFacet\Adapter\CustomMySQL
        arguments:
            # Match the arguments from the original module's services.yml
            - '@doctrine.dbal.default_connection'
            - '@=service("prestashop.adapter.legacy.configuration").getInt("PS_LIMIT_PRODUCTS")'
            # Add any other required arguments from the original service

Check the ps_facetedsearch/config/services.yml file to copy all required arguments exactly—this ensures your class works with existing dependencies.

3. Set Your Module's Priority Higher #

Make sure your module loads before ps_facetedsearch so your service definition takes precedence. Edit your module's config.xml:

<!-- Path: mystore/modules/my_custom_facet/config.xml -->
<?xml version="1.0" encoding="UTF-8"?>
<module>
    <name>my_custom_facet</name>
    <tab>front_office_features</tab>
    <version>1.0.0</version>
    <author>Your Name</author>
    <bootstrap>true</bootstrap>
    <priority>1</priority> <!-- Lower number = higher priority; ps_facetedsearch uses ~10 by default -->
</module>

4. Install & Enable Your Custom Module #

Go to your PrestaShop back office, install and activate your custom module. PrestaShop's service container will now use your CustomMySQL class wherever the original MySQL class was used—including in the Search class and any other parts of the module that depend on it.

What If the Original Class Uses Direct Instantiation? #

In rare cases, if the Search class directly creates a MySQL instance with new MySQL() instead of using the service container, you can use PrestaShop's override system:

1. Create the path mystore/override/modules/ps_facetedsearch/src/Adapter/
2. Copy your CustomMySQL.php file there, rename it to MySQL.php, and update the namespace to match the original:

namespace PrestaShop\Module\PsFacetedSearch\Adapter;

// Your custom class code, extending the original (now loaded via PrestaShop's override system)

Then run the "Clear cache" option in the back office to apply the override.

Note: Using the service override method is preferred over file overrides, as it's cleaner and less likely to cause conflicts during module updates.

内容的提问来源于stack exchange，提问作者Marek J.