New answers tagged

2

Run following query will resolve your issue if it is null sku related error: SKU should be empty or string. UPDATE catalog_product_entity SET sku='' WHERE sku IS NULL; You can check your corrupted sku and fix that. if don't get any affected rows for that query. your SKU has some corrupted data. check your corrupted sku that is not a string Or you can ...


0

I finally managed to sort this out. This was due to a change in order email template. disabling order email solved it, and I changed order email content in order to make it work.


1

Downgrade symfony/console to v4.4.26. composer require symfony/console=4.4.26 error resolved.


0

Please make sure you are using composer 1 if not then download composer.phar file and run php composer.phar install and check if it runs smoothly. If this is done then run composer command php composer.phar require [module name] if you want then you can use --no-update followed by your command. Happy Coding


0

this is due to the symfony/console package. Downgrading the symfony package worked for me. see this thread. Errors during compilation: AbstractConfigOption.php


0

As you got the same PHP version and everything, i guess that you are just missing dependent vendor packages inside the linux docker container? Try composer install command in project root to fix it. Afterwards run the cli command again and it should work. Good luck


0

There are 4 solutions to resolve this error on WINDOWS XAMPP. Solution 1:- One of the reason for this error is sodium extension not enabled in php.ini file, so we need to enable it and re-run install command in the command prompt. To enable:- Go to C:\xampp\php\php.ini, find "extension=sodium" in it and then remove semicolon from beginning of this ...


0

In Magento 1, You have some/any product without SKU (magento 1 allow it). When it comes to magento 2, SKU is required. Just go through your catalog in M1 OR query database to check for missing SKU and add missing SKU to those products! Hope above will help you.


0

The file vendor/mirasvit/module-core/Model/Module.php has been removed in the module mirasvit/module-core version 1.2.118. To resolve this issue downgrade to version 1.2.114 composer req mirasvit/module-core:1.2.114 It is imported to pin this version in composer.json as the mirasvit/module-seo module defines a lax dependency definition in its' composer.json:...


1

<?php namespace Vendor\Extension\Yourcontrollerfolder; class Yourcontrollerclass { protected $request; public function __construct( \Magento\Framework\App\RequestInterface $request) { $this->request = $request; } public function Yourfunction() { $GET = $request->getParams(); $POST = $request->getPost()...


1

You need to use magento method like this : <?php namespace Vendor\Extension\Yourcontrollerfolder; class Yourcontrollerclass { protected $request; public function __construct( \Magento\Framework\App\RequestInterface $request) { $this->request = $request; } public function Yourfunction() { ...


0

this solves the problem but nobody has taken the effort of running the required tests for it to pass all checks (since 6 jan) so it will not be added, shame shame ;-) https://github.com/magento/magento2/pull/31565/files


0

I just came across this problem. It was caused by the long list of pending cron jobs in table cron_schedule. I backed up the database then truncated table 'cron_schedule' with command TRUNCATE TABLE cron_schedule; After this I reindex data and manually ran cron jobs with command bin/magenot cron:run After this I was able to create/save products as normal. ...


0

It's not a common problem and it's can be for different case. The best things will be if you debug. Suppose in my case. vendor/magento/module-deploy/Service/DeployPackage.php $this->deployStaticFile->deployFile() method. As that is on core so i did put try cache and got my solution. For Example : $this->deployStaticFile->deployFile( $...


Top 50 recent answers are included