There are no commands defined in the “cache” namespace Unicorn Meta Zoo #1: Why another podcast? Announcing the arrival of Valued Associate #679: Cesar Manaraconfiguration for DB connection is absentI made clone of Magento 2.2.4 Enterprise edition from Integration branch but gives error There are no commands defined in the “cache” namespaceno commands defined in the “setup” namespaceCategory ids, where are they defined in the admin?There are no commands defined in the “setup” namespace : Magento 2Magento 2 - There are no commands defined in the “setup” namespace on windowsWhat are the best practices for Magento CRON (& cache cleaning)?Cache Types are invalidatedThere are no commands defined in the “setup:static-content” namespaceMagento 2: Checkout Success Page not loading if payment option is cash or wire transferMagento 2 admin panel not logged inI made clone of Magento 2.2.4 Enterprise edition from Integration branch but gives error There are no commands defined in the “cache” namespaceSome modules use code versions newer or older than the database. First update the module code, then run 'setup:upgrade'
What is the least dense liquid under normal conditions?
How to open locks without disable device?
What is this word supposed to be?
How to get even lighting when using flash for group photos near wall?
Why does the Cisco show run command not show the full version, while the show version command does?
"My boss was furious with me and I have been fired" vs. "My boss was furious with me and I was fired"
Are there moral objections to a life motivated purely by money? How to sway a person from this lifestyle?
Second order approximation of the loss function (Deep learning book, 7.33)
My bank got bought out, am I now going to have to start filing tax returns in a different state?
How long after the last departure shall the airport stay open for an emergency return?
What to do with someone that cheated their way through university and a PhD program?
A Dictionary or Encyclopedia of Fantasy or Fairy Tales from the 1960s
finding a tangent line to a parabola
Multiple fireplaces in an apartment building?
Retract an already submitted recommendation letter (written for an undergrad student)
c++ diamond problem - How to call base method only once
What's the difference between using dependency injection with a container and using a service locator?
Is Bran literally the world's memory?
What’s with the clanks in Endgame?
Can you stand up from being prone using Skirmisher outside of your turn?
Map material from china not allowed to leave the country
Trumpet valves, lengths, and pitch
Would reducing the reference voltage of an ADC have any effect on accuracy?
Check if a string is entirely made of the same substring
There are no commands defined in the “cache” namespace
Unicorn Meta Zoo #1: Why another podcast?
Announcing the arrival of Valued Associate #679: Cesar Manaraconfiguration for DB connection is absentI made clone of Magento 2.2.4 Enterprise edition from Integration branch but gives error There are no commands defined in the “cache” namespaceno commands defined in the “setup” namespaceCategory ids, where are they defined in the admin?There are no commands defined in the “setup” namespace : Magento 2Magento 2 - There are no commands defined in the “setup” namespace on windowsWhat are the best practices for Magento CRON (& cache cleaning)?Cache Types are invalidatedThere are no commands defined in the “setup:static-content” namespaceMagento 2: Checkout Success Page not loading if payment option is cash or wire transferMagento 2 admin panel not logged inI made clone of Magento 2.2.4 Enterprise edition from Integration branch but gives error There are no commands defined in the “cache” namespaceSome modules use code versions newer or older than the database. First update the module code, then run 'setup:upgrade'
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
Update
Everything is working now but There are no commands defined in the "cache" namespace
is still there. I tried chmod 777 -R var/generation
, didn't fix a thing. AFAIK no module is enabled
public_html]# bin/magento module:status
List of enabled modules:
Nosto_Tagging
List of disabled modules:
Magento_Store
Magento_AdvancedPricingImportExport
Magento_Directory
Magento_Theme
Magento_Backend
Magento_Backup
Magento_Eav
Magento_Customer
Magento_BundleImportExport
Magento_AdminNotification
Magento_CacheInvalidate
Magento_Indexer
Magento_Cms
Magento_CatalogImportExport
Magento_Catalog
Magento_Rule
Magento_Msrp
Magento_Search
Magento_Bundle
Magento_Quote
Magento_CatalogUrlRewrite
Magento_Widget
Magento_SalesSequence
Magento_CheckoutAgreements
Magento_Payment
Magento_Downloadable
Magento_CmsUrlRewrite
Magento_Config
Magento_ConfigurableImportExport
Magento_CatalogInventory
Magento_SampleData
Magento_Contact
Magento_Cookie
Magento_Cron
Magento_CurrencySymbol
Magento_CatalogSearch
Magento_CustomerImportExport
Magento_CustomerSampleData
Magento_Deploy
Magento_Developer
Magento_Dhl
Magento_Authorization
Magento_User
Magento_ImportExport
Magento_Sales
Magento_CatalogRule
Magento_Email
Magento_EncryptionKey
Magento_Fedex
Magento_GiftMessage
Magento_Checkout
Magento_GoogleAnalytics
Magento_GoogleOptimizer
Magento_GroupedImportExport
Magento_GroupedProduct
Magento_Tax
Magento_DownloadableImportExport
Magento_Braintree
Magento_Integration
Magento_LayeredNavigation
Magento_Marketplace
Magento_MediaStorage
Magento_ConfigurableProduct
Magento_MsrpSampleData
Magento_Multishipping
Magento_NewRelicReporting
Magento_Newsletter
Magento_OfflinePayments
Magento_SalesRule
Magento_OfflineShipping
Magento_PageCache
Magento_Captcha
Magento_Paypal
Magento_Persistent
Magento_ProductAlert
Magento_Weee
Magento_ProductVideo
Magento_CatalogSampleData
Magento_Reports
Magento_RequireJs
Magento_Review
Magento_BundleSampleData
Magento_Rss
Magento_DownloadableSampleData
Magento_Authorizenet
Magento_OfflineShippingSampleData
Magento_ConfigurableSampleData
Magento_SalesSampleData
Magento_ProductLinksSampleData
Magento_ThemeSampleData
Magento_ReviewSampleData
Magento_SendFriend
Magento_Ui
Magento_Sitemap
Magento_CatalogRuleConfigurable
Magento_Swagger
Magento_Swatches
Magento_SwatchesSampleData
Magento_GroupedProductSampleData
Magento_TaxImportExport
Magento_TaxSampleData
Magento_GoogleAdwords
Magento_CmsSampleData
Magento_Translation
Magento_Shipping
Magento_Ups
Magento_UrlRewrite
Magento_CatalogRuleSampleData
Magento_Usps
Magento_Variable
Magento_Version
Magento_Webapi
Magento_WebapiSecurity
Magento_SalesRuleSampleData
Magento_CatalogWidget
Magento_WidgetSampleData
Magento_Wishlist
Magento_WishlistSampleData
Sm_BasicProducts
Sm_Categories
Sm_Deals
Sm_ImageSlider
Sm_ListingTabs
Sm_Market
Sm_MegaMenu
Sm_QuickView
The issue was there long before I installed nosto, I initially installed SM quickstart then upgraded it the latest magento version. if I clear the cache from admin area, I see no error. I need to fix it otherwise I'll never be able to install any module or fix this
Update now I disabled nosto.
magento2 admin cache upgrade
|
show 7 more comments
Update
Everything is working now but There are no commands defined in the "cache" namespace
is still there. I tried chmod 777 -R var/generation
, didn't fix a thing. AFAIK no module is enabled
public_html]# bin/magento module:status
List of enabled modules:
Nosto_Tagging
List of disabled modules:
Magento_Store
Magento_AdvancedPricingImportExport
Magento_Directory
Magento_Theme
Magento_Backend
Magento_Backup
Magento_Eav
Magento_Customer
Magento_BundleImportExport
Magento_AdminNotification
Magento_CacheInvalidate
Magento_Indexer
Magento_Cms
Magento_CatalogImportExport
Magento_Catalog
Magento_Rule
Magento_Msrp
Magento_Search
Magento_Bundle
Magento_Quote
Magento_CatalogUrlRewrite
Magento_Widget
Magento_SalesSequence
Magento_CheckoutAgreements
Magento_Payment
Magento_Downloadable
Magento_CmsUrlRewrite
Magento_Config
Magento_ConfigurableImportExport
Magento_CatalogInventory
Magento_SampleData
Magento_Contact
Magento_Cookie
Magento_Cron
Magento_CurrencySymbol
Magento_CatalogSearch
Magento_CustomerImportExport
Magento_CustomerSampleData
Magento_Deploy
Magento_Developer
Magento_Dhl
Magento_Authorization
Magento_User
Magento_ImportExport
Magento_Sales
Magento_CatalogRule
Magento_Email
Magento_EncryptionKey
Magento_Fedex
Magento_GiftMessage
Magento_Checkout
Magento_GoogleAnalytics
Magento_GoogleOptimizer
Magento_GroupedImportExport
Magento_GroupedProduct
Magento_Tax
Magento_DownloadableImportExport
Magento_Braintree
Magento_Integration
Magento_LayeredNavigation
Magento_Marketplace
Magento_MediaStorage
Magento_ConfigurableProduct
Magento_MsrpSampleData
Magento_Multishipping
Magento_NewRelicReporting
Magento_Newsletter
Magento_OfflinePayments
Magento_SalesRule
Magento_OfflineShipping
Magento_PageCache
Magento_Captcha
Magento_Paypal
Magento_Persistent
Magento_ProductAlert
Magento_Weee
Magento_ProductVideo
Magento_CatalogSampleData
Magento_Reports
Magento_RequireJs
Magento_Review
Magento_BundleSampleData
Magento_Rss
Magento_DownloadableSampleData
Magento_Authorizenet
Magento_OfflineShippingSampleData
Magento_ConfigurableSampleData
Magento_SalesSampleData
Magento_ProductLinksSampleData
Magento_ThemeSampleData
Magento_ReviewSampleData
Magento_SendFriend
Magento_Ui
Magento_Sitemap
Magento_CatalogRuleConfigurable
Magento_Swagger
Magento_Swatches
Magento_SwatchesSampleData
Magento_GroupedProductSampleData
Magento_TaxImportExport
Magento_TaxSampleData
Magento_GoogleAdwords
Magento_CmsSampleData
Magento_Translation
Magento_Shipping
Magento_Ups
Magento_UrlRewrite
Magento_CatalogRuleSampleData
Magento_Usps
Magento_Variable
Magento_Version
Magento_Webapi
Magento_WebapiSecurity
Magento_SalesRuleSampleData
Magento_CatalogWidget
Magento_WidgetSampleData
Magento_Wishlist
Magento_WishlistSampleData
Sm_BasicProducts
Sm_Categories
Sm_Deals
Sm_ImageSlider
Sm_ListingTabs
Sm_Market
Sm_MegaMenu
Sm_QuickView
The issue was there long before I installed nosto, I initially installed SM quickstart then upgraded it the latest magento version. if I clear the cache from admin area, I see no error. I need to fix it otherwise I'll never be able to install any module or fix this
Update now I disabled nosto.
magento2 admin cache upgrade
if the images are too big, please remove them and just leave a link to imgur instead
– Lynob
Jun 23 '16 at 21:03
@ProxiBlue no I havent, will try it this weekend and let u know, thanks for the info, i believe your solution will solve it
– Lynob
Jun 27 '16 at 14:09
I have had this issue, or variations of the same, many times whilst coding my first m2 module. In all instances, it was caused by my own code, usualky some issue in the module.xml. Considering that, i would venture some 3rd part moduke is havibg an issue. May need an update. Figure you will have to systematically disable 3rd party modules to find the culprit(s)
– ProxiBlue
Jun 27 '16 at 14:12
Sorry. Accidentalky deleted my comment. So just reposred.
– ProxiBlue
Jun 27 '16 at 14:13
@ProxiBlue thats fine and if a module can cause that then the error is definitely caused by a module since i'm using a custom magento version backed by SM market, it has its own theme and a trillion extension i don't know what for, seems i have to disable them 1 by 1
– Lynob
Jun 27 '16 at 14:17
|
show 7 more comments
Update
Everything is working now but There are no commands defined in the "cache" namespace
is still there. I tried chmod 777 -R var/generation
, didn't fix a thing. AFAIK no module is enabled
public_html]# bin/magento module:status
List of enabled modules:
Nosto_Tagging
List of disabled modules:
Magento_Store
Magento_AdvancedPricingImportExport
Magento_Directory
Magento_Theme
Magento_Backend
Magento_Backup
Magento_Eav
Magento_Customer
Magento_BundleImportExport
Magento_AdminNotification
Magento_CacheInvalidate
Magento_Indexer
Magento_Cms
Magento_CatalogImportExport
Magento_Catalog
Magento_Rule
Magento_Msrp
Magento_Search
Magento_Bundle
Magento_Quote
Magento_CatalogUrlRewrite
Magento_Widget
Magento_SalesSequence
Magento_CheckoutAgreements
Magento_Payment
Magento_Downloadable
Magento_CmsUrlRewrite
Magento_Config
Magento_ConfigurableImportExport
Magento_CatalogInventory
Magento_SampleData
Magento_Contact
Magento_Cookie
Magento_Cron
Magento_CurrencySymbol
Magento_CatalogSearch
Magento_CustomerImportExport
Magento_CustomerSampleData
Magento_Deploy
Magento_Developer
Magento_Dhl
Magento_Authorization
Magento_User
Magento_ImportExport
Magento_Sales
Magento_CatalogRule
Magento_Email
Magento_EncryptionKey
Magento_Fedex
Magento_GiftMessage
Magento_Checkout
Magento_GoogleAnalytics
Magento_GoogleOptimizer
Magento_GroupedImportExport
Magento_GroupedProduct
Magento_Tax
Magento_DownloadableImportExport
Magento_Braintree
Magento_Integration
Magento_LayeredNavigation
Magento_Marketplace
Magento_MediaStorage
Magento_ConfigurableProduct
Magento_MsrpSampleData
Magento_Multishipping
Magento_NewRelicReporting
Magento_Newsletter
Magento_OfflinePayments
Magento_SalesRule
Magento_OfflineShipping
Magento_PageCache
Magento_Captcha
Magento_Paypal
Magento_Persistent
Magento_ProductAlert
Magento_Weee
Magento_ProductVideo
Magento_CatalogSampleData
Magento_Reports
Magento_RequireJs
Magento_Review
Magento_BundleSampleData
Magento_Rss
Magento_DownloadableSampleData
Magento_Authorizenet
Magento_OfflineShippingSampleData
Magento_ConfigurableSampleData
Magento_SalesSampleData
Magento_ProductLinksSampleData
Magento_ThemeSampleData
Magento_ReviewSampleData
Magento_SendFriend
Magento_Ui
Magento_Sitemap
Magento_CatalogRuleConfigurable
Magento_Swagger
Magento_Swatches
Magento_SwatchesSampleData
Magento_GroupedProductSampleData
Magento_TaxImportExport
Magento_TaxSampleData
Magento_GoogleAdwords
Magento_CmsSampleData
Magento_Translation
Magento_Shipping
Magento_Ups
Magento_UrlRewrite
Magento_CatalogRuleSampleData
Magento_Usps
Magento_Variable
Magento_Version
Magento_Webapi
Magento_WebapiSecurity
Magento_SalesRuleSampleData
Magento_CatalogWidget
Magento_WidgetSampleData
Magento_Wishlist
Magento_WishlistSampleData
Sm_BasicProducts
Sm_Categories
Sm_Deals
Sm_ImageSlider
Sm_ListingTabs
Sm_Market
Sm_MegaMenu
Sm_QuickView
The issue was there long before I installed nosto, I initially installed SM quickstart then upgraded it the latest magento version. if I clear the cache from admin area, I see no error. I need to fix it otherwise I'll never be able to install any module or fix this
Update now I disabled nosto.
magento2 admin cache upgrade
Update
Everything is working now but There are no commands defined in the "cache" namespace
is still there. I tried chmod 777 -R var/generation
, didn't fix a thing. AFAIK no module is enabled
public_html]# bin/magento module:status
List of enabled modules:
Nosto_Tagging
List of disabled modules:
Magento_Store
Magento_AdvancedPricingImportExport
Magento_Directory
Magento_Theme
Magento_Backend
Magento_Backup
Magento_Eav
Magento_Customer
Magento_BundleImportExport
Magento_AdminNotification
Magento_CacheInvalidate
Magento_Indexer
Magento_Cms
Magento_CatalogImportExport
Magento_Catalog
Magento_Rule
Magento_Msrp
Magento_Search
Magento_Bundle
Magento_Quote
Magento_CatalogUrlRewrite
Magento_Widget
Magento_SalesSequence
Magento_CheckoutAgreements
Magento_Payment
Magento_Downloadable
Magento_CmsUrlRewrite
Magento_Config
Magento_ConfigurableImportExport
Magento_CatalogInventory
Magento_SampleData
Magento_Contact
Magento_Cookie
Magento_Cron
Magento_CurrencySymbol
Magento_CatalogSearch
Magento_CustomerImportExport
Magento_CustomerSampleData
Magento_Deploy
Magento_Developer
Magento_Dhl
Magento_Authorization
Magento_User
Magento_ImportExport
Magento_Sales
Magento_CatalogRule
Magento_Email
Magento_EncryptionKey
Magento_Fedex
Magento_GiftMessage
Magento_Checkout
Magento_GoogleAnalytics
Magento_GoogleOptimizer
Magento_GroupedImportExport
Magento_GroupedProduct
Magento_Tax
Magento_DownloadableImportExport
Magento_Braintree
Magento_Integration
Magento_LayeredNavigation
Magento_Marketplace
Magento_MediaStorage
Magento_ConfigurableProduct
Magento_MsrpSampleData
Magento_Multishipping
Magento_NewRelicReporting
Magento_Newsletter
Magento_OfflinePayments
Magento_SalesRule
Magento_OfflineShipping
Magento_PageCache
Magento_Captcha
Magento_Paypal
Magento_Persistent
Magento_ProductAlert
Magento_Weee
Magento_ProductVideo
Magento_CatalogSampleData
Magento_Reports
Magento_RequireJs
Magento_Review
Magento_BundleSampleData
Magento_Rss
Magento_DownloadableSampleData
Magento_Authorizenet
Magento_OfflineShippingSampleData
Magento_ConfigurableSampleData
Magento_SalesSampleData
Magento_ProductLinksSampleData
Magento_ThemeSampleData
Magento_ReviewSampleData
Magento_SendFriend
Magento_Ui
Magento_Sitemap
Magento_CatalogRuleConfigurable
Magento_Swagger
Magento_Swatches
Magento_SwatchesSampleData
Magento_GroupedProductSampleData
Magento_TaxImportExport
Magento_TaxSampleData
Magento_GoogleAdwords
Magento_CmsSampleData
Magento_Translation
Magento_Shipping
Magento_Ups
Magento_UrlRewrite
Magento_CatalogRuleSampleData
Magento_Usps
Magento_Variable
Magento_Version
Magento_Webapi
Magento_WebapiSecurity
Magento_SalesRuleSampleData
Magento_CatalogWidget
Magento_WidgetSampleData
Magento_Wishlist
Magento_WishlistSampleData
Sm_BasicProducts
Sm_Categories
Sm_Deals
Sm_ImageSlider
Sm_ListingTabs
Sm_Market
Sm_MegaMenu
Sm_QuickView
The issue was there long before I installed nosto, I initially installed SM quickstart then upgraded it the latest magento version. if I clear the cache from admin area, I see no error. I need to fix it otherwise I'll never be able to install any module or fix this
Update now I disabled nosto.
magento2 admin cache upgrade
magento2 admin cache upgrade
edited Apr 13 '17 at 12:54
Community♦
1
1
asked Jun 23 '16 at 21:01
![](https://i.stack.imgur.com/gkgdd.jpg?s=32&g=1)
![](https://i.stack.imgur.com/gkgdd.jpg?s=32&g=1)
LynobLynob
2072416
2072416
if the images are too big, please remove them and just leave a link to imgur instead
– Lynob
Jun 23 '16 at 21:03
@ProxiBlue no I havent, will try it this weekend and let u know, thanks for the info, i believe your solution will solve it
– Lynob
Jun 27 '16 at 14:09
I have had this issue, or variations of the same, many times whilst coding my first m2 module. In all instances, it was caused by my own code, usualky some issue in the module.xml. Considering that, i would venture some 3rd part moduke is havibg an issue. May need an update. Figure you will have to systematically disable 3rd party modules to find the culprit(s)
– ProxiBlue
Jun 27 '16 at 14:12
Sorry. Accidentalky deleted my comment. So just reposred.
– ProxiBlue
Jun 27 '16 at 14:13
@ProxiBlue thats fine and if a module can cause that then the error is definitely caused by a module since i'm using a custom magento version backed by SM market, it has its own theme and a trillion extension i don't know what for, seems i have to disable them 1 by 1
– Lynob
Jun 27 '16 at 14:17
|
show 7 more comments
if the images are too big, please remove them and just leave a link to imgur instead
– Lynob
Jun 23 '16 at 21:03
@ProxiBlue no I havent, will try it this weekend and let u know, thanks for the info, i believe your solution will solve it
– Lynob
Jun 27 '16 at 14:09
I have had this issue, or variations of the same, many times whilst coding my first m2 module. In all instances, it was caused by my own code, usualky some issue in the module.xml. Considering that, i would venture some 3rd part moduke is havibg an issue. May need an update. Figure you will have to systematically disable 3rd party modules to find the culprit(s)
– ProxiBlue
Jun 27 '16 at 14:12
Sorry. Accidentalky deleted my comment. So just reposred.
– ProxiBlue
Jun 27 '16 at 14:13
@ProxiBlue thats fine and if a module can cause that then the error is definitely caused by a module since i'm using a custom magento version backed by SM market, it has its own theme and a trillion extension i don't know what for, seems i have to disable them 1 by 1
– Lynob
Jun 27 '16 at 14:17
if the images are too big, please remove them and just leave a link to imgur instead
– Lynob
Jun 23 '16 at 21:03
if the images are too big, please remove them and just leave a link to imgur instead
– Lynob
Jun 23 '16 at 21:03
@ProxiBlue no I havent, will try it this weekend and let u know, thanks for the info, i believe your solution will solve it
– Lynob
Jun 27 '16 at 14:09
@ProxiBlue no I havent, will try it this weekend and let u know, thanks for the info, i believe your solution will solve it
– Lynob
Jun 27 '16 at 14:09
I have had this issue, or variations of the same, many times whilst coding my first m2 module. In all instances, it was caused by my own code, usualky some issue in the module.xml. Considering that, i would venture some 3rd part moduke is havibg an issue. May need an update. Figure you will have to systematically disable 3rd party modules to find the culprit(s)
– ProxiBlue
Jun 27 '16 at 14:12
I have had this issue, or variations of the same, many times whilst coding my first m2 module. In all instances, it was caused by my own code, usualky some issue in the module.xml. Considering that, i would venture some 3rd part moduke is havibg an issue. May need an update. Figure you will have to systematically disable 3rd party modules to find the culprit(s)
– ProxiBlue
Jun 27 '16 at 14:12
Sorry. Accidentalky deleted my comment. So just reposred.
– ProxiBlue
Jun 27 '16 at 14:13
Sorry. Accidentalky deleted my comment. So just reposred.
– ProxiBlue
Jun 27 '16 at 14:13
@ProxiBlue thats fine and if a module can cause that then the error is definitely caused by a module since i'm using a custom magento version backed by SM market, it has its own theme and a trillion extension i don't know what for, seems i have to disable them 1 by 1
– Lynob
Jun 27 '16 at 14:17
@ProxiBlue thats fine and if a module can cause that then the error is definitely caused by a module since i'm using a custom magento version backed by SM market, it has its own theme and a trillion extension i don't know what for, seems i have to disable them 1 by 1
– Lynob
Jun 27 '16 at 14:17
|
show 7 more comments
11 Answers
11
active
oldest
votes
That error comes up when a module does not correctly declare its commands. It just stops Magento from correctly reading the wole commands list.
Unless you have broken third party modules, you probably have something left in your cache or generation folder preventing you to correctly run Magento commands.
From your Magento root:
rm -Rf var/cache/*
rm -Rf generated/* (or rm -Rf var/generation/* depending on your Magento version)
Then try again:
php bin/magento cache:flush
If it does not work just try to run:
php bin/magento
And see what is the last shown command.
no it did not work and heres the output ofphp bin/magento
pastebin.com/AknS0gV9
– Lynob
Jun 23 '16 at 23:48
Did you turn on display_errors on CLI?
– Phoenix128_RiccardoT
Jun 24 '16 at 7:31
php -d display_errors bin/magento >log.txt
no strage errors
– Lynob
Jun 24 '16 at 8:07
should i turn it on from php.ini? should i use magento verbose?
– Lynob
Jun 24 '16 at 8:08
Uhm... any 3rd part modules?
– Phoenix128_RiccardoT
Jun 27 '16 at 21:13
|
show 1 more comment
I have gone through the same problem. I have done same as you delete pub/static content but after re-deploying I didn't get the solutions. Again I installed fresh Magento. After some time again I face this issue but this time, I used the best approach. Hope this will work for you :
Use the following command from your magento root directory
Step 1 - sudo rm -rf var/di/* var/generation/* var/cache/* var/page_cache/* var/view_preprocessed/* var/composer_home/cache/*
Step 2 - sudo chmod 777 var -R
Step 3 - sudo chmod 777 pub -R
Step 4 - sudo php bin/magento setup:static-content:deploy
Repeat step 2 & 3.
Please avoid 777 on the production server, but provide read and write permission for Magento.
Thanks Lynob. Please can you paste your error here ?
– Manish
Jun 27 '16 at 14:16
1
same error, the steps didn't fix it, i guess some sort of a custom module is causing the issue
– Lynob
Jun 27 '16 at 14:28
Downvoted for 777 as a solution.
– Vicary
Nov 21 '17 at 18:28
add a comment |
$ bin/magento module:enable --all
This command will generate theapp/etc/config.php
file which contains all installed module and there activation status.
– Cyclonecode
Jan 13 at 16:49
add a comment |
it got same problem . i have been resolve by run this command :
php bin/magento
after done, it display the errors like as "Circular sequence reference ..." . With this errors,we only remove :
in etc/module.xml, because the module name already defined in module tag.
add a comment |
I had this issue once as well. Mine happened because I was doing a clean refresh
php bin/magento setup:upgrade
php bin/magento setup:di:compile
php bin/magento setup:static-content:deploy
php bin/magento indexer:reindex
php bin/magento cache:clean
how I broke mine was I was rushed at work to go home and continue working not completing the steps thinking I could just ssh back into the server and finish. sure enough, I had to clear var/cache/* var/page_cache/* var/di/* var/generation/* and then run the process over again and everything worked fine.
just sharing my experience. hope it helps you in your troubleshooting.
add a comment |
Try this,
- sudo chmod -R 777 var
- sudo chmod -R 777 pub
- sudo php bin/magento setup:upgrade
while this may help giving write permission to anything and everyone is NOT the way to go. Set the permissions correctly so that the correct use can write to these folders.
– Andy
Jul 19 '18 at 8:45
add a comment |
2nd answer after you updated your post:
According to your module:status
output you have all the Magento core modules disabled. I've never seen this and I do not know how your admin is still working!
Anyway open your app/etc/config.php
file and set all the modules starting with Magento_
to 1
.
Example:
...
return array (
'modules' =>
array (
...
'Magento_Store' => 1,
'Magento_AdvancedPricingImportExport' => 1,
'Magento_Directory' => 1,
...
...
After this, from you Magento root run:
rm -Rf var/cache/*
rm -Rf var/generation/*
And try again.
add a comment |
I struggled with this for a while, not finding any information on these forums, until I finally figured it out. I had a 3rd party module that was not properly defined. I had the registration.php
file in place, but I didn't have the etcmodule.xml
file. Instead of gracefully erroring out or ignoring the mis-configured module, it kills the entire Magento engine, including the CLI. I couldn't even run bin/magento module:status
without it throwing the same error.
So, if this happens to you, and all other solutions fail, check that you don't have a misconfigured extension.
add a comment |
I got same issue
[SymfonyComponentConsoleExceptionCommandNotFoundException]
There are no commands defined in the "cache" namespace.
I checked in my source lost file etc/evn.php. Push on source and it be fixed.
add a comment |
I apply all the answer But not work.
Then i start to check my code, in env.php file i found problem there.
So please carefully to apply all the answer .
Check module.xml file of your last installed extension. This error generally because of this file only
– zuber bandi
12 mins ago
add a comment |
Check module.xml file of your last installed extension. This error generally because of this file only
add a comment |
protected by Community♦ Apr 4 '18 at 5:06
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
11 Answers
11
active
oldest
votes
11 Answers
11
active
oldest
votes
active
oldest
votes
active
oldest
votes
That error comes up when a module does not correctly declare its commands. It just stops Magento from correctly reading the wole commands list.
Unless you have broken third party modules, you probably have something left in your cache or generation folder preventing you to correctly run Magento commands.
From your Magento root:
rm -Rf var/cache/*
rm -Rf generated/* (or rm -Rf var/generation/* depending on your Magento version)
Then try again:
php bin/magento cache:flush
If it does not work just try to run:
php bin/magento
And see what is the last shown command.
no it did not work and heres the output ofphp bin/magento
pastebin.com/AknS0gV9
– Lynob
Jun 23 '16 at 23:48
Did you turn on display_errors on CLI?
– Phoenix128_RiccardoT
Jun 24 '16 at 7:31
php -d display_errors bin/magento >log.txt
no strage errors
– Lynob
Jun 24 '16 at 8:07
should i turn it on from php.ini? should i use magento verbose?
– Lynob
Jun 24 '16 at 8:08
Uhm... any 3rd part modules?
– Phoenix128_RiccardoT
Jun 27 '16 at 21:13
|
show 1 more comment
That error comes up when a module does not correctly declare its commands. It just stops Magento from correctly reading the wole commands list.
Unless you have broken third party modules, you probably have something left in your cache or generation folder preventing you to correctly run Magento commands.
From your Magento root:
rm -Rf var/cache/*
rm -Rf generated/* (or rm -Rf var/generation/* depending on your Magento version)
Then try again:
php bin/magento cache:flush
If it does not work just try to run:
php bin/magento
And see what is the last shown command.
no it did not work and heres the output ofphp bin/magento
pastebin.com/AknS0gV9
– Lynob
Jun 23 '16 at 23:48
Did you turn on display_errors on CLI?
– Phoenix128_RiccardoT
Jun 24 '16 at 7:31
php -d display_errors bin/magento >log.txt
no strage errors
– Lynob
Jun 24 '16 at 8:07
should i turn it on from php.ini? should i use magento verbose?
– Lynob
Jun 24 '16 at 8:08
Uhm... any 3rd part modules?
– Phoenix128_RiccardoT
Jun 27 '16 at 21:13
|
show 1 more comment
That error comes up when a module does not correctly declare its commands. It just stops Magento from correctly reading the wole commands list.
Unless you have broken third party modules, you probably have something left in your cache or generation folder preventing you to correctly run Magento commands.
From your Magento root:
rm -Rf var/cache/*
rm -Rf generated/* (or rm -Rf var/generation/* depending on your Magento version)
Then try again:
php bin/magento cache:flush
If it does not work just try to run:
php bin/magento
And see what is the last shown command.
That error comes up when a module does not correctly declare its commands. It just stops Magento from correctly reading the wole commands list.
Unless you have broken third party modules, you probably have something left in your cache or generation folder preventing you to correctly run Magento commands.
From your Magento root:
rm -Rf var/cache/*
rm -Rf generated/* (or rm -Rf var/generation/* depending on your Magento version)
Then try again:
php bin/magento cache:flush
If it does not work just try to run:
php bin/magento
And see what is the last shown command.
edited Nov 9 '18 at 10:21
answered Jun 23 '16 at 21:22
![](https://i.stack.imgur.com/OZo0H.jpg?s=32&g=1)
![](https://i.stack.imgur.com/OZo0H.jpg?s=32&g=1)
Phoenix128_RiccardoTPhoenix128_RiccardoT
5,40721231
5,40721231
no it did not work and heres the output ofphp bin/magento
pastebin.com/AknS0gV9
– Lynob
Jun 23 '16 at 23:48
Did you turn on display_errors on CLI?
– Phoenix128_RiccardoT
Jun 24 '16 at 7:31
php -d display_errors bin/magento >log.txt
no strage errors
– Lynob
Jun 24 '16 at 8:07
should i turn it on from php.ini? should i use magento verbose?
– Lynob
Jun 24 '16 at 8:08
Uhm... any 3rd part modules?
– Phoenix128_RiccardoT
Jun 27 '16 at 21:13
|
show 1 more comment
no it did not work and heres the output ofphp bin/magento
pastebin.com/AknS0gV9
– Lynob
Jun 23 '16 at 23:48
Did you turn on display_errors on CLI?
– Phoenix128_RiccardoT
Jun 24 '16 at 7:31
php -d display_errors bin/magento >log.txt
no strage errors
– Lynob
Jun 24 '16 at 8:07
should i turn it on from php.ini? should i use magento verbose?
– Lynob
Jun 24 '16 at 8:08
Uhm... any 3rd part modules?
– Phoenix128_RiccardoT
Jun 27 '16 at 21:13
no it did not work and heres the output of
php bin/magento
pastebin.com/AknS0gV9– Lynob
Jun 23 '16 at 23:48
no it did not work and heres the output of
php bin/magento
pastebin.com/AknS0gV9– Lynob
Jun 23 '16 at 23:48
Did you turn on display_errors on CLI?
– Phoenix128_RiccardoT
Jun 24 '16 at 7:31
Did you turn on display_errors on CLI?
– Phoenix128_RiccardoT
Jun 24 '16 at 7:31
php -d display_errors bin/magento >log.txt
no strage errors– Lynob
Jun 24 '16 at 8:07
php -d display_errors bin/magento >log.txt
no strage errors– Lynob
Jun 24 '16 at 8:07
should i turn it on from php.ini? should i use magento verbose?
– Lynob
Jun 24 '16 at 8:08
should i turn it on from php.ini? should i use magento verbose?
– Lynob
Jun 24 '16 at 8:08
Uhm... any 3rd part modules?
– Phoenix128_RiccardoT
Jun 27 '16 at 21:13
Uhm... any 3rd part modules?
– Phoenix128_RiccardoT
Jun 27 '16 at 21:13
|
show 1 more comment
I have gone through the same problem. I have done same as you delete pub/static content but after re-deploying I didn't get the solutions. Again I installed fresh Magento. After some time again I face this issue but this time, I used the best approach. Hope this will work for you :
Use the following command from your magento root directory
Step 1 - sudo rm -rf var/di/* var/generation/* var/cache/* var/page_cache/* var/view_preprocessed/* var/composer_home/cache/*
Step 2 - sudo chmod 777 var -R
Step 3 - sudo chmod 777 pub -R
Step 4 - sudo php bin/magento setup:static-content:deploy
Repeat step 2 & 3.
Please avoid 777 on the production server, but provide read and write permission for Magento.
Thanks Lynob. Please can you paste your error here ?
– Manish
Jun 27 '16 at 14:16
1
same error, the steps didn't fix it, i guess some sort of a custom module is causing the issue
– Lynob
Jun 27 '16 at 14:28
Downvoted for 777 as a solution.
– Vicary
Nov 21 '17 at 18:28
add a comment |
I have gone through the same problem. I have done same as you delete pub/static content but after re-deploying I didn't get the solutions. Again I installed fresh Magento. After some time again I face this issue but this time, I used the best approach. Hope this will work for you :
Use the following command from your magento root directory
Step 1 - sudo rm -rf var/di/* var/generation/* var/cache/* var/page_cache/* var/view_preprocessed/* var/composer_home/cache/*
Step 2 - sudo chmod 777 var -R
Step 3 - sudo chmod 777 pub -R
Step 4 - sudo php bin/magento setup:static-content:deploy
Repeat step 2 & 3.
Please avoid 777 on the production server, but provide read and write permission for Magento.
Thanks Lynob. Please can you paste your error here ?
– Manish
Jun 27 '16 at 14:16
1
same error, the steps didn't fix it, i guess some sort of a custom module is causing the issue
– Lynob
Jun 27 '16 at 14:28
Downvoted for 777 as a solution.
– Vicary
Nov 21 '17 at 18:28
add a comment |
I have gone through the same problem. I have done same as you delete pub/static content but after re-deploying I didn't get the solutions. Again I installed fresh Magento. After some time again I face this issue but this time, I used the best approach. Hope this will work for you :
Use the following command from your magento root directory
Step 1 - sudo rm -rf var/di/* var/generation/* var/cache/* var/page_cache/* var/view_preprocessed/* var/composer_home/cache/*
Step 2 - sudo chmod 777 var -R
Step 3 - sudo chmod 777 pub -R
Step 4 - sudo php bin/magento setup:static-content:deploy
Repeat step 2 & 3.
Please avoid 777 on the production server, but provide read and write permission for Magento.
I have gone through the same problem. I have done same as you delete pub/static content but after re-deploying I didn't get the solutions. Again I installed fresh Magento. After some time again I face this issue but this time, I used the best approach. Hope this will work for you :
Use the following command from your magento root directory
Step 1 - sudo rm -rf var/di/* var/generation/* var/cache/* var/page_cache/* var/view_preprocessed/* var/composer_home/cache/*
Step 2 - sudo chmod 777 var -R
Step 3 - sudo chmod 777 pub -R
Step 4 - sudo php bin/magento setup:static-content:deploy
Repeat step 2 & 3.
Please avoid 777 on the production server, but provide read and write permission for Magento.
edited Nov 22 '17 at 7:27
answered Jun 27 '16 at 13:41
![](https://i.stack.imgur.com/O4HVa.jpg?s=32&g=1)
![](https://i.stack.imgur.com/O4HVa.jpg?s=32&g=1)
ManishManish
2,02931840
2,02931840
Thanks Lynob. Please can you paste your error here ?
– Manish
Jun 27 '16 at 14:16
1
same error, the steps didn't fix it, i guess some sort of a custom module is causing the issue
– Lynob
Jun 27 '16 at 14:28
Downvoted for 777 as a solution.
– Vicary
Nov 21 '17 at 18:28
add a comment |
Thanks Lynob. Please can you paste your error here ?
– Manish
Jun 27 '16 at 14:16
1
same error, the steps didn't fix it, i guess some sort of a custom module is causing the issue
– Lynob
Jun 27 '16 at 14:28
Downvoted for 777 as a solution.
– Vicary
Nov 21 '17 at 18:28
Thanks Lynob. Please can you paste your error here ?
– Manish
Jun 27 '16 at 14:16
Thanks Lynob. Please can you paste your error here ?
– Manish
Jun 27 '16 at 14:16
1
1
same error, the steps didn't fix it, i guess some sort of a custom module is causing the issue
– Lynob
Jun 27 '16 at 14:28
same error, the steps didn't fix it, i guess some sort of a custom module is causing the issue
– Lynob
Jun 27 '16 at 14:28
Downvoted for 777 as a solution.
– Vicary
Nov 21 '17 at 18:28
Downvoted for 777 as a solution.
– Vicary
Nov 21 '17 at 18:28
add a comment |
$ bin/magento module:enable --all
This command will generate theapp/etc/config.php
file which contains all installed module and there activation status.
– Cyclonecode
Jan 13 at 16:49
add a comment |
$ bin/magento module:enable --all
This command will generate theapp/etc/config.php
file which contains all installed module and there activation status.
– Cyclonecode
Jan 13 at 16:49
add a comment |
$ bin/magento module:enable --all
$ bin/magento module:enable --all
answered Nov 7 '16 at 12:38
muhsinmuhsin
12113
12113
This command will generate theapp/etc/config.php
file which contains all installed module and there activation status.
– Cyclonecode
Jan 13 at 16:49
add a comment |
This command will generate theapp/etc/config.php
file which contains all installed module and there activation status.
– Cyclonecode
Jan 13 at 16:49
This command will generate the
app/etc/config.php
file which contains all installed module and there activation status.– Cyclonecode
Jan 13 at 16:49
This command will generate the
app/etc/config.php
file which contains all installed module and there activation status.– Cyclonecode
Jan 13 at 16:49
add a comment |
it got same problem . i have been resolve by run this command :
php bin/magento
after done, it display the errors like as "Circular sequence reference ..." . With this errors,we only remove :
in etc/module.xml, because the module name already defined in module tag.
add a comment |
it got same problem . i have been resolve by run this command :
php bin/magento
after done, it display the errors like as "Circular sequence reference ..." . With this errors,we only remove :
in etc/module.xml, because the module name already defined in module tag.
add a comment |
it got same problem . i have been resolve by run this command :
php bin/magento
after done, it display the errors like as "Circular sequence reference ..." . With this errors,we only remove :
in etc/module.xml, because the module name already defined in module tag.
it got same problem . i have been resolve by run this command :
php bin/magento
after done, it display the errors like as "Circular sequence reference ..." . With this errors,we only remove :
in etc/module.xml, because the module name already defined in module tag.
edited Jan 30 at 10:40
![](https://i.stack.imgur.com/qUGVv.jpg?s=32&g=1)
![](https://i.stack.imgur.com/qUGVv.jpg?s=32&g=1)
Teja Bhagavan Kollepara
2,99241950
2,99241950
answered Oct 12 '16 at 3:34
![](https://i.stack.imgur.com/VabCZ.png?s=32&g=1)
![](https://i.stack.imgur.com/VabCZ.png?s=32&g=1)
Vu AnhVu Anh
78669
78669
add a comment |
add a comment |
I had this issue once as well. Mine happened because I was doing a clean refresh
php bin/magento setup:upgrade
php bin/magento setup:di:compile
php bin/magento setup:static-content:deploy
php bin/magento indexer:reindex
php bin/magento cache:clean
how I broke mine was I was rushed at work to go home and continue working not completing the steps thinking I could just ssh back into the server and finish. sure enough, I had to clear var/cache/* var/page_cache/* var/di/* var/generation/* and then run the process over again and everything worked fine.
just sharing my experience. hope it helps you in your troubleshooting.
add a comment |
I had this issue once as well. Mine happened because I was doing a clean refresh
php bin/magento setup:upgrade
php bin/magento setup:di:compile
php bin/magento setup:static-content:deploy
php bin/magento indexer:reindex
php bin/magento cache:clean
how I broke mine was I was rushed at work to go home and continue working not completing the steps thinking I could just ssh back into the server and finish. sure enough, I had to clear var/cache/* var/page_cache/* var/di/* var/generation/* and then run the process over again and everything worked fine.
just sharing my experience. hope it helps you in your troubleshooting.
add a comment |
I had this issue once as well. Mine happened because I was doing a clean refresh
php bin/magento setup:upgrade
php bin/magento setup:di:compile
php bin/magento setup:static-content:deploy
php bin/magento indexer:reindex
php bin/magento cache:clean
how I broke mine was I was rushed at work to go home and continue working not completing the steps thinking I could just ssh back into the server and finish. sure enough, I had to clear var/cache/* var/page_cache/* var/di/* var/generation/* and then run the process over again and everything worked fine.
just sharing my experience. hope it helps you in your troubleshooting.
I had this issue once as well. Mine happened because I was doing a clean refresh
php bin/magento setup:upgrade
php bin/magento setup:di:compile
php bin/magento setup:static-content:deploy
php bin/magento indexer:reindex
php bin/magento cache:clean
how I broke mine was I was rushed at work to go home and continue working not completing the steps thinking I could just ssh back into the server and finish. sure enough, I had to clear var/cache/* var/page_cache/* var/di/* var/generation/* and then run the process over again and everything worked fine.
just sharing my experience. hope it helps you in your troubleshooting.
answered Sep 21 '17 at 1:55
gx2ggx2g
9310
9310
add a comment |
add a comment |
Try this,
- sudo chmod -R 777 var
- sudo chmod -R 777 pub
- sudo php bin/magento setup:upgrade
while this may help giving write permission to anything and everyone is NOT the way to go. Set the permissions correctly so that the correct use can write to these folders.
– Andy
Jul 19 '18 at 8:45
add a comment |
Try this,
- sudo chmod -R 777 var
- sudo chmod -R 777 pub
- sudo php bin/magento setup:upgrade
while this may help giving write permission to anything and everyone is NOT the way to go. Set the permissions correctly so that the correct use can write to these folders.
– Andy
Jul 19 '18 at 8:45
add a comment |
Try this,
- sudo chmod -R 777 var
- sudo chmod -R 777 pub
- sudo php bin/magento setup:upgrade
Try this,
- sudo chmod -R 777 var
- sudo chmod -R 777 pub
- sudo php bin/magento setup:upgrade
answered Oct 12 '16 at 4:14
SukeshiniSukeshini
6,5851457115
6,5851457115
while this may help giving write permission to anything and everyone is NOT the way to go. Set the permissions correctly so that the correct use can write to these folders.
– Andy
Jul 19 '18 at 8:45
add a comment |
while this may help giving write permission to anything and everyone is NOT the way to go. Set the permissions correctly so that the correct use can write to these folders.
– Andy
Jul 19 '18 at 8:45
while this may help giving write permission to anything and everyone is NOT the way to go. Set the permissions correctly so that the correct use can write to these folders.
– Andy
Jul 19 '18 at 8:45
while this may help giving write permission to anything and everyone is NOT the way to go. Set the permissions correctly so that the correct use can write to these folders.
– Andy
Jul 19 '18 at 8:45
add a comment |
2nd answer after you updated your post:
According to your module:status
output you have all the Magento core modules disabled. I've never seen this and I do not know how your admin is still working!
Anyway open your app/etc/config.php
file and set all the modules starting with Magento_
to 1
.
Example:
...
return array (
'modules' =>
array (
...
'Magento_Store' => 1,
'Magento_AdvancedPricingImportExport' => 1,
'Magento_Directory' => 1,
...
...
After this, from you Magento root run:
rm -Rf var/cache/*
rm -Rf var/generation/*
And try again.
add a comment |
2nd answer after you updated your post:
According to your module:status
output you have all the Magento core modules disabled. I've never seen this and I do not know how your admin is still working!
Anyway open your app/etc/config.php
file and set all the modules starting with Magento_
to 1
.
Example:
...
return array (
'modules' =>
array (
...
'Magento_Store' => 1,
'Magento_AdvancedPricingImportExport' => 1,
'Magento_Directory' => 1,
...
...
After this, from you Magento root run:
rm -Rf var/cache/*
rm -Rf var/generation/*
And try again.
add a comment |
2nd answer after you updated your post:
According to your module:status
output you have all the Magento core modules disabled. I've never seen this and I do not know how your admin is still working!
Anyway open your app/etc/config.php
file and set all the modules starting with Magento_
to 1
.
Example:
...
return array (
'modules' =>
array (
...
'Magento_Store' => 1,
'Magento_AdvancedPricingImportExport' => 1,
'Magento_Directory' => 1,
...
...
After this, from you Magento root run:
rm -Rf var/cache/*
rm -Rf var/generation/*
And try again.
2nd answer after you updated your post:
According to your module:status
output you have all the Magento core modules disabled. I've never seen this and I do not know how your admin is still working!
Anyway open your app/etc/config.php
file and set all the modules starting with Magento_
to 1
.
Example:
...
return array (
'modules' =>
array (
...
'Magento_Store' => 1,
'Magento_AdvancedPricingImportExport' => 1,
'Magento_Directory' => 1,
...
...
After this, from you Magento root run:
rm -Rf var/cache/*
rm -Rf var/generation/*
And try again.
answered Jul 5 '16 at 15:17
![](https://i.stack.imgur.com/OZo0H.jpg?s=32&g=1)
![](https://i.stack.imgur.com/OZo0H.jpg?s=32&g=1)
Phoenix128_RiccardoTPhoenix128_RiccardoT
5,40721231
5,40721231
add a comment |
add a comment |
I struggled with this for a while, not finding any information on these forums, until I finally figured it out. I had a 3rd party module that was not properly defined. I had the registration.php
file in place, but I didn't have the etcmodule.xml
file. Instead of gracefully erroring out or ignoring the mis-configured module, it kills the entire Magento engine, including the CLI. I couldn't even run bin/magento module:status
without it throwing the same error.
So, if this happens to you, and all other solutions fail, check that you don't have a misconfigured extension.
add a comment |
I struggled with this for a while, not finding any information on these forums, until I finally figured it out. I had a 3rd party module that was not properly defined. I had the registration.php
file in place, but I didn't have the etcmodule.xml
file. Instead of gracefully erroring out or ignoring the mis-configured module, it kills the entire Magento engine, including the CLI. I couldn't even run bin/magento module:status
without it throwing the same error.
So, if this happens to you, and all other solutions fail, check that you don't have a misconfigured extension.
add a comment |
I struggled with this for a while, not finding any information on these forums, until I finally figured it out. I had a 3rd party module that was not properly defined. I had the registration.php
file in place, but I didn't have the etcmodule.xml
file. Instead of gracefully erroring out or ignoring the mis-configured module, it kills the entire Magento engine, including the CLI. I couldn't even run bin/magento module:status
without it throwing the same error.
So, if this happens to you, and all other solutions fail, check that you don't have a misconfigured extension.
I struggled with this for a while, not finding any information on these forums, until I finally figured it out. I had a 3rd party module that was not properly defined. I had the registration.php
file in place, but I didn't have the etcmodule.xml
file. Instead of gracefully erroring out or ignoring the mis-configured module, it kills the entire Magento engine, including the CLI. I couldn't even run bin/magento module:status
without it throwing the same error.
So, if this happens to you, and all other solutions fail, check that you don't have a misconfigured extension.
answered Jun 1 '18 at 21:43
BrianVPSBrianVPS
348214
348214
add a comment |
add a comment |
I got same issue
[SymfonyComponentConsoleExceptionCommandNotFoundException]
There are no commands defined in the "cache" namespace.
I checked in my source lost file etc/evn.php. Push on source and it be fixed.
add a comment |
I got same issue
[SymfonyComponentConsoleExceptionCommandNotFoundException]
There are no commands defined in the "cache" namespace.
I checked in my source lost file etc/evn.php. Push on source and it be fixed.
add a comment |
I got same issue
[SymfonyComponentConsoleExceptionCommandNotFoundException]
There are no commands defined in the "cache" namespace.
I checked in my source lost file etc/evn.php. Push on source and it be fixed.
I got same issue
[SymfonyComponentConsoleExceptionCommandNotFoundException]
There are no commands defined in the "cache" namespace.
I checked in my source lost file etc/evn.php. Push on source and it be fixed.
answered Dec 3 '18 at 19:41
![](https://i.stack.imgur.com/Rwejt.jpg?s=32&g=1)
![](https://i.stack.imgur.com/Rwejt.jpg?s=32&g=1)
xankaxanka
1,03331950
1,03331950
add a comment |
add a comment |
I apply all the answer But not work.
Then i start to check my code, in env.php file i found problem there.
So please carefully to apply all the answer .
Check module.xml file of your last installed extension. This error generally because of this file only
– zuber bandi
12 mins ago
add a comment |
I apply all the answer But not work.
Then i start to check my code, in env.php file i found problem there.
So please carefully to apply all the answer .
Check module.xml file of your last installed extension. This error generally because of this file only
– zuber bandi
12 mins ago
add a comment |
I apply all the answer But not work.
Then i start to check my code, in env.php file i found problem there.
So please carefully to apply all the answer .
I apply all the answer But not work.
Then i start to check my code, in env.php file i found problem there.
So please carefully to apply all the answer .
answered Mar 11 at 10:31
![](https://lh6.googleusercontent.com/-MP-pDnSbcVU/AAAAAAAAAAI/AAAAAAAABB8/SuEzF74mBdU/photo.jpg?sz=32)
![](https://lh6.googleusercontent.com/-MP-pDnSbcVU/AAAAAAAAAAI/AAAAAAAABB8/SuEzF74mBdU/photo.jpg?sz=32)
HaFiz UmerHaFiz Umer
45811
45811
Check module.xml file of your last installed extension. This error generally because of this file only
– zuber bandi
12 mins ago
add a comment |
Check module.xml file of your last installed extension. This error generally because of this file only
– zuber bandi
12 mins ago
Check module.xml file of your last installed extension. This error generally because of this file only
– zuber bandi
12 mins ago
Check module.xml file of your last installed extension. This error generally because of this file only
– zuber bandi
12 mins ago
add a comment |
Check module.xml file of your last installed extension. This error generally because of this file only
add a comment |
Check module.xml file of your last installed extension. This error generally because of this file only
add a comment |
Check module.xml file of your last installed extension. This error generally because of this file only
Check module.xml file of your last installed extension. This error generally because of this file only
answered 12 mins ago
![](https://i.stack.imgur.com/swBpP.gif?s=32&g=1)
![](https://i.stack.imgur.com/swBpP.gif?s=32&g=1)
zuber bandizuber bandi
15415
15415
add a comment |
add a comment |
protected by Community♦ Apr 4 '18 at 5:06
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
if the images are too big, please remove them and just leave a link to imgur instead
– Lynob
Jun 23 '16 at 21:03
@ProxiBlue no I havent, will try it this weekend and let u know, thanks for the info, i believe your solution will solve it
– Lynob
Jun 27 '16 at 14:09
I have had this issue, or variations of the same, many times whilst coding my first m2 module. In all instances, it was caused by my own code, usualky some issue in the module.xml. Considering that, i would venture some 3rd part moduke is havibg an issue. May need an update. Figure you will have to systematically disable 3rd party modules to find the culprit(s)
– ProxiBlue
Jun 27 '16 at 14:12
Sorry. Accidentalky deleted my comment. So just reposred.
– ProxiBlue
Jun 27 '16 at 14:13
@ProxiBlue thats fine and if a module can cause that then the error is definitely caused by a module since i'm using a custom magento version backed by SM market, it has its own theme and a trillion extension i don't know what for, seems i have to disable them 1 by 1
– Lynob
Jun 27 '16 at 14:17