Opened 6 years ago
Closed 6 years ago
#7820 closed defect (bug) (fixed)
Privacy: Data export for Groups
Reported by: | boonebgorges | Owned by: | |
---|---|---|---|
Milestone: | 4.0 | Priority: | normal |
Severity: | normal | Version: | |
Component: | Groups | Keywords: | has-patch |
Cc: |
Description
Parent ticket: #7698
We should include some data about groups in WP user data exports.
What should be included? Much of the content within groups is either handled by Activity (and thus is more logically included in that export) or is handled by plugins (BuddyPress Docs, bbPress, etc). I'd suggest, then, that we really just need a list of group memberships.
We store group memberships in a sorta funky way, so that invitations count as memberships as well. For purposes of the export, I think it's probably OK to lump them together, under a heading 'Group Memberships and Invitations Received'. Each would then have info roughly like this:
- name
- url
- date_modified (label could change based on whether user is a member - "Date Joined" or "Date Invited")
- inviter name (if there is one)
- "status", which could be a translation of
is_confirmed
andis_banned
and the otheris_
fields into "Banned", "Member", "Mod", "Admin", "Pending", "Creator" (?) (also, do we show 'banned'? this is strictly speaking data that we have about the user)
I guess we may want a different section for "Group Invitations Sent", since the concept is pretty different. Presumably, it'd be:
- group name
- group url
- date sent
- invitee name
- status
Does this seem like a fair description of what ought to be included?
Attachments (4)
Change History (12)
#2
@
6 years ago
I've started on the patch for this, and it appears that there are, in fact, four different kinds of data that need to be fetched for a given user
- Confirmed memberships
- Pending invitations *to* the user
- Pending membership requests initiated by the user
- Pending invitations *sent by* the user
We have easy techniques for getting a-c - I'll attach a patch. We have no good way of getting d. I've opened a ticket for it: #7859. Once implemented, this type of data will probably need a separate exporter, so that batch counting works properly.
#4
@
6 years ago
- Keywords has-patch added; needs-patch removed
7820.2.diff is an update, after a revision to #7859.
It breaks each of the four different data types into its own exporter. This results in a bit more code (a small amount of it duplicated). But it simplifies the logic, and most importantly, it makes it possible to paginate properly for batch processing.
Milestone renamed