Magento – Reference to undeclared plugin with name ‘stockedProductsFilterPlugin’ warning in di compile magento 2.3.2

magento2pluginsetup-di-compile

I have recently upgraded my site from Magento 2.2.6 to Magento 2.3.2.
During each di compilation it shows a warning like

main.INFO: Reference to undeclared plugin with name 'stockedProductsFilterPlugin'. [] []

When i debugged this case and i found that in Magento 2.3.0 there was a plugin available with this name in 'module-elasticsearch' module and in Magento 2.3.2 they have removed that plugin and definition from that module. But in the module 'module-inventory-elasticsearch' they are written to disable that plugin which is currently not existing like below.

<config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="urn:magento:framework:ObjectManager/etc/config.xsd">
<type name="Magento\CatalogSearch\Model\Indexer\Fulltext\Action\DataProvider">
    <plugin name="stockedProductsFilterPlugin" disabled="true"/>
    <plugin name="stockedProductFilterByInventoryStockPlugin" type="Magento\InventoryElasticsearch\Plugin\CatalogSearch\Model\Indexer\Fulltext\Action\DataProvider\StockedProductFilterByInventoryStock"/>
</type>

So since there is no definition for that plugin this warning is showing. So how we can remove this warning from di compile. When i removed the disabling code from this module the warning will gone. But we are not supposed to edit the magento core files. Also another way i found create a dummy plugin with the same name, but this is a bad way. Any other solution for this?

Best Answer

I'm having a similar error reported in system.log:

main.INFO: Reference to undeclared plugin with name 'priceIndexUpdater'

Mage Version: 2.3.6

When: The log occurs when finalizing checkout: pushing "Place order" button, we have a "Something went wrong ..." message too.

@amesh wrote: "We have just created a patch to remove this code from the di.xml file". How did you create that patch? Did you simply comment xml definitions apparently related to error?

Thank you so much ...

Related Solutions

Magento2 Module – Fix ‘main.CRITICAL: Plugin Class Doesn’t Exist’

I couldn't reproduce your error, but I got an other one.

Then I did some minor adjustments to your code and it worked.
First drop the InstallSchema.php file. It does nothing so it is useless.

Then make sure that your plugin file is in Amaj/CorePlugin/Model/Currency/Plugin.php and it looks like this:

<?php

namespace Amaj\CorePlugin\Model\Currency;

class Plugin
{
    protected $logger;

    public function __construct(\Psr\Log\LoggerInterface $logger) {
        $this->logger = $logger;
    }

    /**
     * @param $subject
     * @param \Closure $proceed
     * @param $price
     * @param array $options
     * @return string
     */
    public function aroundFormatTxt(
        $subject,
        \Closure $proceed,
        $price,
        $options = []
    )
    {
        $this->logger->info('Amaj aroundFormatTxt');
        return '2';
    }

}

you don't need parent::__construct(); in the constructor because there is no parent class.
And I replaced $logger->info with $this->logger->info because there is no $logger variable.

Magento2.1 – How to Change Product Price with Plugin

The problem is that I placed the di.xml into the frontend subfolder, thinking that this defines the area the plugin applies to. But reading the docu ( http://devdocs.magento.com/guides/v2.1/architecture/archi_perspectives/components/modules/mod_and_areas.html )

Magento area types

Magento is organized into these main areas:

Magento Admin (adminhtml): entry point for this area is index.php or pub/index.php. The Admin panel area includes the code needed for store management. The /app/design/adminhtml directory contains all the code for components you’ll see while working in the Admin panel.

Storefront (frontend): entry point for this area is index.php or pub/index.php. The storefront (or frontend) contains template and layout files that define the appearance of your storefront.

Basic (base): used as a fallback for files absent in adminhtml and frontend areas.

again it seems that frontend refers only to display purposes but not saving or anything.

Best Answer

Related Solutions

Magento2 Module – Fix ‘main.CRITICAL: Plugin Class Doesn’t Exist’

Magento2.1 – How to Change Product Price with Plugin

Related Topic