In this command module_1, module_2 - is a comma-separated list of machine names of the modules you would like to enable. To enable Drupal modules with Drush, run the following command drush pm:enable module_1, module_2 Find the machine name of a module for use in another command or script.Check to see if a module is present in a site's codebase, and wether that module is enabled.To see the list of all available options, refer to the official Drush documentation for this command. Filtering out core modules makes the list more trimmed down, especially on sites with a lot of extensions. Slight differences might sometimes happen when experimental core modules are being released or removed from Drupal core. It's useful since the list of core modules is mostly the same for all Drupal sites that are on the same major version of Drupal core. The -no-core option will filter out all core modules from the list. If you'd like to filter by status you can use the -status option that takes one of two available values: disabled or enabled. Run drush pm:list -type module to get a list of all the modules available on your site.īy default the command returns a list of all extensions, regardless of whether they are enabled or disabled. This allows you to filter the extension by its type: module or theme. The command allows passing in some options. The drush pm:list command allows you to see a list of all available extensions - modules and themes - on your site. If you want to learn more about managing your site with Composer, please refer to the Introduction to Composer for Drupal Users series. ![]() It also allows for easy patching and version management. Managing extensions with Composer is beneficial since it will not only load the extensions themselves but also their dependencies such as additional required libraries and packages. Older tutorials will often refer to the drush pm:download or drush dl command to download a contributed module from. Now Composer is recommended to manage dependencies therefore, the list of pm commands has been reduced, removing some dependency management related commands. In the earlier versions of Drush, prior to Drupal's adoption of Composer for dependency management, the list of pm commands was longer. These commands are part of Drush, in the project manager group, and start with the pm prefix.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |