Problem/Motivation

The install system warns me if I try to install an experimental module; I can either continue or cancel. This presents me with a usability issue if I have selected to install both experimental and non-experimental modules at the same time. There is no way to cancel only the experimental installation.

I am marking this as a bug rather than as a feature request because it results in lost work if I prevent the experimental installation.

Steps to reproduce

1. Log in as an administrator
2. Go to /admin/modules
3. Check Content Moderation, Media, Media Library, Responsive Image, Workflows, Help Topics, Content Translation and Language.
4. Click Install.

Expected result:

Experimental modules are provided for testing purposes only. Use at your own risk.
The following module is experimental: Help Topics.
Would you like to continue with the above?

Followed by three buttons (wording can be bikeshedded):

Continue (all)
Continue (nonexperimental only)
Cancel all

Actual result:

Experimental modules are provided for testing purposes only. Use at your own risk.
The following module is experimental: Help Topics.
Would you like to continue with the above?

Followed by two buttons:

Continue
Cancel

5a. Clicking continue installs all modules, including the experimental one.
5b. Clicking cancel cancels the complete installation. None of the boxes that I checked in the previous stop are now checked. I have to redo my decisions about which modules to activate, taking care not to choose the experimental one.

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

Comments

Charles Belov created an issue. See original summary.

charles belov’s picture

charles belov
he/him
Primary language English
Location San Francisco, CA, US
commented
Issue tags: +Usability
cilefen’s picture

cilefen commented
Component: install system » extension system
charles belov’s picture

charles belov
he/him
Primary language English
Location San Francisco, CA, US
commented
Version: 10.1.x-dev » 10.0.x-dev

Version: 10.0.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. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.

nicxvan’s picture

nicxvan commented
Status: Active » Closed (works as designed)

Thank you for raising this issue, I think I'm going to close this works as designed though because I think the decision tree would like be different if the experimental modules are not included.

I think the issue summary meets the bar for credit though so I will grant that.

If you think this warrants more discussion feel free to reopen this!

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.