[wp-trac] [WordPress Trac] #43440: Add tools to show and export the personal data of commenters

[WordPress Trac]

#43440: Add tools to show and export the personal data of commenters
----------------------------------------+------------------
 Reporter:  azaozz                      |       Owner:
     Type:  enhancement                 |      Status:  new
 Priority:  normal                      |   Milestone:  5.0
Component:  Administration              |     Version:
 Severity:  normal                      |  Resolution:
 Keywords:  gdpr has-patch 2nd-opinion  |     Focuses:
----------------------------------------+------------------

Comment (by azaozz):

 Replying to [comment:5 xkon]:
 > First of all I was going to merge this idea with #43442 as well by
 creating a single function that handles an $arg as an action. So 1
 function could tackle deletion/anonymization/export/display of comments
 depending on what we want for the Tools page: for example
 `handle_comments( some at where.com, 'delete' );` etc. This would've been
 easy BUT!

 I'd rather we have separate functions for each action. Even if we handle
 all cases in one "low level" function we should have separate "helpers"
 for each action that will fire a filter or an action for plugins to hook
 in, etc.

 > @netweb brought to my attention on this ticket that there might me
 10.000 comments and because of that we should consider using the Export
 API that already works with batches so it should be perfect for websites
 with massive ammounts of comments etc instead of re-creating something
 that exists.

 I'm not so sure we need that. Even with an extreme amount of comments we
 do a similar DB query every time when displaying comments on each post on
 the front-end. The important part is that we have an index on
 `comment_author_email` that speeds things up considerably.

 Of course writing to the DB when deleting or anonymizing will be slower,
 but still think we can pull that off without batching. Lets do it
 "directly" for now and optimize for writing later if needed. Possible
 optimization can be to select the `comment_ID` in batches of lets say 500
 and use that to limit the writing.

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