[wp-trac] [WordPress Trac] #43442: Add tools for anonymizing of commenters
WordPress Trac
noreply at wordpress.org
Wed Apr 18 18:22:31 UTC 2018
#43442: Add tools for anonymizing of commenters
------------------------------------------+-----------------------
Reporter: azaozz | Owner: allendav
Type: enhancement | Status: assigned
Priority: normal | Milestone: 5.0
Component: General | Version:
Severity: normal | Resolution:
Keywords: gdpr has-patch needs-testing | Focuses:
------------------------------------------+-----------------------
Comment (by birgire):
Thanks for the feedback @allendav
- Yes, it's something to consider, I'm still 50/50 divided between
approach b) and c) ;-)
I might have had few timeout cases in the past, when deleting hundreds
of spam comments in bulk, in wp-admin.
- Regarding the messages in {{{wp_comments_personal_data_eraser}}}, one
way could be to grab possible (rare) db update errors with:
{{{
$updated = $wpdb->update( $wpdb->comments, $anonymized_comment, array(
'comment_ID' => $comment->comment_ID,
) );
if ( $updated ) {
$num_items_removed++;
} else {
$messages[] = sprintf(
'Comment %d contained personal data but could not be
anonymized.',
$comment->comment_ID
);
}
}}}
- Any particular structure here for {{{$messages}}} (like we see e.g. in
the {{{$data_to_export}}} array
[https://core.trac.wordpress.org/changeset/42888 here]) ?
- Another thing to consider is empty input for
{{{wp_comments_personal_data_eraser()}}}, it will still erase comments, as
it will call {{{get_comments()}}} but without the email filtering.
- Also the admin page is ''Remove Personal Data'' but here we have
''erase'' functions. So we have both "remove" and "erase". I think we
should consider only one of them for consistency.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/43442#comment:22>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list