WordPress.org

Make WordPress Core

Opened 3 years ago

Closed 20 months ago

#43912 closed enhancement (wontfix)

Requests (new, pending, completed) should not be deletable.

Reported by: xkon Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: Privacy Keywords:
Focuses: administration Cc:

Description

After todays bug scrub - splitting this from #43481.

azaozz wrote ( https://core.trac.wordpress.org/ticket/43481#comment:46 ):

Requests (new, pending, completed) should not be deletable. This is important for keeping audit log. The only exception may be be requests that haven't been confirmed by email, but then we can auto-delete them when the link in the email expires (and they become unusable).

There is a discussion following that comment on logging ( also there's a somewhat related ticket please see #43797 )

Change History (10)

#1 @desrosj
3 years ago

  • Component changed from General to Privacy

Moving to the new Privacy component.

#2 @birgire
2 years ago

Related #44047

This ticket was mentioned in Slack in #gdpr-compliance by desrosj. View the logs.


2 years ago

#4 @desrosj
2 years ago

Possibly related: #44222.

An "archive" state could be used instead of deleting the request.

#5 @desrosj
2 years ago

  • Keywords gdpr removed

Removing the GDPR keyword. This has been replaced by the new Privacy component and privacy focuses in Trac.

This ticket was mentioned in Slack in #core-privacy by desrosj. View the logs.


2 years ago

#7 @desrosj
2 years ago

  • Keywords needs-patch added
  • Milestone changed from Awaiting Review to Future Release

Related #44707.

To play devil's advocate, what if a site administrator needs to be able to purge old requests?

#8 @desrosj
2 years ago

  • Focuses administration added

This ticket was mentioned in Slack in #core-privacy by birgire. View the logs.


2 years ago

#10 @xkon
20 months ago

  • Keywords needs-patch removed
  • Milestone Future Release deleted
  • Resolution set to wontfix
  • Status changed from new to closed

As we are going to build the logging mechanism, it will be keeping the relative data needed from both the Erasure / Export requests there as well.

Closing this as by keeping both entries into the logging + the lists themselves is pretty much unneeded double content.

Note: See TracTickets for help on using tickets.