Override Constructor of Vendor/Magento/Module_Catalog/Block in Magento 2

blocksmagento2

I am trying to get product list from specific category id.
i am using magento 2.2.1 version.

below are my code of
Block File : view.php
i want to override this file from vender.

Here is my custom module :

app\code\Narola\Magentocatalog\Block\Category\View.php

namespace Narola\Magentocatalog\Block\Category;
class View extends \Magento\Catalog\Block\Category\View
{
  protected $_productCollectionFactory;
  protected $_categoryFactory;

  public function __construct(
    \Magento\Framework\View\Element\Template\Context $context,
    \Magento\Catalog\Model\ResourceModel\Product\CollectionFactory $productCollectionFactory,
    \Magento\Catalog\Model\CategoryFactory $categoryFactory,
    array $data = []
  ) {
    $this->_categoryFactory = $categoryFactory;
    $this->_productCollectionFactory = $productCollectionFactory;
    parent::__construct($context, $data);
}

public function getSubcategory($catId)  
{
    $objectManagerr = \Magento\Framework\App\ObjectManager::getInstance();
    $categoryFactory = $objectManagerr->create('Magento\Catalog\Model\ResourceModel\Category\CollectionFactory');
    $collection = $categoryFactory->create()
    ->addFieldToFilter('parent_id', $catId) 
    ->addAttributeToSelect('*');
    return $collection;
}

public function  getSubcategory_product($sub_catid){
    $category = $this->_categoryFactory->create()->load($categoryId);
    $collection = $this->_productCollectionFactory->create();
    $collection->addAttributeToSelect('*');
    $collection->addCategoryFilter($category);
    $collection->addAttributeToFilter('visibility', \Magento\Catalog\Model\Product\Visibility::VISIBILITY_BOTH);
    $collection->addAttributeToFilter('status',\Magento\Catalog\Model\Product\Attribute\Source\Status::STATUS_ENABLED);
    return $collection;
} 
}

==============================

Here when i add constructor i am getting below error.

Fatal error: Uncaught TypeError: Argument 2 passed to Magento\Catalog\Block\Category\View::__construct() must be an instance of Magento\Catalog\Model\Layer\Resolver, array given, called in C:\wamp64\www\magento_221\app\code\Narola\Magentocatalog\Block\Category\View.php on line 18 and defined in C:\wamp64\www\magento_221\vendor\magento\module-catalog\Block\Category\View.php on line 45

If any one has solution regarding this then please provide me.

Best Answer

Your constructor has to be like

\Magento\Framework\View\Element\Template\Context $context,
\Magento\Catalog\Model\ResourceModel\Product\CollectionFactory $productCollectionFactory,
\Magento\Catalog\Model\CategoryFactory $categoryFactory,
\Magento\Framework\View\Element\Template\Context $context,
\Magento\Catalog\Model\Layer\Resolver $layerResolver,
\Magento\Framework\Registry $registry,
\Magento\Catalog\Helper\Category $categoryHelper,
array $data = []

and call the parent function like

parent::__construct($context, $layerResolver, $layerResolver, $categoryHelper, $data);

Related Solutions

Magento 2 – Fix Model Override Issue

It's caused by the fact that your model constructor does not match your original model constructor.

So this is the constructor from Magento\Newsletter\Model\Queue :

public function __construct(
    \Magento\Framework\Model\Context $context,
    \Magento\Framework\Registry $registry,
    \Magento\Newsletter\Model\Template\Filter $templateFilter,
    \Magento\Framework\Stdlib\DateTime\DateTime $date,
    \Magento\Newsletter\Model\TemplateFactory $templateFactory,
    \Magento\Newsletter\Model\ProblemFactory $problemFactory,
    \Magento\Newsletter\Model\ResourceModel\Subscriber\CollectionFactory $subscriberCollectionFactory,
    \Magento\Newsletter\Model\Queue\TransportBuilder $transportBuilder,
    \Magento\Framework\Model\ResourceModel\AbstractResource $resource = null,
    \Magento\Framework\Data\Collection\AbstractDb $resourceCollection = null,
    array $data = []
) {
    parent::__construct(
        $context,
        $registry,
        $resource,
        $resourceCollection,
        $data
    );
    $this->_templateFilter = $templateFilter;
    $this->_date = $date;
    $this->_templateFactory = $templateFactory;
    $this->_problemFactory = $problemFactory;
    $this->_subscribersCollection = $subscriberCollectionFactory->create();
    $this->_transportBuilder = $transportBuilder;
}

To fix your constructor it needs to be:

public function __construct(
    \Magento\Framework\Model\Context $context,
    \Magento\Framework\Registry $registry,
    \Magento\Newsletter\Model\Template\Filter $templateFilter,
    \Magento\Framework\Stdlib\DateTime\DateTime $date,
    \Magento\Newsletter\Model\TemplateFactory $templateFactory,
    \Magento\Newsletter\Model\ProblemFactory $problemFactory,
    \Magento\Newsletter\Model\ResourceModel\Subscriber\CollectionFactory $subscriberCollectionFactory,
    \Magento\Newsletter\Model\Queue\TransportBuilder $transportBuilder,
    \Magento\Framework\Model\ResourceModel\AbstractResource $resource = null,
    \Magento\Framework\Data\Collection\AbstractDb $resourceCollection = null,
    \Vendor\Module\Block\Testing $customergroup,
    \Magento\Customer\Model\ResourceModel\Group\Collection $customergroupdata,
    array $data = []
)
{
    $this->_customergroup = $customergroup;
    $this->_customergroupdata = $customergroupdata;
    parent::__construct(
        $context,
        $registry,
        $templateFilter,
        $date,
        $templateFactory,
        $problemFactory,
        $subscriberCollectionFactory,
        $transportBuilder,
        $resource,
        $resourceCollection,
        $data
    );
}

Magento2 – Why Getting Categories and Names on Product View Page Fails

Just to confirm, I've tested your code on a fresh Magento 2.1.2 and it works absolutely fine in both cases (when accessing the product via its direct URL or when accessing the product via the category).

Regarding your second question: yes I'm 90% sure the Porto theme is the problem. All those themes are shipped with a huge number of widgets, modules, custom modifications which are very often the root cause of many issues.

I'm not saying those themes are bad, they're great when you're dealing with a small store which do not need a lot of custom development and modifications. However, when you're dealing with a bigger structure, problems arise.

Best Answer

Related Solutions

Magento 2 – Fix Model Override Issue

Magento2 – Why Getting Categories and Names on Product View Page Fails

Related Topic