Problem/Motivation

Maybe it's just me, but this link caption threw me off a bit when I first saw it.

From reading it, I assumed that clicking it would actually activate the module I had just installed. But all it does is take you back to the module overview.

If that's its function, then it should probably just be called "Back to modules list" or something similar.

Steps to reproduce

  • Go to the "Add new module" (admin/modules/install) page.
  • Add a module through any of the options on the page and click on the "Continue" button.
  • It will go to another page, where we can see the link.

Proposed resolution

  1. No change.
  2. "Back to modules list" In #48 it is explained why this isn't quite right.
  3. Install newly added module on the extend page
  4. allow users to enable it directly from that screen instead
  5. add your suggestion ..

Remaining tasks

Discuss options

User interface changes

Before
link-text-screenshot

After

API changes

Data model changes

Release notes snippet

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

dawehner’s picture

As drupal core has a string freeze this is probably to late to change, but i agree this is really confusing.

ralf.strobel’s picture

So should we make it 8.x-dev then?

dawehner’s picture

Version: 7.8 » 8.x-dev

Yes, this makes sense.

ralf.strobel’s picture

By the way, as an alternative to changing the text, I would actually like it if the link really did activate the module I just installed.

rpayanm’s picture

Issue summary: View changes
Status: Active » Needs review
FileSize
568 bytes

Changed from "Enable newly added modules" to "Back to modules list".

rpayanm’s picture

Status: Needs review » Reviewed & tested by the community
webchick’s picture

Category: Feature request » Task
Issue tags: +Usability

Yeah, I could see this. However, I believe that text was chosen as a reason, to spur an 'action' so it'd be good for the UX team to sign-off on this.

webchick’s picture

Status: Reviewed & tested by the community » Needs review

Oops.

Bojhan’s picture

Cant we set them to the actual module # on the module page? I think that having an action here makes a lot more sense.

jochem_nl’s picture

I think both arguments are good.

It should be clear to the user to click the link so he/she can enable the modules.
But it also should include something about the page where you end up after clicking the link.

My suggestion is "Back to modules list to enable newly added modules"
It maybe to long.

jochem_nl’s picture

Issue tags: +Amsterdam2014
Bojhan’s picture

Why not just "back to the list"

fragtom’s picture

I have installed Update Manager to see functionality. Would also prefer to shorten the link-text. "Back to modules list"

snte’s picture

going to review it

jochem_nl’s picture

Okay, I agree. I'll make a patch with "Back to modules list"

The last submitted patch, 5: drupal-link-text-misleading-1273676-5.patch, failed testing.

snte’s picture

Can't review #15 because i cannot install a module via Extend, tested locally (DevDesktop) and on simplytest.me, with random modules (ctools, admin_menu, google_analytics). Issue here: https://www.drupal.org/node/2042447

jhedstrom’s picture

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

Probably needs to be bounced to 8.1 since beta is supposed to freeze strings.

Bojhan’s picture

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

Nope, no freezed strings.

ChuChuNaKu’s picture

Assigned: Unassigned » ChuChuNaKu
ChuChuNaKu’s picture

I tested comment number 15 and the patch ran cleanly. However, as comment number 18 stated , I was unable to add a module. I tried installing the date module using drush, but it doesn't display on the Extend page even after clearing the cache.

#SprintWeekend2015

ChuChuNaKu’s picture

Assigned: ChuChuNaKu » Unassigned
mikemiles86’s picture

Issue tags: +SprintWeekend2015

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.

Kumar Kundan’s picture

I have installed path auto module to see functionality. Would also prefer to shorten the link-text. "Back to modules list".

Same Issue with drupal 7 also.

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.

wturrell’s picture

Here's a new patch for 8.2.x

Status: Needs review » Needs work

The last submitted patch, 28: link_text_enable_newly-1273676-28.patch, failed testing.

wturrell’s picture

This is failing because there's a test for the old link text in UpdateUploadTest.php:

$this->assertLink(t('Enable newly added modules'));

I've not changed a test before - do I literally just add that to the patch as well?

(Also, are we still at the stage in the release cycle where this should be against 8.2.x rather than 8.3.x, as it's non-disruptive?)

Thew’s picture

Update the test. This should pass now.

Thew’s picture

Status: Needs work » Needs review

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.

smustgrave’s picture

Version: 9.5.x-dev » 10.1.x-dev
Status: Needs review » Needs work
Issue tags: +Needs Review Queue Initiative, +Needs issue summary update

This issue is being reviewed by the kind folks in Slack, #need-reveiw-queue. We are working to keep the size of Needs Review queue [2700+ issues] to around 400 (1 month or less), following Review a patch or merge require as a guide.

So reading the comments and this seems to be very close.

Patch #31 needs to made for 10.1.x and the issue summary needs updating about what is being fixed actually, to match the patch

Please do not simply just reroll.

ranjith_kumar_k_u’s picture

ranjith_kumar_k_u’s picture

Issue summary: View changes
ranjith_kumar_k_u’s picture

Status: Needs work » Needs review
Asha Nair’s picture

FileSize
21.27 KB
17.79 KB

Applied patch #44 successfully in 10.x. It changes the text to 'Back to modules list'

smustgrave’s picture

Status: Needs review » Needs work

Brought this up in the #ux channel

from @rkoller

i am not sure if i would agree. the current string Enable newly added modules and the new string has two different meanings or call to actions. the current says enable the module that you’ve installed right before and the other says go to the modules page. problem with the current is that it isn’t minding the wording in https://www.drupal.org/project/drupal/issues/2888657 plus it isn't an action link that would actually install the module but just forwarding to the modules page. on the other hand the proposed resolution just states what happens clicking that link that you will go back to the modules page. but it is missing the instruction for the mandatory next step. meaning yes the module got added but a new user might assume that would be enough? Install newly added module on the module page it is a bit long but a bit clearer instruction wise. The call to action is install the newly added module on the module page. and i’ve used singular for added module instead of plural. at least on the screenshot in the issue summary there was just a single module added and i am not sure when a module via the interface if more than module could be added at once?

So think the wording needs some more thought. Leaving Needs issue summary update tag for that new proposal.

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

@ranjith_kumar_k_u, When working on issues it is always helpful to read previous comments and to comment on what you have done and why. Your patch is not accompanied by any explanation or your thoughts on this proposed change. I also see that the comment prior to your reroll has in bold "Please do not simply just reroll." As far as I can tell by the patch and the (very large) screenshots that is what has happened. Therefor, credit has been removed per How is credit granted for Drupal core issues.

@Asha Nair, a second set of screenshots is not at all helpful.

I have updated the Issue Summary. I am setting this to Active because it needs discussion to decide on any text change before a patch is worked on.