Fatal error: Cannot instantiate interface
My magento store is throwing this error:
Fatal error: Cannot instantiate interface MagentoFrameworkViewDesignThemeResolverInterface in /Library/WebServer/Documents/magento/vendor/magento/framework/ObjectManager/Factory/Dynamic/Developer.php on line 73
I don't know why it started to appear. I made no new module installation. The store was working fine.
I've check file permissions and I see no issue there. Also delete the /var/ dir and, I think, all folders/files where created.
[EDIT] The preference is defined vendor/magento/magento2-base/app/etc/di.xml
<preference for="MagentoFrameworkViewDesignThemeResolverInterface" type="MagentoThemeModelThemeResolver" />
magento2 design
edited Nov 27 '15 at 15:44
7ochem
5,72193668
asked Nov 24 '15 at 2:32
Filipe Sá
51129
add a comment |
My magento store is throwing this error:
Fatal error: Cannot instantiate interface MagentoFrameworkViewDesignThemeResolverInterface in /Library/WebServer/Documents/magento/vendor/magento/framework/ObjectManager/Factory/Dynamic/Developer.php on line 73
I don't know why it started to appear. I made no new module installation. The store was working fine.
I've check file permissions and I see no issue there. Also delete the /var/ dir and, I think, all folders/files where created.
[EDIT] The preference is defined vendor/magento/magento2-base/app/etc/di.xml
<preference for="MagentoFrameworkViewDesignThemeResolverInterface" type="MagentoThemeModelThemeResolver" />
magento2 design
edited Nov 27 '15 at 15:44
7ochem
5,72193668
asked Nov 24 '15 at 2:32
Filipe Sá
51129
1
i hope in ur custom module or code your trying to use MagentoFrameworkViewDesignThemeResolverInterface in constructor or object manager
– Pradeep Kumar
Nov 24 '15 at 4:28
@PradeepKumar No. I'm not.
– Filipe Sá
Nov 24 '15 at 14:19
2
clear your cache and the contents ofvar/generation.
– Marius♦
Nov 24 '15 at 14:23
@Marius as stated in the question, I've already removed the /var/* folder completely.
– Filipe Sá
Nov 24 '15 at 14:28
Sorry. I missed that line.
– Marius♦
Nov 24 '15 at 14:44
add a comment |
My magento store is throwing this error:
Fatal error: Cannot instantiate interface MagentoFrameworkViewDesignThemeResolverInterface in /Library/WebServer/Documents/magento/vendor/magento/framework/ObjectManager/Factory/Dynamic/Developer.php on line 73
I don't know why it started to appear. I made no new module installation. The store was working fine.
I've check file permissions and I see no issue there. Also delete the /var/ dir and, I think, all folders/files where created.
[EDIT] The preference is defined vendor/magento/magento2-base/app/etc/di.xml
<preference for="MagentoFrameworkViewDesignThemeResolverInterface" type="MagentoThemeModelThemeResolver" />
magento2 design
edited Nov 27 '15 at 15:44
7ochem
5,72193668
asked Nov 24 '15 at 2:32
Filipe Sá
51129
My magento store is throwing this error:
Fatal error: Cannot instantiate interface MagentoFrameworkViewDesignThemeResolverInterface in /Library/WebServer/Documents/magento/vendor/magento/framework/ObjectManager/Factory/Dynamic/Developer.php on line 73
I don't know why it started to appear. I made no new module installation. The store was working fine.
I've check file permissions and I see no issue there. Also delete the /var/ dir and, I think, all folders/files where created.
[EDIT] The preference is defined vendor/magento/magento2-base/app/etc/di.xml
<preference for="MagentoFrameworkViewDesignThemeResolverInterface" type="MagentoThemeModelThemeResolver" />
magento2 design
magento2 design
edited Nov 27 '15 at 15:44
7ochem
5,72193668
asked Nov 24 '15 at 2:32
Filipe Sá
51129
edited Nov 27 '15 at 15:44
7ochem
5,72193668
asked Nov 24 '15 at 2:32
Filipe Sá
51129
edited Nov 27 '15 at 15:44
7ochem
5,72193668
edited Nov 27 '15 at 15:44
7ochem
5,72193668
edited Nov 27 '15 at 15:44
7ochem
5,72193668
5,72193668
asked Nov 24 '15 at 2:32
Filipe Sá
51129
asked Nov 24 '15 at 2:32
Filipe Sá
51129
asked Nov 24 '15 at 2:32
Filipe Sá
51129
51129
1
i hope in ur custom module or code your trying to use MagentoFrameworkViewDesignThemeResolverInterface in constructor or object manager
– Pradeep Kumar
Nov 24 '15 at 4:28
@PradeepKumar No. I'm not.
– Filipe Sá
Nov 24 '15 at 14:19
2
clear your cache and the contents ofvar/generation.
– Marius♦
Nov 24 '15 at 14:23
@Marius as stated in the question, I've already removed the /var/* folder completely.
– Filipe Sá
Nov 24 '15 at 14:28
Sorry. I missed that line.
– Marius♦
Nov 24 '15 at 14:44
add a comment |
1
i hope in ur custom module or code your trying to use MagentoFrameworkViewDesignThemeResolverInterface in constructor or object manager
– Pradeep Kumar
Nov 24 '15 at 4:28
@PradeepKumar No. I'm not.
– Filipe Sá
Nov 24 '15 at 14:19
2
clear your cache and the contents ofvar/generation.
– Marius♦
Nov 24 '15 at 14:23
@Marius as stated in the question, I've already removed the /var/* folder completely.
– Filipe Sá
Nov 24 '15 at 14:28
Sorry. I missed that line.
– Marius♦
Nov 24 '15 at 14:44
1
1
i hope in ur custom module or code your trying to use MagentoFrameworkViewDesignThemeResolverInterface in constructor or object manager
– Pradeep Kumar
Nov 24 '15 at 4:28
i hope in ur custom module or code your trying to use MagentoFrameworkViewDesignThemeResolverInterface in constructor or object manager
– Pradeep Kumar
Nov 24 '15 at 4:28
@PradeepKumar No. I'm not.
– Filipe Sá
Nov 24 '15 at 14:19
@PradeepKumar No. I'm not.
– Filipe Sá
Nov 24 '15 at 14:19
2
2
clear your cache and the contents of
var/generation.– Marius♦
Nov 24 '15 at 14:23
clear your cache and the contents of
var/generation.– Marius♦
Nov 24 '15 at 14:23
@Marius as stated in the question, I've already removed the /var/* folder completely.
– Filipe Sá
Nov 24 '15 at 14:28
@Marius as stated in the question, I've already removed the /var/* folder completely.
– Filipe Sá
Nov 24 '15 at 14:28
Sorry. I missed that line.
– Marius♦
Nov 24 '15 at 14:44
Sorry. I missed that line.
– Marius♦
Nov 24 '15 at 14:44
add a comment |
6 Answers
6
active
oldest
votes
I had this error and it was solved by clearing the var folder and then running setup:upgrade. If this doesn't solve it then look for errors in di.xml files
answered Apr 11 '16 at 12:19
Claudiu Creanga
4,20512674
worked for me, specificallyvar/cache
– Joshua Soileau
Jul 25 '16 at 17:46
add a comment |
This worked for me :
sudo apt-get install php-intl
sudo service apache2 reload
answered Jun 16 '16 at 12:26
abahet
1211
add a comment |
found answer on git =>
"If you use redis, then first ==> redis-cli then ==> flushall".
P.S. If you also use env e.g. ansible (lxc - server). U'll need to do that command in conteiner. Plus I used next commands : clear var/generation and var/cache, enable Magento modules (bin/magento module:enable --all), compile DI (bin/magento setup:di:compile).
answered Jun 1 '18 at 14:07
Gorr1995
212
add a comment |
In my case, I had to remove a module and I simply deleted the files of the module without following proper methods and then this error was on screen everywhere. After searching much I ended up to replace the files of the module back to same directory and deleted all required folders from var and ran the following commands.
php bin/magento setup:upgrade
php bin/magento setup:static-content:deploy
and all was fixed. I then followed proper ways to remove the module. Hope this saves someones time. :-)
answered Oct 17 '16 at 14:15
MTM
1,89611429
add a comment |
Run following command and check.
rm -rf generated
rm -rf var/*
Worked for me.
answered Oct 28 '18 at 9:47
Kazim Noorani
847523
add a comment |
Clear the cache
rm -rf var/cache
If redis enabled, clear redis db using command line:
$> redis-cli
$> flushall
answered yesterday
Arvind07
8451016
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%2f91294%2ffatal-error-cannot-instantiate-interface%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
6 Answers
6
active
oldest
votes
6 Answers
6
active
oldest
votes
active
oldest
votes
active
oldest
votes
I had this error and it was solved by clearing the var folder and then running setup:upgrade. If this doesn't solve it then look for errors in di.xml files
answered Apr 11 '16 at 12:19
Claudiu Creanga
4,20512674
worked for me, specificallyvar/cache
– Joshua Soileau
Jul 25 '16 at 17:46
add a comment |
I had this error and it was solved by clearing the var folder and then running setup:upgrade. If this doesn't solve it then look for errors in di.xml files
answered Apr 11 '16 at 12:19
Claudiu Creanga
4,20512674
worked for me, specificallyvar/cache
– Joshua Soileau
Jul 25 '16 at 17:46
add a comment |
I had this error and it was solved by clearing the var folder and then running setup:upgrade. If this doesn't solve it then look for errors in di.xml files
answered Apr 11 '16 at 12:19
Claudiu Creanga
4,20512674
I had this error and it was solved by clearing the var folder and then running setup:upgrade. If this doesn't solve it then look for errors in di.xml files
answered Apr 11 '16 at 12:19
Claudiu Creanga
4,20512674
edited Mar 11 '17 at 14:18
answered Apr 11 '16 at 12:19
Claudiu Creanga
4,20512674
answered Apr 11 '16 at 12:19
Claudiu Creanga
4,20512674
answered Apr 11 '16 at 12:19
Claudiu Creanga
4,20512674
4,20512674
worked for me, specificallyvar/cache
– Joshua Soileau
Jul 25 '16 at 17:46
add a comment |
worked for me, specificallyvar/cache
– Joshua Soileau
Jul 25 '16 at 17:46
worked for me, specifically
var/cache– Joshua Soileau
Jul 25 '16 at 17:46
worked for me, specifically
var/cache– Joshua Soileau
Jul 25 '16 at 17:46
add a comment |
This worked for me :
sudo apt-get install php-intl
sudo service apache2 reload
answered Jun 16 '16 at 12:26
abahet
1211
add a comment |
This worked for me :
sudo apt-get install php-intl
sudo service apache2 reload
answered Jun 16 '16 at 12:26
abahet
1211
add a comment |
This worked for me :
sudo apt-get install php-intl
sudo service apache2 reload
answered Jun 16 '16 at 12:26
abahet
1211
This worked for me :
sudo apt-get install php-intl
sudo service apache2 reload
answered Jun 16 '16 at 12:26
abahet
1211
answered Jun 16 '16 at 12:26
abahet
1211
answered Jun 16 '16 at 12:26
abahet
1211
answered Jun 16 '16 at 12:26
abahet
1211
1211
add a comment |
add a comment |
found answer on git =>
"If you use redis, then first ==> redis-cli then ==> flushall".
P.S. If you also use env e.g. ansible (lxc - server). U'll need to do that command in conteiner. Plus I used next commands : clear var/generation and var/cache, enable Magento modules (bin/magento module:enable --all), compile DI (bin/magento setup:di:compile).
answered Jun 1 '18 at 14:07
Gorr1995
212
add a comment |
found answer on git =>
"If you use redis, then first ==> redis-cli then ==> flushall".
P.S. If you also use env e.g. ansible (lxc - server). U'll need to do that command in conteiner. Plus I used next commands : clear var/generation and var/cache, enable Magento modules (bin/magento module:enable --all), compile DI (bin/magento setup:di:compile).
answered Jun 1 '18 at 14:07
Gorr1995
212
add a comment |
found answer on git =>
"If you use redis, then first ==> redis-cli then ==> flushall".
P.S. If you also use env e.g. ansible (lxc - server). U'll need to do that command in conteiner. Plus I used next commands : clear var/generation and var/cache, enable Magento modules (bin/magento module:enable --all), compile DI (bin/magento setup:di:compile).
answered Jun 1 '18 at 14:07
Gorr1995
212
found answer on git =>
"If you use redis, then first ==> redis-cli then ==> flushall".
P.S. If you also use env e.g. ansible (lxc - server). U'll need to do that command in conteiner. Plus I used next commands : clear var/generation and var/cache, enable Magento modules (bin/magento module:enable --all), compile DI (bin/magento setup:di:compile).
answered Jun 1 '18 at 14:07
Gorr1995
212
edited Jun 1 '18 at 14:18
answered Jun 1 '18 at 14:07
Gorr1995
212
answered Jun 1 '18 at 14:07
Gorr1995
212
answered Jun 1 '18 at 14:07
Gorr1995
212
212
add a comment |
add a comment |
In my case, I had to remove a module and I simply deleted the files of the module without following proper methods and then this error was on screen everywhere. After searching much I ended up to replace the files of the module back to same directory and deleted all required folders from var and ran the following commands.
php bin/magento setup:upgrade
php bin/magento setup:static-content:deploy
and all was fixed. I then followed proper ways to remove the module. Hope this saves someones time. :-)
answered Oct 17 '16 at 14:15
MTM
1,89611429
add a comment |
In my case, I had to remove a module and I simply deleted the files of the module without following proper methods and then this error was on screen everywhere. After searching much I ended up to replace the files of the module back to same directory and deleted all required folders from var and ran the following commands.
php bin/magento setup:upgrade
php bin/magento setup:static-content:deploy
and all was fixed. I then followed proper ways to remove the module. Hope this saves someones time. :-)
answered Oct 17 '16 at 14:15
MTM
1,89611429
add a comment |
In my case, I had to remove a module and I simply deleted the files of the module without following proper methods and then this error was on screen everywhere. After searching much I ended up to replace the files of the module back to same directory and deleted all required folders from var and ran the following commands.
php bin/magento setup:upgrade
php bin/magento setup:static-content:deploy
and all was fixed. I then followed proper ways to remove the module. Hope this saves someones time. :-)
answered Oct 17 '16 at 14:15
MTM
1,89611429
In my case, I had to remove a module and I simply deleted the files of the module without following proper methods and then this error was on screen everywhere. After searching much I ended up to replace the files of the module back to same directory and deleted all required folders from var and ran the following commands.
php bin/magento setup:upgrade
php bin/magento setup:static-content:deploy
and all was fixed. I then followed proper ways to remove the module. Hope this saves someones time. :-)
answered Oct 17 '16 at 14:15
MTM
1,89611429
answered Oct 17 '16 at 14:15
MTM
1,89611429
answered Oct 17 '16 at 14:15
MTM
1,89611429
answered Oct 17 '16 at 14:15
MTM
1,89611429
1,89611429
add a comment |
add a comment |
Run following command and check.
rm -rf generated
rm -rf var/*
Worked for me.
answered Oct 28 '18 at 9:47
Kazim Noorani
847523
add a comment |
Run following command and check.
rm -rf generated
rm -rf var/*
Worked for me.
answered Oct 28 '18 at 9:47
Kazim Noorani
847523
add a comment |
Run following command and check.
rm -rf generated
rm -rf var/*
Worked for me.
answered Oct 28 '18 at 9:47
Kazim Noorani
847523
Run following command and check.
rm -rf generated
rm -rf var/*
Worked for me.
answered Oct 28 '18 at 9:47
Kazim Noorani
847523
answered Oct 28 '18 at 9:47
Kazim Noorani
847523
answered Oct 28 '18 at 9:47
Kazim Noorani
847523
answered Oct 28 '18 at 9:47
Kazim Noorani
847523
847523
add a comment |
add a comment |
Clear the cache
rm -rf var/cache
If redis enabled, clear redis db using command line:
$> redis-cli
$> flushall
answered yesterday
Arvind07
8451016
add a comment |
Clear the cache
rm -rf var/cache
If redis enabled, clear redis db using command line:
$> redis-cli
$> flushall
answered yesterday
Arvind07
8451016
add a comment |
Clear the cache
rm -rf var/cache
If redis enabled, clear redis db using command line:
$> redis-cli
$> flushall
answered yesterday
Arvind07
8451016
Clear the cache
rm -rf var/cache
If redis enabled, clear redis db using command line:
$> redis-cli
$> flushall
answered yesterday
Arvind07
8451016
answered yesterday
Arvind07
8451016
answered yesterday
Arvind07
8451016
answered yesterday
Arvind07
8451016
8451016
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%2f91294%2ffatal-error-cannot-instantiate-interface%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
1
i hope in ur custom module or code your trying to use MagentoFrameworkViewDesignThemeResolverInterface in constructor or object manager
– Pradeep Kumar
Nov 24 '15 at 4:28
@PradeepKumar No. I'm not.
– Filipe Sá
Nov 24 '15 at 14:19
2
clear your cache and the contents of
var/generation.– Marius♦
Nov 24 '15 at 14:23
@Marius as stated in the question, I've already removed the /var/* folder completely.
– Filipe Sá
Nov 24 '15 at 14:28
Sorry. I missed that line.
– Marius♦
Nov 24 '15 at 14:44