gdpr_tasks: SAR Only exports user fields

Open on Drupal.org →

Created on 31 July 2021, over 3 years ago

Updated 16 July 2024, 8 months ago

Problem/Motivation

This is a D9 install.

I've configured one content type to have some fields that are to be included in GDPR right to access. At least one content entity is created by the user with this field populated.

I've also configured several fields on the user profile to be included.

When using the user account to request access to content a job is created, cron is run, and the task is avaliable to look at in the task list it shows the user field but it does not show the field configured on the content type.

When the requests is processed and cron is run it generates with a main.csv that includes the list of user fields and their content.

The CSV does not contain any of the other fields from content types.

As an aside: In the case of a file field is the file suppose to be exported or not? One of the user fields I have selected for testing is the photo field, and I do get the file name listed as assets/.png but no file is included in the zip. Not sure if this is by design or is possibly a similar fault to not including the other fields.

I've been trying to track this through the traveral routines to see what is going on though I'm not significantly familiar with it. The best I can see it looks like traversal is only occurring on the User entity and there is no call to the other entity types to loop through them and obtain their content.

Also always possible I just don't understand how this module is suppose to work.

This also appears to apply to right to be forgotten tasks not finding the additional fields.

Steps to reproduce

Install module.
Create a content type and configure the body field to be included in a right to access and to be forgotten (remove)
Configure user fields to be included in right to access.
Create content under this content type.
Request a content export.
Run Cron
Approve the export (note: only user fields included)
Run Cron
Download the file and only user fields are included, expect all fields to be included.

Request to be forgotten can than be run and note that the body field will still exist without having been deleted.

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

🐛 Bug report

Status

Active

Version

3.0

Component

Code

Created by

🇺🇸United States cmlara

Live updates comments and jobs are added and updated live.

Incomplete comments

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Comment 8 months ago →
TH94
Facing similar issues in Drupal 10. Is there any specific configurations needs to be done to solve this
Comment 8 months ago →
🇺🇸United States cmlara
I was never able to figure out the cause or a config change to make this work.

I ended up not deploying the GDPR module as the site was operating without any EU users and was also exempted from CCPA, it was just a desire of the site to go “above and beyond” by implementing the feature.

Per above to me it appeared that this portion of the feature was not implemented for anything but the User entity, and even then it appeared to only be partial (file name without file).
Comment 8 months ago →
TH94
There should be a possible solution regarding this. If only user entity can be exported not other fields it doesn;t make sense to export, As a user might have user specific fields like comments ,discussions etc. Also the data is displayed as an ID for taxonomies, where it should be displayed as text.

I am hoping any other users/contributors who is using this module can comment regarding this.
Comment 8 months ago →
🇺🇸United States cmlara
I am hoping any other users/contributors who is using this module can comment regarding this.

I have pinged this issue in the #gdpr Slack room as well since it is no longer just me seeing this.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024