-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Users are not removed in related tables (i.e. Institution users) if the main user entry is deleted #3265
Comments
Fix in #3284, would be great if you could test it |
amercader
added a commit
that referenced
this issue
Oct 21, 2016
amercader
added a commit
that referenced
this issue
Oct 21, 2016
Otherwise when passing the user name on `user_delete` the memberships where not deleted
amercader
added a commit
that referenced
this issue
Oct 21, 2016
Otherwise we miss all the membership logic
wardi
added a commit
that referenced
this issue
Oct 25, 2016
[#3265] Fixes removal of memberships on user_delete
amercader
added a commit
that referenced
this issue
Oct 26, 2016
Conflicts: ckan/tests/logic/action/test_delete.py
amercader
added a commit
that referenced
this issue
Oct 26, 2016
Otherwise when passing the user name on `user_delete` the memberships where not deleted
amercader
added a commit
that referenced
this issue
Oct 26, 2016
Otherwise we miss all the membership logic
amercader
added a commit
that referenced
this issue
Feb 14, 2017
amercader
added a commit
that referenced
this issue
Feb 14, 2017
Otherwise when passing the user name on `user_delete` the memberships where not deleted
amercader
added a commit
that referenced
this issue
Feb 14, 2017
Otherwise we miss all the membership logic
amercader
added a commit
that referenced
this issue
Feb 14, 2017
amercader
added a commit
that referenced
this issue
Feb 14, 2017
Otherwise when passing the user name on `user_delete` the memberships where not deleted
amercader
added a commit
that referenced
this issue
Feb 14, 2017
Otherwise we miss all the membership logic
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
CKAN Version if known (or site URL)
2.4
Please describe the expected behaviour
An user assigned to different organisations / roles should be removed from each group / role if the user is deleted. If not, zombie user entries persist in the system.
Please describe the actual behaviour
The users are not deleted from groups / roles if the main user entry is deleted.
What steps can be taken to reproduce the issue?
Check the relations between main user tables and the related tables. In detail, is the relation a real relational one or not (is the delete flag set or not)?
The text was updated successfully, but these errors were encountered: