Problem/Motivation

There is a UI that lets you turn a module/theme on/off. Turning it on adds configuration and often database tables. Turning it off removes content, configuration, and/or database tables. The UI for this should consistently use the verbs "Install" and "Uninstall". Currently it mostly does use these verbs, but it says "Enable" in a few places.

Proposed resolution

The UI for this should consistently use the verbs "Install" and "Uninstall" for turning a module/theme on/off.
Comments and variables.

Fix hook_update_projects_alter() and update.report.inc (and possibly other places) still have references to disabled extensions.

Will mean a lot of data structures passed to/returned from hooks will change, but might just have to be a CR for that - we can check if those hooks are actually implemented in contrib or not.

Remaining tasks

UI changes
Comment changes
Variable changes

User interface changes

More consistent wording.

API changes

N/A

Data model changes

N/A

Release notes snippet

N/A

People to credit

Duplicate issue #2856038: Confusing instructions when installing a theme in D8: Please credit dbjpanda , yogeshmpawar, gaurav.kapoor, cilefen, joelpittet

Comments

Charles Belov created an issue. See original summary.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

gaurav.kapoor’s picture

Status: Active » Needs review
StatusFileSize
new21.04 KB
new915 bytes

I installed Xmlsitemap module and got message 'XMLSitemap has been enabled'. Added a corrective patch.

Status: Needs review » Needs work

The last submitted patch, 3: 2891294-2.patch, failed testing. View results

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

jhodgdon’s picture

FYI -- on the parent issue #2888657: [meta] Less confusing and more consistent wording needed in module/theme add/install/update the Usability team is discussing the UI text for this and about 10 other issues. Until decisions are made, making another patch here would probably be premature.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

jhodgdon’s picture

Issue summary: View changes

We discussed several related UI text issues at the Usability meeting today -- see #2888657-23: [meta] Less confusing and more consistent wording needed in module/theme add/install/update for a summary.

I'm adopting this issue to cover item 2 from that plan:

There is a UI that lets you turn a module/theme on/off. Turning it on adds configuration and often database tables. Turning it off removes content, configuration, and/or database tables. The UI for this should consistently use the verbs "Install" and "Uninstall". Currently it mostly does use these verbs, but it says "Enable" in a few places. This can be fixed in a minor release, as it is only UI text changes.

Updating title and summary accordingly.

jhodgdon’s picture

Title: Clicking Install button results in "enable" message » Use Install/Uninstall consistently for turning modules/themes on/off (not Enable)
Issue summary: View changes

Adding list of people to credit from #2856038: Confusing instructions when installing a theme in D8 which is now a duplicate.

And forgot to update title.

jhodgdon’s picture

Status: Needs work » Postponed

This patch will conflict with #2577407: Action of uploading module/theme files should consistently be called "Add", not "Install", so postponing until that one is done.

jhodgdon’s picture

Issue summary: View changes
Status: Postponed » Active

#2577407: Action of uploading module/theme files should consistently be called "Add", not "Install" has been fixed, so we are no longer using the verb "Install" for the action of adding files for a module/theme to the site. So we can un-postpone this now. The previous patches will not apply any more.

I started looked through the entire core codebase for "enabl" and "disabl" (so that I'd make sure I found "enabling" as well as "enable" "enabled" "enables") and I found a number of spots in the codebase that need to be looked at and/or fixed. Adding them to the issue summary. There are more....

jhodgdon’s picture

This will be a big patch and it will conflict with #3182405: Do not use verb "Install" for things other than turning on modules/themes, so I think we should postpone this issue after all.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

quietone credited Spokje.

quietone’s picture

Issue tags: +Bug Smash Initiative
StatusFileSize
new20.21 KB

Closed #2532652: Make the install and uninstall message the same as a duplicate. Posting the latest MR from there as a patch here. Credit to Manjit.Singh, Spokje, quietone.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

quietone’s picture

Issue summary: View changes
Status: Postponed » Active

This is now active.

In #16 it is said that this will be a big patch and reading the IS I tend to agree. This needs to be split into smaller manageable child issue.

quietone’s picture

Title: Use Install/Uninstall consistently for turning modules/themes on/off (not Enable) » [Meta] Use Install/Uninstall consistently for turning modules/themes on/off (not Enable)
Category: Bug report » Task
Issue summary: View changes

Converting this to a Meta. I've deliberately trimmed down the IS to make it easier to see the child issues and how they have been scoped. The list of changes in the IS was helpful but I would up doing my own searches anyway when making the changes.

ressa’s picture

Should we create a dedicated issue for Documentation as well? For example the pages under https://www.drupal.org/docs/extending-drupal needs updating as well. I have already updated these two pages:

... but there are most likely many more instances of "enable" which should be "install".

longwave’s picture

We have some methods that need renaming too:

+++ b/core/tests/Drupal/KernelTests/KernelTestBase.php
@@ -858,7 +858,7 @@ protected function enableModules(array $modules) {
@@ -884,7 +884,7 @@ protected function disableModules(array $modules) {
quietone’s picture

Issue summary: View changes
quietone’s picture

Issue summary: View changes
quietone’s picture

Issue summary: View changes

More instances to change were found in #3379495-21: Convert enable/disable to install/uninstall in hook_help(). 2 in language_tour_tips_alter and one in system.install. These may need individual issue or a better scope. For example, the tour one might be for all hook_tour_tips_alter. I have added them to the remaining tasks.

quietone’s picture

Issue summary: View changes

longwave found an instance in a test module and I have added that to the list in the issue summary, #3379496-20: Convert enable/disable to install/uninstall in UI not in hook_help.

quietone’s picture

Issue summary: View changes
quietone’s picture

Issue summary: View changes

quietone credited cilefen.

quietone credited dbjpanda.

quietone’s picture

Status: Active » Fixed

This meta was for tracking changes to the UI. All the child issues are now closed. If any more instances are found someone can make a new issue.

The points in #27 and #29 are addressed in the 2 referenced instances. #2888654: URLs for module/theme actions are inconsistent with UI text #3182408: [meta] API function names in module/theme install/uninstall space should match UI

Added created per the Issue Summary and closing as fixed.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

ressa’s picture

Just a tip that a discussion of wording for the install command in the new dr tool is taking place in #3594334: Add a module and theme install command, for those who are interested.

mstrelan’s picture

FWIW the /admin/modules lists dependent modules that are not installed with the "disabled" suffix. This doesn't bother me at all, but if we want to be consistent it should probably say "not installed".

In \Drupal\system\Form\ModulesListForm::buildRow:

$row['#requires'][$dependency] = $modules[$dependency]->status ? $this->t('@module', ['@module' => $name]) : $this->t('@module (<span class="admin-disabled">disabled</span>)', ['@module' => $name]);
ressa’s picture

Thanks for the tip @mstrelan, I think we should be consistent. So I created #3611590: Use Installed and Uninstalled on Available updates page which updates it to "uninstalled". I first went for "not installed", but then saw that the Themes ("Appearances") header is "Uninstalled themes", so maybe it's best to use that as well for modules?

About consistency in the dr issue #3594334: Add a module and theme install command, it seems undecided ... so feel free to weigh in.

ressa’s picture

Ah yes sorry, I added the wrong issue, here's the one I intended to add.