Add bulk restore function

Created on 14 February 2025, about 2 months ago

Problem/Motivation

Currently, it's really nice to bulk delete/trash entities from the /admin/content view. It would be really nice to have a feature to bulk restore entities from the /admin/content/trash view with checkboxes added to the first column.

✨ Feature request
Status

Active

Version

3.0

Component

Code

Created by

🇨🇦Canada chrisck BC, Canada

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

Comments & Activities

  • Issue created by @chrisck
  • 🇨🇦Canada chrisck BC, Canada
  • anish.ir → made their first commit to this issue’s fork.

  • 🇷🇴Romania amateescu

    I agree that having this feature would be super useful. I'd like to see it implemented in a very specific way if possible, by creating "on-demand" custom views for each trashable entity type. The reason for them being custom is that we need to display different fields than /admin/content for example.

  • Hey @amateescu,

    I’ve attached a screenshot showcasing the functionality I’ve implemented so far. Please have a look and let me know your feedback.

    I also need some clarification regarding the "on-demand custom view" you mentioned. Are you suggesting:

    • Should each trashable entity type have its own predefined View, or should we generate Views dynamically based on the selected entity type?
    • When you say "on-demand," do you mean the Views should be created programmatically when accessed, or should they be predefined and stored permanently?
    • Are there specific fields you'd like displayed for different entity types, or should the View dynamically adjust based on available fields?
    • Or did you have something else in mind?

    Let me know your thoughts! Thanks.

  • 🇷🇴Romania amateescu

    Re #6:

    Should each trashable entity type have its own predefined View, or should we generate Views dynamically based on the selected entity type?

    Generate Views dynamically based on the selected entity type.

    When you say "on-demand," do you mean the Views should be created programmatically when accessed, or should they be predefined and stored permanently?

    Views should be created programmatically when accessed.

    Are there specific fields you'd like displayed for different entity types, or should the View dynamically adjust based on available fields?

    The View dynamically adjust based on available fields, using the list of fields we currently display in the trash controller.

  • 🇮🇳India Vivek Panicker Kolkata

    As anish.ir has not worked on this issue for quite some time, unassigning the issue from him.

Production build 0.71.5 2024