[wp-trac] [WordPress Trac] #43443: Add a method for confirmation of requests for deleting or anonymizing of personal data

WordPress Trac noreply at wordpress.org
Fri Mar 23 15:05:59 UTC 2018


#43443: Add a method for confirmation of requests for deleting or anonymizing of
personal data
-------------------------------------------------+-------------------------
 Reporter:  azaozz                               |       Owner:  mikejolley
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  5.0
Component:  General                              |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  gdpr has-patch dev-feedback needs-   |     Focuses:
  testing                                        |
-------------------------------------------------+-------------------------

Comment (by allendav):

 Replying to [comment:17 mikejolley]:
 > @allendav I actually think that would be a mistake here. We should keep
 this mechanism for the approval only, not make it into a log.
 >
 > > I'm in the middle of hooking up everything and I've gotten to the
 point where I'd like to fill a WP_List_Table with the requests and their
 status
 >
 > If this what we're doing, with a CPT, when the request is triggered it
 should be logged as pending, then approval should be obtained with the
 email.
 >
 > When confirmed, hook in and update the log entry. Then the log is
 independent of this mechanism.
 >
 > What we may want to add is instead a way to pass data with the action so
 when it's confirmed, the data is passed to the action. Then you could for
 example pass the log ID so it's updated :)
 >
 > Sound good?

 If we switch to a CPT for facilitating the approvals, we wouldn't use the
 options/meta approach anymore right?

 And, if we switch to a CPT, would we not want this patch/code to store the
 approval in post meta itself instead of relying on code in a separate
 patch?

 I _do_ like the idea of having the action (including passing hooked
 callbacks the CPT id and action in play) so that plugins can do additional
 things with this approval mechanism you've created beyond the storing of
 request-started, request-approved in a CPT.

 Does that make sense?

--
Ticket URL: <https://core.trac.wordpress.org/ticket/43443#comment:18>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list