Create a “How To Install” tab with instructions to install and URL/download links.

Comments

raytiley’s picture

raytiley CreditAttribution: raytiley commented
Version: 7.x-dev » 8.x-dev
jefflinwood’s picture

jefflinwood CreditAttribution: jefflinwood commented

We made some observations here:

1) The Modules page lists everything, and is quite overwhelming if all you want to do is install a new module. The "Install a new module" link is there, but it is a little hidden

2) On "Install a new module", this gets really confusing. The sentence:
"You can find modules and themes on drupal.org." has three different links. Why would we install a theme from the "Install a new module" page? Site builders would know that modules aren't themes, even though they might be installed in a similar way.

3) Before clicking "modules" on "Install a new module", the site builder thinks they are going to get a definition of "module", almost like a wikipedia page

4) After clicking "modules", the drupal.org/project/modules page shows up. What is the call-to-action here? The site builder gets 8108 modules that match their search, except they haven't searched yet.

5) Why should the site builder know what version of Drupal they are on (for filter by compatibility), when their Drupal installation knows? This should be pre-selected if they visit from a link from their own site.

6) No call to action to download on individual module pages on drupal.org - download link should be up at top, even if it is just an anchor link that goes to the downloads box

7) Without a strong background in UNIX, site builder will have no idea whether to choose tar.gz or zip for downloading a module. Drupal.org gives no clue that either one is fine, or even to recommend a default.

xjm’s picture

xjm
she/her
Primary language English
CreditAttribution: xjm commented

I'd add to this that the "Install new module" text is a little misleading, and the workflow after using the form needs some work. The form downloads modules; it does not install them (that is, fire hook_install() as happens when the module is first enabled). Furthermore, if the module has already been downloaded, the form throws the error "Module is already installed," yet the user cannot find the module on the "Uninstall" tab because it hasn't actually been installed... just downloaded.

Also, if something goes wrong with a particular module's installation, it is not clear to the user that they just go back to admin/modules rather than using the form at admin/modules/install over and over again. I spent 20 minutes going in circles with someone on IRC who didn't realize all the modules were downloaded even though only one module threw an error and didn't get enabled.

jhedstrom’s picture

jhedstrom
Primary language English
Location Portland, OR
CreditAttribution: jhedstrom at Phase2 commented
Issue summary: View changes
Issue tags: +Needs issue summary update
David_Rothstein’s picture

David_Rothstein CreditAttribution: David_Rothstein as a volunteer commented

I'd add to this that the "Install new module" text is a little misleading, and the workflow after using the form needs some work. The form downloads modules; it does not install them (that is, fire hook_install() as happens when the module is first enabled). Furthermore, if the module has already been downloaded, the form throws the error "Module is already installed," yet the user cannot find the module on the "Uninstall" tab because it hasn't actually been installed... just downloaded.

Made a separate issue for this (with a patch) since I've seen it mentioned several places by several people but there didn't seem to be a dedicated issue anywhere: #2543066: "Install new module" and "Install new theme" links are confusing

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.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.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.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.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.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.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should 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.

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

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should 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.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should 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.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.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.

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

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should 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.

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

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

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

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

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should 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.4.x-dev » 9.5.x-dev

Drupal 9.4.9 was released on December 7, 2022 and is the final full bugfix release for the Drupal 9.4.x series. Drupal 9.4.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.5.x-dev branch from now on, and new development or disruptive changes should 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: 9.5.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.