- 🇳🇿New Zealand quietone
All the child issue but one are completed here. By convention we can close issues when there is only one child left. I am moving the child issue to the newly added parent and closing this issue.
We have about 10 related Usability issues (see Child issues in the sidebar) around the area of the functionality that lets you add a new contrib or custom module/theme from the UI, and the wording on the screens/buttons for this process. Here's how it works currently for modules (themes are similar):
Download additional contributed modules to extend your site's functionality.
Regularly review and install available updates to maintain a secure and current site. Always run the update script each time a module is updated.
+Install new module (button)
(see previous top screenshot)
Installation was completed successfully.
Installed [module name] successfully
Enable newly added modules
Install another module
All of these messages are confusing. When you click the Enable link, it doesn't enable the module, but only takes you back to admin/modules (where you can find the module in the list and Install it, not Enable it), and as noted above, using the word "install" for what just happened is confusing anyway.
Module [module name] has been enabled.
(emphasis added). You just clicked Install so it should say Installed.
There are some other usability issues on the Extend and Appearance pages that are probably out of scope for this issue, but are somewhat related:
From comment #23 and #3178030: Drupal Usability Meeting 2020-11-13 → :
We can fix up the wording in the UI for module/theme add/install/uninstall as follows, divided up into 5 phases of fixes that we could actually get done, each in its own issue. Here is a list of what we decided should be done now, with anything else currently listed in the Problem section above being out of scope for this meta issue:
We also noted that at the Composer command line, the verb for this action is "require", but we don't want to use that in the UI inside Drupal. There is no Drush command for doing this.
We also noted that the Drush commands use the verbs "enable"/"uninstall"; we should probably see if we can get Drush to be more consistent in its use of these verbs too. Created issue:
https://github.com/drush-ops/drush/issues/4588
a) [Done!]
b) Fix each child issue.
Better and less confusing UI for adding a new module/theme to the system, turning it on, and/or updating it (on child issues).
API function names will change to match the UI (on a child issue).
None.
Not on this meta issue.
Fixed
11.0 🔥
user interface text
Makes Drupal easier to use. Preferred over UX, D7UX, etc.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
All the child issue but one are completed here. By convention we can close issues when there is only one child left. I am moving the child issue to the newly added parent and closing this issue.