UX issues in trash, when many entity types are trashable

Created on 17 February 2025, 22 days ago

Problem/Motivation

When many different entity types are selected in configuration, to be allowed to be trashed, list under /admin/content/trash becomes more difficult to use.

Using Claro admin theme there is long list of tabs above of the lsit of recycled elements.
Using Gin admin theme those tabs became horizontal, and due to lack of space, they are very narrow and hard to read.

Steps to reproduce

1. Enable trash for as many entity types as possibe at /admin/config/content/trash
1. Go to /admin/content/trash and observe long list of tabs
1. Change admin theme to Gin and observe tabs squeezed together horizontally.

Proposed resolution

As the number or entity types can vary between different projects and at complex websites it might be quite big, maybe those tabs should be replaced by one screen for all entity types, with filter above that would allow limiting the results?

Attached example screenshots

🐛 Bug report
Status

Active

Version

3.0

Component

User interface

Created by

🇵🇱Poland besek

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

Merge Requests

Comments & Activities

  • Issue created by @besek
  • 🇷🇴Romania amateescu

    That's an interesting problem, I'll need to think a bit about what we can do to alleviate it.

    Not sure I agree with displaying all trashed entities on a single page, in Add bulk restore function Active I'm trying to change those listings to use views where possible, and views can't work with multiple entity types :/

    In the meantime, I mentioned this issue in #3500162-6: Define how to handle secondary local tasks in entity pages when Navigation Top Bar is enabled , to make folks aware of the possibility of having so many 2nd level tasks when designing the new Navigation Top Bar.

  • 🇵🇱Poland besek

    Thanks for reviewing this issue.

    On the side note: Views for those lists would be great, as this would enable more options to configure how those lists look. But I get why it makes my suggestion not very useful :)

    So, maybe another option: Maybe it could be achieved with the menu? Like taxonomy is, for example?
    So there would be one position "Trash" under content and children menu items with all entity types enabled?

  • 🇷🇴Romania amateescu

    I've been thinking about this problem lately and I think we should add a Compact overview setting that displays the list of trash-enabled entity types in a select element and hides the second-level local tasks.

    Let me know if you can test this a bit and what do you think about it :)

Production build 0.71.5 2024