Moodle in English: GDPR is a no go for now

GDPR is a no go for now

by Ray Havlin - Wednesday, January 23, 2019, 9:54 AM

(Until this is resolved I cannot allow any IPs where new regulations like GDPR is in effect due to the legal exposure.)

I am trying to prototype the data requests functionality that is part of compiling with GDPR. I am sorry to report, that it is simply not working. I have seen others posting here with the same results and at a dead end with no further way to proceed further.

https://moodle.org/mod/forum/discuss.php?d=379216

I have tirelessly read EVERYTHING I can find in the docs, forums and tracker. I know that this is new functionality and may have some gaps in the docs or a few bugs, but I am simply unable to produce any successful results with the most basic settings.

I had been testing the data requests functionality on 3.6.1 as well as 3.6.2 and have found that a "export" request or "delete" request after being approved by the admin stays in a perpetual state of "processing". I have the data registries defined and have 'set' their defaults, or at least I believe I have done so correctly based upon the current documentation.

So I'd like to help out with my end goal being to document a best practice with step-by-step instructions to share with everyone. However, I simply don't have any additional paths to test for a successful outcome at this point.

Any help is gratefully appreciated

Ray

Re: GDPR is a no go for now

by Tim Hunt - Wednesday, January 23, 2019, 5:10 PM

If cron running on your server? https://docs.moodle.org/en/Cron

Average of ratings:Useful (1)

Re: GDPR is a no go for now

by Amit Kumar - Wednesday, July 3, 2019, 10:15 PM

Hi Have run cron job and purge cache. but its showing processing status.

Average of ratings: -

Re: GDPR is a no go for now

by Ken Task - Thursday, July 4, 2019, 1:54 AM

No solution ... but a suggestion since you had PM'd me about another issue/question - include that here as well.

Comment about 'processing' status, however ... could foresee that not being 'instant' depending upon factors user(s) related. One user/multiple users?

One place to look is at task ...

There are 4 task related:

\tool_dataprivacy\task\delete_existing_deleted_users
\tool_dataprivacy\task\delete_expired_contexts
\tool_dataprivacy\task\delete_expired_requests
\tool_dataprivacy\task\expired_retention_period

Using command line, you could run each to see what's up:

cd moodlecode/admin/tool/task/cli/

Then run each one like so:

php schedule_task.php --execute="\tool_dataprivacy\task\delete_existing_deleted_users"

'SoS', Ken

Average of ratings: -

Re: GDPR is a no go for now

by Ray Havlin - Thursday, July 4, 2019, 3:12 AM

FYI - per my original post here...

After the upgrade to Moodle 3.7 (Build: 20190520) all of the stuck Data Requests have now completed successfully with out any intervention on my part.

I'll be re-testing to see if there are any remaining issues.

Ray

Average of ratings:Useful (2)

Re: GDPR is a no go for now

by Helen Foster - Thursday, July 4, 2019, 1:24 PM

Thanks Ray for posting. It's good to hear that after upgrading to 3.7 that stuck data requests have completed! Hopefully you won't encounter any further issues.

Average of ratings: -

Security and privacy

GDPR is a no go for now