-
Notifications
You must be signed in to change notification settings - Fork 669
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
Comment and reply permissions overrides #10022
Conversation
Extending classes can now explicitly pass default canComment permissions value to the parent class
Reopening. This needs to go in in some form |
Considering the desire to make replies into regular comments, does this make that harder? |
$entity->disable_comments !== true |
* @param int $user_guid GUID of the user to leave a reply | ||
* @return bool | ||
*/ | ||
public function canReply($user_guid = 0) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why aren't we using this anywhere?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR is adding it
Oh. I sorry I misunderstood your comment. I thought this was thr PR about disabljng comments. |
Replaced by #10465 |
feat(discussions): discussion topics now have their own class
feat(comments): entities can now inherit canComment permissions
Extending classes can now explicitly pass default canComment permissions value to the parent class
feat(discussions): adds a shortcut ElggDiscussion::canReply method