Skip to content
This repository has been archived by the owner on Jan 18, 2020. It is now read-only.

Passing user should not fail if django-guardian is not installed #252

Closed
bruth opened this issue Oct 17, 2014 · 0 comments · Fixed by #253
Closed

Passing user should not fail if django-guardian is not installed #252

bruth opened this issue Oct 17, 2014 · 0 comments · Fixed by #253

Comments

@bruth
Copy link
Contributor

bruth commented Oct 17, 2014

This issue must be resolved for chop-dbhi/serrano#220 to work transparently.

bruth added a commit that referenced this issue Oct 17, 2014
This fixes an ambiguity when applying the permissions if a user is
passed to the published() manager method for DataField and DataConcept.

Fix #252

Signed-off-by: Byron Ruth <b@devel.io>
bruth added a commit that referenced this issue Oct 19, 2014
This fixes an ambiguity when applying the permissions if a user is
passed to the published() manager method for DataField and DataConcept.

Fix #252

Signed-off-by: Byron Ruth <b@devel.io>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant