Enable or disable modules
This command has no prerequisites.
Module status
Use the following command to list enabled and disabled modules:
bin/magento module:status [--enabled] [--disabled] <module-list>
Where
--enabledlists all enabled modules.--disabledlists all disabled modules.<module-list>is a space-delimited list of modules to check the status. If any module name contains special characters, enclose the name in either single or double quotes.
app/etc/config.php file for an environment. See Pro project workflow: Deployment workflow.Module enable, disable
To enable or disable available modules, use the following command:
bin/magento module:enable [-c|--clear-static-content] [-f|--force] [--all] <module-list>
bin/magento module:disable [-c|--clear-static-content] [-f|--force] [--all] <module-list>
Where
-
<module-list>is a space-delimited list of modules to enable or disable. If any module name contains special characters, enclose the name in either single or double quotes. -
--allto enable or disable all modules at the same time. -
-for--forceto force a module to be enabled or disabled despite dependencies. Before you use this option, see About enabling and disabling modules. -
-cor--clear-static-contentcleans generated static view files.Failure to clear static view files might result in issues if there are multiple files with the same name and you do not clear all of them.
In other words, because of the static file fallback rules, if you do not clear static files and there is more than one file named
logo.svgthat are different, fallback might cause the wrong file to display.
For example, to disable the Magento_Weee module, enter:
bin/magento module:disable Magento_Weee
For important information about enabling and disabling modules, see About enabling and disabling modules.
Update the database
If you enabled one or more modules, run the following command to update the database:
bin/magento setup:upgrade
Then clean the cache:
bin/magento cache:clean
About enabling and disabling modules
Adobe Commerce enables you to enable or disable currently available modules; in other words, any Adobe-provided module or any third-party module that is currently available.
Certain modules have dependencies on other modules, in which case you might not be able to enable or disable a module because it has dependencies on other modules.
In addition, there might be conflicting modules that cannot both be enabled at the same time.
Examples:
-
Module A depends on Module B. You cannot disable Module B unless you first disable Module A.
-
Module A depends on Module B, both of which are disabled. You must enable module B before you can enable module A.
-
Module A conflicts with Module B. You can disable Module A and Module B, or you can disable either module but you cannot enable Module A and Module B at the same time.
-
Dependencies are declared in the
requirefield in the Adobe Commercecomposer.jsonfile for each module. Conflicts are declared in theconflictfield in modules’composer.jsonfiles. We use that information to build a dependency graph:A->Bmeans module A depends on module B. -
A dependency chain is the path from a module to another one. For example, if module A depends on module B and module B depends on module C, then the dependency chain is
A->B->C.
If you attempt to enable or disable a module that depends on other modules, the dependency graph displays in the error message.
composer.json declares a conflict with module B but not conversely.Command line only: To force a module to be enabled or disabled regardless of its dependencies, use the optional --force argument.
--force can disable your store and cause problems accessing the Admin.