[buddypress-trac] [BuddyPress Trac] #7698: GDPR

buddypress-trac noreply at wordpress.org
Fri May 11 22:22:29 UTC 2018

#7698: GDPR
 Reporter:  DJPaul        |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  3.1
Component:  Core          |     Version:
 Severity:  normal        |  Resolution:
 Keywords:                |

Comment (by boonebgorges):

 Replying to [comment:12 r-a-y]:
 > Can we only load this code when the WP data exporter functionality runs,
 which is on the admin AJAX action?

 Thinking about it more, I don't think we should do this. There are non-
 AJAX places where WordPress calls the `wp_privacy_personal_data_exporters`
 hook, so the part I've currently got in `bp-*-filters.php` can't be loaded
 in the way you suggest. As for the exporter callbacks themselves, loading
 them only on a specific AJAX action means we lose the flexibility of
 building a front-end self-service request tool, at least without having
 additional logic for loading the necessary callbacks. I don't have a
 problem with optimizing, but let's avoid getting overly clever until we
 figure out the more general shape of things: what the callbacks should
 look like, how data should be chunked and represented, how it'll be
 fetched through the interface and by whom, etc.

Ticket URL: <https://buddypress.trac.wordpress.org/ticket/7698#comment:15>
BuddyPress Trac <http://buddypress.org/>
BuddyPress Trac

More information about the buddypress-trac mailing list