Skip to content
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.

Sign up for GitHub

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

Jump to bottom

canComment() permissions #129

Open
hypeJunction opened this issue Jul 21, 2015 · 2 comments
Open

canComment() permissions #129

hypeJunction opened this issue Jul 21, 2015 · 2 comments

Comments

@hypeJunction
Copy link
Contributor

I am noticing that the core doesn't really check canComment() permissions before rendering a form or when saving a comment. Seems that we rely entirely on canWriteToContainer() permissions. We need to align these. Perhaps it would make sense to rewrite canComment() to default to canWriteToContainer()
@hypeJunction
Copy link
Contributor Author

There is a difference in how these two behave with regards to group content.

@hypeJunction
Copy link
Contributor Author

@juho-jaakkola

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@hypeJunction