cancel
Showing results for 
Search instead for 
Did you mean: 

CatalogWidget issue

CatalogWidget issue

Hi,

 

I'm facing this issue, how can I fix it?

 

Error filtering template: Invalid template file: 'product/widget/content/grid_v16.phtml' in module: 'Magento_CatalogWidget' block's name: 'product\productslist_0'
4 REPLIES 4

Re: CatalogWidget issue

Hi @clemence_benharbon 

 

I have resolved this issue with my project. The problem was the name of the view folder:

app>>code>>Vendor>>ModuleName>>View>>frontend>>templates>>magicheader.phtml

This needed to be:

app>>code>>Vendor>>ModuleName>>view>>frontend>>templates>>magicheader.phtml

It may help you!
Problem Solved? Click on Kudos & Accept as Solution! 

 

Problem solved? Click Accept as Solution!

Re: CatalogWidget issue

Hi @clemence_benharbon ,

 

It seems like you have overridden the magento catalog widget template file. Please check in your code and database where this grid_v16.phtml file is mentioned because default html file Is grid.phtml

 

Also cross check whether you have this grid_v16 html present in your custom theme or module. 

 

https://community.magento.com/t5/Magento-2-x-Programming/override-Magento-Catalog-Wiget-templates-pr...

 

Hope this helps you!

Problem Solved! Click Kudos & Accept as Solution!

Re: CatalogWidget issue

In the Magento Admin section (Stores > Configuration > Web>block blast), you will need to make sure the Base URL of your site (or of each website in your multi-website setup) is set to the correct.

Re: CatalogWidget issue

 

I've come across similar issues when using the CatalogWidget, especially after upgrades or custom theme changes. Sometimes it helps to re-deploy static content and clear the cache:

 

bash
php bin/magento setup:upgrade php bin/magento setup:di:compile php bin/magento setup:static-content:deploy php bin/magento cache:flush

Also, check if the widget is properly enabled in the admin and whether any recent changes affected block permissions or template paths. If the issue persists, reviewing the logs under var/log/ can give more insight. Let us know how it goes!