Magento – Class ‘Magento\Setup\Mvc\Bootstrap\InitParamListener’ not found when running CLI

climagento-2.1

I have a VM running Magento 2 with the sample data that was installed not using composer – I grabbed the latest version from the Magento site). The site itself runs fine, but when I try to run anything for the command line, I get this error:

PHP Fatal error:  Uncaught Error: Class 'Magento\Setup\Mvc\Bootstrap\InitParamListener' not found in /var/www/html/public/setup/config/application.config.php:24
Stack trace:
#0 /var/www/html/public/vendor/magento/framework/Console/Cli.php(57): require()
#1 /var/www/html/public/bin/magento(22): Magento\Framework\Console\Cli->__construct('Magento CLI')
#2 {main}
  thrown in /var/www/html/public/setup/config/application.config.php on line 24

I built the VM on another machine using build scripts, and then used those to build it on this machine, and it worked for a bit, but I suspect I left something out of source control that would be causing this.

Best Answer

I got a very similar issue with the following error;

Zend\ServiceManager\ServiceManager::get was unable to fetch or create an instance for Magento\Setup\Mvc\Bootstrap\InitParamListener

I was able to solve this by deleting the contents of vendor and then re-running composer install

Related Solutions

Magento – Magento 2 module not registering and causing CLI to fail

If you get the error "Decoding failed: Syntax error" I would check the module's composer.json file. For me this has happened a couple of times due to a comma that is not needed inside the require parameters.

If your composer file has this:

"require": {
    "php": "~5.6.0|7.0.2|~7.0.6",
    "magento/module-catalog": "101.0.*",
    "magento/module-checkout": "100.1.*",
},

You will see this error every time. Instead, remove the comma on your last required value. It should now look like this.

"require": {
    "php": "~5.6.0|7.0.2|~7.0.6",
    "magento/module-catalog": "101.0.*",
    "magento/module-checkout": "100.1.*"
},

I haven't tested but this error would probably happen for each parameter if the last value has a comma at the end.

Magento 2.1 PHP Error – Fatal Error: Call to a Member Function setEscapeMessageFlag() on Boolean

This is a known Magento bug:

https://github.com/magento/magento2/issues/4127

Basically if the page lacks page.messages block, it will cause Magento 2 fail with critical error message (dev mode) or white screen of death (production mode). Usually it happens when your layout contains something like this:

<referenceBlock name="page.messages" remove="true"/>

Removing message block is not a good practice anyway, so if you absolutely need to do it, just display empty template file instead.

Best Answer

Related Solutions

Magento – Magento 2 module not registering and causing CLI to fail

Magento 2.1 PHP Error – Fatal Error: Call to a Member Function setEscapeMessageFlag() on Boolean

Related Topic