Datetime when user agreed to privacy policy should be allowed to be empty #63154

Closed
opened 2019-03-31 15:22:48 +02:00 by Sybren A. Stüvel · 3 comments

When a user hasn't agreed to our privacy policy, we currently can't edit the user in the Blender ID admin, because it's a field that isn't allowed to be blank. The root problem here is that we have such users at all (who signed up via the store and never agreed to anything). However, currently this not-allowed-to-be-blank requirement blocks our ability to change a user's email address, getting in the way of synchronisation issues between Store and ID.

When a user hasn't agreed to our privacy policy, we currently can't edit the user in the Blender ID admin, because it's a field that isn't allowed to be blank. The root problem here is that we have such users at all (who signed up via the store and never agreed to anything). However, currently this not-allowed-to-be-blank requirement blocks our ability to change a user's email address, getting in the way of synchronisation issues between Store and ID.
Author
Owner

Added subscriber: @dr.sybren

Added subscriber: @dr.sybren
Author
Owner

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
Sybren A. Stüvel self-assigned this 2019-09-26 12:13:59 +02:00
Author
Owner

Was resolved in {2aa2e9a460948654e06c9697d7ad207081ed91ef}

Was resolved in {2aa2e9a460948654e06c9697d7ad207081ed91ef}
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: infrastructure/blender-id#63154
No description provided.