Note: This issue is part of #2721129: Workflow Initiative and is only meant for planning and governance sign-offs. Work will happen in child issues of this plan.

This phase will leverage the new archive and purge API and implement a new experimental module called Trash which gives the ability to "undo" or "restore" the deletion of content entities.
See Trash module for current implementation in contrib.

Sign-offs needed

Product manager

A product manager needs to sign-off on this plan as the above phases are required as part of a planned initiative.

Framework manager

A framework manager needs to sign-off on this plan as the above phases introduces major API additions (archive and purge).

Release manager

A release manager needs to sign off because the scope and impact of the work are significant for core.

Sub-system maintainers

The sub-system maintainers for the Entity API needs to sign-off on this plan as it significantly impacts the Entity API.

Sign-offs given

  • Product manager - pending
  • Framework manager - pending
  • Release manager - pending
  • Sub-system maintainers - pending

Comments

dixon_ created an issue. See original summary.

dixon_’s picture

dixon_
he/him
Primary language English
Location France
commented
Issue summary: View changes
naveenvalecha’s picture

naveenvalecha
He/Him
commented
Issue summary: View changes
catch’s picture

catch
he/him
Primary language English
commented
Issue tags: +Needs framework manager review, +Needs release manager review, +Needs product manager review

Has there been any discussion about how to manage expectations for config entities?

Right now if you delete either content or configuration you know it's gone forever. With trash module, you can restore content, but config the behaviour is the same.

Since deleting config results in both the deletion of other config that depends on it and/or removal of configuration from other configuration objects, restoring configuration would be close to impossible - we could do things like configuration snapshotting (i.e. export config A, make a change, import config A again which undoes the change), but that's very different.

dixon_’s picture

dixon_
he/him
Primary language English
Location France
commented

@catch No, we haven't thought anything about that yet. Perhaps we should add that as a challenge to be resolved in #2725449: WI: UX prototypes for Trash module.

naveenvalecha’s picture

naveenvalecha
He/Him
commented
Project: Drupal core » Drupal core ideas
Version: 8.3.x-dev »
Component: entity system » Idea

Moving this to Drupal core Ideas project as this issue is for the roadmap/plan for the trash module and it only needs the signoff from product manager and release manager other than patches.

dixon_’s picture

dixon_
he/him
Primary language English
Location France
commented
Issue summary: View changes
dixon_’s picture

dixon_
he/him
Primary language English
Location France
commented
Issue summary: View changes
quietone’s picture

quietone commented
Project: Drupal core ideas » Drupal CMS development repository
Component: Idea » General
Category: Plan » Feature request

The Ideas project is being deprecated. As discussed in a core committer meeting issues that are adding modules are being moved to the Drupal CMS project for discussion.

phenaproxima’s picture

phenaproxima
he/him
Primary language English
Location Massachusetts
commented

The Trash module is already included with Drupal CMS and has been since the beginning. Should we close this issue as fixed?

tim.plunkett’s picture

tim.plunkett
he/him
Primary language English
Location Philadelphia
commented
Issue tags: +Moved from Ideas queue
catch’s picture

catch
he/him
Primary language English
commented
Status: Active » Fixed

Should we close this issue as fixed?

Yes :)

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.