Class 'MagentoSetupMvcBootstrapInitParamListener' not found when running CLI
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 'MagentoSetupMvcBootstrapInitParamListener' 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): MagentoFrameworkConsoleCli->__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.
magento-2.1
bumped to the homepage by Community♦ yesterday
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
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 'MagentoSetupMvcBootstrapInitParamListener' 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): MagentoFrameworkConsoleCli->__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.
magento-2.1
bumped to the homepage by Community♦ yesterday
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
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 'MagentoSetupMvcBootstrapInitParamListener' 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): MagentoFrameworkConsoleCli->__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.
magento-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 'MagentoSetupMvcBootstrapInitParamListener' 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): MagentoFrameworkConsoleCli->__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.
magento-2.1
magento-2.1
asked Feb 11 '17 at 0:26
Laura
2,09011944
2,09011944
bumped to the homepage by Community♦ yesterday
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ yesterday
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
I can see that something is running inside the vendor folder:
#0 /var/www/html/public/vendor/magento/framework/Console/Cli.php(57)
Please, try:
composer self-update && composer update
I did that earlier and it wiped out my magento install. My composer.json only has this: { "repositories": { "magento": { "type": "composer", "url": "repo.magento.com" } } }. I assume that has to do with the fact that I didn't use composer to install Magento?
– Laura
Feb 11 '17 at 4:26
Yes @Laura , probably. Sorry, I did not pay attention to the part of your question that had not used composer.. Got a solution for this?
– Rafael Ortega Bueno
Mar 3 '17 at 17:59
add a comment |
I got a very similar issue with the following error;
ZendServiceManagerServiceManager::get was unable to fetch or create an instance for MagentoSetupMvcBootstrapInitParamListener
I was able to solve this by deleting the contents of vendor
and then re-running composer install
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "479"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f159319%2fclass-magento-setup-mvc-bootstrap-initparamlistener-not-found-when-running-cli%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
I can see that something is running inside the vendor folder:
#0 /var/www/html/public/vendor/magento/framework/Console/Cli.php(57)
Please, try:
composer self-update && composer update
I did that earlier and it wiped out my magento install. My composer.json only has this: { "repositories": { "magento": { "type": "composer", "url": "repo.magento.com" } } }. I assume that has to do with the fact that I didn't use composer to install Magento?
– Laura
Feb 11 '17 at 4:26
Yes @Laura , probably. Sorry, I did not pay attention to the part of your question that had not used composer.. Got a solution for this?
– Rafael Ortega Bueno
Mar 3 '17 at 17:59
add a comment |
I can see that something is running inside the vendor folder:
#0 /var/www/html/public/vendor/magento/framework/Console/Cli.php(57)
Please, try:
composer self-update && composer update
I did that earlier and it wiped out my magento install. My composer.json only has this: { "repositories": { "magento": { "type": "composer", "url": "repo.magento.com" } } }. I assume that has to do with the fact that I didn't use composer to install Magento?
– Laura
Feb 11 '17 at 4:26
Yes @Laura , probably. Sorry, I did not pay attention to the part of your question that had not used composer.. Got a solution for this?
– Rafael Ortega Bueno
Mar 3 '17 at 17:59
add a comment |
I can see that something is running inside the vendor folder:
#0 /var/www/html/public/vendor/magento/framework/Console/Cli.php(57)
Please, try:
composer self-update && composer update
I can see that something is running inside the vendor folder:
#0 /var/www/html/public/vendor/magento/framework/Console/Cli.php(57)
Please, try:
composer self-update && composer update
answered Feb 11 '17 at 0:55
Rafael Ortega Bueno
557313
557313
I did that earlier and it wiped out my magento install. My composer.json only has this: { "repositories": { "magento": { "type": "composer", "url": "repo.magento.com" } } }. I assume that has to do with the fact that I didn't use composer to install Magento?
– Laura
Feb 11 '17 at 4:26
Yes @Laura , probably. Sorry, I did not pay attention to the part of your question that had not used composer.. Got a solution for this?
– Rafael Ortega Bueno
Mar 3 '17 at 17:59
add a comment |
I did that earlier and it wiped out my magento install. My composer.json only has this: { "repositories": { "magento": { "type": "composer", "url": "repo.magento.com" } } }. I assume that has to do with the fact that I didn't use composer to install Magento?
– Laura
Feb 11 '17 at 4:26
Yes @Laura , probably. Sorry, I did not pay attention to the part of your question that had not used composer.. Got a solution for this?
– Rafael Ortega Bueno
Mar 3 '17 at 17:59
I did that earlier and it wiped out my magento install. My composer.json only has this: { "repositories": { "magento": { "type": "composer", "url": "repo.magento.com" } } }. I assume that has to do with the fact that I didn't use composer to install Magento?
– Laura
Feb 11 '17 at 4:26
I did that earlier and it wiped out my magento install. My composer.json only has this: { "repositories": { "magento": { "type": "composer", "url": "repo.magento.com" } } }. I assume that has to do with the fact that I didn't use composer to install Magento?
– Laura
Feb 11 '17 at 4:26
Yes @Laura , probably. Sorry, I did not pay attention to the part of your question that had not used composer.. Got a solution for this?
– Rafael Ortega Bueno
Mar 3 '17 at 17:59
Yes @Laura , probably. Sorry, I did not pay attention to the part of your question that had not used composer.. Got a solution for this?
– Rafael Ortega Bueno
Mar 3 '17 at 17:59
add a comment |
I got a very similar issue with the following error;
ZendServiceManagerServiceManager::get was unable to fetch or create an instance for MagentoSetupMvcBootstrapInitParamListener
I was able to solve this by deleting the contents of vendor
and then re-running composer install
add a comment |
I got a very similar issue with the following error;
ZendServiceManagerServiceManager::get was unable to fetch or create an instance for MagentoSetupMvcBootstrapInitParamListener
I was able to solve this by deleting the contents of vendor
and then re-running composer install
add a comment |
I got a very similar issue with the following error;
ZendServiceManagerServiceManager::get was unable to fetch or create an instance for MagentoSetupMvcBootstrapInitParamListener
I was able to solve this by deleting the contents of vendor
and then re-running composer install
I got a very similar issue with the following error;
ZendServiceManagerServiceManager::get was unable to fetch or create an instance for MagentoSetupMvcBootstrapInitParamListener
I was able to solve this by deleting the contents of vendor
and then re-running composer install
answered Oct 30 '18 at 10:57
ol'bob dole
301217
301217
add a comment |
add a comment |
Thanks for contributing an answer to Magento Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f159319%2fclass-magento-setup-mvc-bootstrap-initparamlistener-not-found-when-running-cli%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown