Magento 2.0 – Fix Custom Module Enabling Error

climagento-2.0magento2module

Download

Today I downloaded the Magento 2.0 Full Release from the Magento website. I downloaded the Full Release with Sample Data (ZIP with sample data) and installed it. I wanted to test if my custom module build in RC-1 was still working however when I tried to enable the module I got an error.

Module installation

When I wanted to install my custom module I noticed the app/code directory disappeared and after a few clicks found that this was moved to the vendor directory. I assumed this was done by composer so decided to add my module to the composer.json in the document root. Running composer update installed the module to the vendor directory.

Error

Tried to enable module by executing the following command from my root directory:

PHP -f bin/magento module:enable --clear-static-content Test_Module

http://devdocs.magento.com/guides/v2.0/extension-dev-guide/enable-module.html

Unfortunately, I get the following error; anyone has an idea what goes wrong?

[InvalidArgumentException]
There are no commands defined in the "module" namespace.

Best Answer

Giving full control (read/write/execute) to var and pub directory solved this issue for me.

sudo chmod -R 777 var pub

Or, you may also try running the command using sudo.

sudo php -f bin/magento module:enable --clear-static-content Test_Module

Related Solutions

Magento 2 – How to Install a Custom Module

Just create the app/code/YourNameSpace/ModuleName folder yourself. Make sure, that your composer.json in the project root contains the line

    "files": [
        "app/etc/NonComposerComponentRegistration.php"
    ]

in the autoload section (see https://github.com/magento/magento2-community-edition/blob/master/composer.json#L42) which is responsible for loading modules which are not installed via composer.

Magento 2 Modules – Where Do Third Party Modules Go?

Preferably 3PLs will live in the vendor directory along with everything else. However… :) We all know there is typically custom code written for almost every custom site-build out there, and this IMO belongs in app/code/ still. Yes, you can still run a module from app/code.

All modules, regardless of location, should have a composer.json and a registration.php file which are used to get the module into the system. You also need the etc/modules.xml file. This is, technically, all it takes to register a module:

$ tree app/code/Alger/
app/code/Alger/
└── Skeleton
    ├── composer.json
    ├── etc
    │   └── module.xml
    └── registration.php

2 directories, 3 files

To get the module up and running, you need to run setup:upgrade and then cache:flush for the system to both recognize and load your new component:

$ bin/magento module:enable Foo_Bar
$ bin/magento setup:upgrade -q && bin/magento cache:flush -q

Update: Two methods to install module from public GitHub repo: https://gist.github.com/davidalger/77761f13d9752b117f35

Related Topic