-
Bug
-
Resolution: Fixed
-
Critical
-
3.3.9, 3.4.6, 3.5.3
-
MOODLE_33_STABLE, MOODLE_34_STABLE, MOODLE_35_STABLE
-
MOODLE_33_STABLE, MOODLE_34_STABLE, MOODLE_35_STABLE
-
MDL-64205-master-sarunconfirmeduser -
This has been originally reported by marycooch at her own site and I was able to reproduce it.
Say a user self-registers but does not confirm the account. Eventually the task delete_unconfirmed_users_task gets executed and an automatic request to delete the user's data is created (via the observer introduced in MDL-62564), but the user's account is immediately deleted. So we end up with a record in the tool_dataprivacy_request table pointing to a non-existing userid.
I believe we should not delete the actual user record - even for unconfirmed users - same as we do not deleted them in the delete_incomplete_users_task
- is a regression caused by
-
MDL-62564 Improve bulk deletion
- Closed