- Sponsor
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
pm:enable should be pm:install #4588
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
+1 we can keep pm:enable as an alias, so there is little cost to doing this. |
Yeah, this is a good proposal ... The docs web page will change url. We could add a redirect plugin for mkdocs if we want to avoid a few 404s. |
I have create PR #5061 I have tested this on local and confirming that below all commands are working fine, as expected.
|
This is an improvement, but for consistency, shouldn't we also add an
|
I created a PR which adds a
|
Describe the bug
In Drupal 8.x and above, there is no longer a way to "enable/disable" modules. Instead we "install/uninstall" them.
However, Drush still has a pm:enable command along with pm:uninstall.
This is confusing (enable is the opposite of uninstall?) and inconsistent with the Drupal UI.
To Reproduce
List commands in Drush and you'll see that pm:enable turns a module on, and pm:uninstall turns it off (which also involves adding/removing configuration, database tables, and/or content).
Expected behavior
The pm:enable command should be named pm:install for consistency with the Drupal UI and with the pm:uninstall command.
System Configuration
Additional information
Drupal core issue about making the Drupal UI more consistent in this area:
https://www.drupal.org/project/drupal/issues/2891294
which is part of a meta issue:
https://www.drupal.org/project/drupal/issues/2888657
The text was updated successfully, but these errors were encountered: