After installing a new module from the admin panel, it takes to a successful page where we get two option
Next steps

* Enable newly added modules
* Administration pages
Here comes the problem if I choose Enable newly added module it doesn't get added at all.
I have to do it manually, hence there is no point of this feature.

I don't know whether someone else experienced this issue or just me only.

Comments

amc’s picture

Title: After installing new module » Link to enable new module doesn't work
Version: 7.0-rc1 » 7.x-dev

Fixing title to be more descriptive. Can anyone confirm this?

amc’s picture

Component: update system » update.module

And I think this should be changed per #990366: Rename core's "update system" component to "database update system", unless I got them mixed up myself...

bfroehle’s picture

Title: Link to enable new module doesn't work » Link to enable new module confusing

Ciril, I think this is by-design. Some packages might include multiple modules, not all of which you would want to enable. The point of the link is just to take you to the module administration page (where you can then choose to enable the modules).

I'm re-titling this issue as the link text is certainly confusing.

@amc: You're right, it is update.module.

mariusz.slonina’s picture

It is confusing, as well as some other messages, i.e. "Go online" when in maintenance mode, which suggest that, after clicking ,your site will be online, but in fact, you have to check it by self (but it is separate issue). Maybe the simplest solution for that could be changing the text, i.e. "Enable newly added modules on
modules page or go to
administration page" instead of list?

dww’s picture

Priority: Major » Normal
Issue tags: +Usability, +string freeze

Yes, this is a bit confusing, but it's hardly a major bug. See the definitions at http://drupal.org/node/45111 for more on what the priorities mean.

Unfortunately, fixing this now is going to be an uphill battle, since it's probably going to break the string freeze.

Also, tagging as a usability bug to get the UX team's attention.

Cheers,
-Derek

Bojhan’s picture

Status: Active » Closed (works as designed)

Yhea, this works as compromised (not as designed). We cannot fix it this late, the propper fix would be to include a module list like interaction for enabling.

David_Rothstein’s picture

Title: Link to enable new module confusing » Link to enable a new module after adding it via the Update Manager is confusing - allow users to enable it directly from that screen instead
Version: 7.x-dev » 8.0.x-dev
Issue summary: View changes
Status: Closed (works as designed) » Active
Issue tags: +needs backport to D7
Related issues: +#2543066: "Install new module" and "Install new theme" links are confusing

So why not fix this, then?

It seems like what we want is some checkboxes on the final screen with an option for turning the module(s) on. If you submit that it enables them then and there.

In the case of a module that has sub-modules within it, we probably would want the checkboxes unchecked by default (since there's no way to know what they intend to turn on). But for projects that have only module in them, the checkbox could be checked by default.

What about themes - should you have an option to "enable and set as default" here too (in addition to just enabling it)?

See also the related issue I am linking to.

snehi’s picture

Status: Active » Closed (duplicate)

marking it as duplicate of this https://www.drupal.org/node/2577407
Let us resolve over there, that issue is already had 84 comments.

David_Rothstein’s picture

Status: Closed (duplicate) » Active

I think it's not a good idea to expand that issue so much to cover this too - this one is a bit more complicated whereas that's mostly wording changes.

Maybe it could be postponed though.

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.

yoroy’s picture

Issue tags: +ux-workflow

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.