Add "List content" operation to the content type administration page

Created on 22 June 2016, about 9 years ago
Updated 20 March 2025, 4 months ago

Problem/Motivation

Most areas where we are configuring and then creating structure, like menus and taxonomy vocabularies, have action buttons where we can both make edits to the configuration and list the entries that apply. This doesn’t currently happen with content itself.

Proposed resolution

To place a further secondary action in the action button on each content type, named “List content” which directs the user to admin/content with a filter for the content type already applied. See screenshot as example

Remaining tasks

User interface changes

Adding a further action to the action button as described above.

API changes

none

Data model changes

none

Feature request
Status

Postponed: needs info

Version

11.0 🔥

Component

node system

Created by

🇬🇧United Kingdom rachel_norfolk UK

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇦🇺Australia acbramley

    I'm not actually sure if there's a good way to achieve this. For example, what happens if a user changes the key of the type filter in the Content view? Those links would now be broken.

    As per #50 it doesn't look like we should go with the operation so I'm removing the Needs tests tag since we'd need a new solution.

  • Status changed to Closed: won't fix 15 days ago
  • 🇦🇺Australia acbramley

    Closing this as won't fix based on #50 and #52

    If anyone feels strongly that this should be implemented and has a way around the limitations mentioned, feel free to reopen this.

  • 🇺🇸United States benjifisher Boston area
  • 🇩🇪Germany rkoller Nürnberg, Germany

    xjm credited rkoller .

  • 🇺🇸United States xjm

    For #52, how this works with other types is that there is an entity list handler that provides the link, which is then overridden by the view. If the view is altered to no longer provide the operation, then it would fall back to the basic handler (I think).

    That said, I'm also a bit skeptical of the proposed alternate approach, and of introducing a new pattern just for this; a separate column seems equally problematic to an operation link for me. So (committer hat on) I also agree with the wontfix here, given that there isn't a clear UX win. If we want to close the loop for site administrators on this somehow, we should probably start from scratch with design.

    Adding credits from the usability meeting and for various reviewers and maintainers.

    Thanks everyone!

Production build 0.71.5 2024