For the purpose of this example, we’ll make our module in app/code/.
Create a namespace directory – E.g. ‘llapgoch’. Within that should be another directory which is typically the name of the module; for this example we’ll use ‘developertoolbar’. The structure of this folder is quite similar to Magento 1’s module structure.
Within our developertoolbar directory, we need to create a registration.php file which Magento will look for in order to register our module. This would be a rough equivalent of the old module registration stub files back in Magento 1, which in this case would be Llapgoch_Developertoolbar.xml.
Add the following to the registration.php file to tell Magento about our new module:
\Magento\Framework\Component\ComponentRegistrar::register( \Magento\Framework\Component\ComponentRegistrar::MODULE, 'Llapgoch_Developertoolbar', __DIR__ );
The Register Method’s Parameters
- Type– Either MODULE , LIBRARY, LANGUAGE, or THEME which are constants within the ComponentRegistrar class.
- Location – Typically, we’ll use PHP’s magic constant __DIR__ to tell Magento that our module exists in the same place as our registration.php file
Check The Module’s Status
To check Magento can actually see the module, navigate to the bin folder in terminal and run:
Your module should be listed at the bottom, in “List of disabled modules”.
Enable the Module
Run the following from terminal which will enable your module:
./magento module:enable Llapgoch_Developertoolbar
And that’s it! We’ve got a module registered with Magento. Now there’s the task of actually making it do something…