While it is a usability improvement to be able to show or hide descriptions on the main admin page, it seems confusing to me that this show/hide setting also applies on the subpages 'admin/content', 'admin/build', 'admin/settings', 'admin/user' and 'admin/reports'.

As the main admin page is very crowded, it makes sense to hide descriptions there. The sub-pages on the other hand are less crowded, without descriptions they rather look like a uninspired list of links, and don't provide the information novices need.

Several solutions would be better than the status quo:

  1. To keep the generalized setting, but show the same "show/hide descriptions" link on every admin subpage.
  2. To add a "show/hide descriptions" link with a separate settings on each admin subpage.
  3. To always show descriptions on admin subpages, no matter what the setting is on main admin page.

2 seems to me too complicated, I'd prefer 3, but would also be happy with 1.

CommentFileSizeAuthor
#4 compact-items.patch6.03 KBjbrown

Comments

lilou’s picture

Version: 6.x-dev » 7.x-dev
Component: base system » usability
andypost’s picture

Component: usability » base system
Status: Active » Closed (duplicate)
jbrown’s picture

Title: Usability: Show descriptions on admin sub-listings » 'Hide descriptions' link on admin/config affects other pages
Category: task » bug
Status: Closed (duplicate) » Active

Many pages, e.g. admin/structure are affected by this setting, but it can only be controlled on admin/config .

I say we just make the 'hide descriptions' setting only affect admin/config .

jbrown’s picture

Status: Active » Needs review
StatusFileSize
new6.03 KB
yoroy’s picture

Issue tags: +Usability

I know this has confused me multiple times.

Bojhan’s picture

So how do you hide it on other pages? ie structure?

jbrown’s picture

My patch means that you can't.

The alternative solution would be to have the 'Hide descriptions' link on every page that uses theme_admin_block_content(), but what would be the point of that? Its only required on big complicated pages.

The Structure page has very little content on it as it is.

jbrown’s picture

#4: compact-items.patch queued for re-testing.

moshe weitzman’s picture

I would simply drop the hide/show feature entirely. The link clutters as much as the descriptions it tries to save us from. Just show the descriptions always, and drop the hide/show link. My .02

jbrown’s picture

I agree!

jbrown’s picture

Any consensus on whether the hide/show feature should be removed entirely?

Bojhan’s picture

Not really, I mean as much as moshe is right that the link clutters is at a completely awkward position - we need it to unclutter our interface in the case of many modules.

aspilicious’s picture

Don't drop the option. First time you like the descriptions but after a while you prefer to see as many options as possible without the descriptions.

cartagena’s picture

Thanks, but that's not what I checked--these were checkboxes, not a link. And I specifically checked to hide descriptions on modules and permissions.

yoroy’s picture

Version: 7.x-dev » 8.x-dev

Still weird. Right-aligning the link would unclutter things a lot and make this link consistent with the 'show weights' option for sortable tables, which is also a UI customization feature like this is.

droplet’s picture

Issue tags: +Needs backport to D7

funky behaviour

kscheirer’s picture

#4: compact-items.patch queued for re-testing.

Status: Needs review » Needs work
Issue tags: +Usability, +Needs backport to D7

The last submitted patch, compact-items.patch, failed testing.

c4rl’s picture

The implementation of this functionality has been debatable since its inception, see #72079-62: Patch to give Drupal an overall administration page

As acknowledged way back in 2006(!), this could be implemented purely via JS, which is likely a cleaner, lightweight, and cross-theme solution.

For example, we could use a `compact-invisible` HTML class on elements that should be hidden, then implement visibility via a `compact-mode` class to the <html> tag similar to how we add the `js` class. Then add the compound selector `.compact-mode .compact-invisible` to `.element-invisible` or `.element-hidden`.

Then again, we have much more sophisticated ways of navigating Drupal since 2006, namely toolbars and contextual links; which could be reason to deprecate this feature entirely. Personally, I've never used this in my Drupal career. :)

Is anyone against deprecating? If so, let's convert this to a JS-driven approach.

greggles’s picture

If it stays I would personally vote to keep it affecting all pages. I used that feature for the first time this week and was pleasantly surprised that it affects all pages. However, in general, I would be happier to just remove it. I've never seen anyone use this feature.

steveoliver’s picture

I vote +1 to keep the functionality, but as a js solution and with the toggle somewhere predictable and appropriate on all affected pages.

andypost’s picture

The related issue suggest opposing

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.

chi’s picture

Issue tags: +Accessibility

As this link is controled by JavaScript it behaves like a button. So that it needs to be replaced with button tag.
Anyway I would simply drop it or move to contrib. Never seen anyone using it.

pameeela’s picture

Status: Needs work » Closed (won't fix)
Issue tags: +Bug Smash Initiative

@Chi, can you create a new ticket for the accessibility issue (and there we can decide whether to 'fix' the link or remove it), as the original issue here is quite different.

I am going to close this because the situation has changed quite a bit since and there clearly isn't much support behind this. There is no longer a 'main admin' page and this setting now only applies to admin/config, admin/structure and admin/reports. The Structure page can easily get crowded on a large site so I think it's fine to have it apply there and I don't see any issue with it on Reports either.

(FWIW I vote remove as I have been using Drupal for 10 years and did not know this existed until I found this issue!)