Problem/Motivation

In d8 locale module is Interface Translation and translation_entity module is Content Translation. So module names are different then module machine names and currently there is no way of getting machine name form modules administration page.

Proposed resolution

Add title attribute to module label so that it shows machine name of the module when it is hovered.

Remaining tasks

Review the patch

User interface changes

When hover on module label it shows module machine name tooltip.
after-0.jpg

API changes

none

#184010: Add #anchors to modules administration page

CommentFileSizeAuthor
#10 Extend___drupal_8_4_0.png24.27 KBxjm
#1 after-0.jpg3.74 KBjibran
system_module-title.patch887 bytesjibran

Comments

jibran’s picture

jibran
he/him
Primary language Urdu
Location Toronto, Canada
commented
StatusFileSize
new after-0.jpg3.74 KB

Added screenshot.

jibran’s picture

jibran
he/him
Primary language Urdu
Location Toronto, Canada
commented
Status: Needs review » Closed (duplicate)

Duplicate of #1734534: Optionally show the machine names on the permission page

salvis’s picture

salvis
he/his
commented

I don't think that other issue is going anywhere because it's too broad.

The new D8 modules page reserves an entire line for

Version: 8.0-dev

Rather than adding a title attribute to the module name, why not add the module machine name to that line? Putting it on the page allows copy&paste.

And while we're at it, why not add the path to the module as well. That would make it much easier to recognize submodules and identify their parent modules, especially when/if we get #1848064-50: Allow to filter modules by arbitrary search strings on the Modules page.

jibran’s picture

jibran
he/him
Primary language Urdu
Location Toronto, Canada
commented
Status: Closed (duplicate) » Active

Making active to discuss the possibilities.

kalabro’s picture

kalabro
she/her
commented

Please, take a look at screenshots from #20 from #1734534: Optionally show the machine names on the permission page.

kalabro’s picture

kalabro
she/her
commented
Issue summary: View changes

Updated issue summary.

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.

jibran’s picture

jibran
he/him
Primary language Urdu
Location Toronto, Canada
commented
Version: 8.2.x-dev » 8.4.x-dev
Issue summary: View changes
Status: Active » Needs review

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

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now 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.

xjm’s picture

xjm
she/her
Primary language English
commented
Issue summary: View changes
Status: Needs review » Closed (won't fix)
StatusFileSize
new Extend___drupal_8_4_0.png24.27 KB

This information is already presented in the detailed module information; I don't think it's a correct use of the title attribute to redundantly add it there as well.

So this is wontfix I think. Thanks!