*** This bug is a duplicate of bug 1171310 ***
https://bugs.launchpad.net/bugs/1171310
** Changed in: mahara
Milestone: 1.8.0rc1 = None
** Changed in: mahara
Assignee: Son Nguyen (ngson2000) = (unassigned)
** This bug has been marked a duplicate of bug 1171310
Can bypass comment
** Changed in: mahara
Status: Invalid = Triaged
** Changed in: mahara
Milestone: 1.7.0 = 1.8.0
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
https://bugs.launchpad.net/bugs/1095890
Title:
allowcomments not
** Changed in: mahara
Assignee: (unassigned) = Son Nguyen (ngson2000)
** Changed in: mahara
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
https://bugs.launchpad.net/bugs/1095890
There are two options the function user_comments_allowed() needs to
check: allowcomments and approvecomments.
if allowcomments of one access right is true, the user can put comments
and if approvecomments of one access right is FALSE given the
allowcomments is TRUE then the user can publish
Hi Son,
The issue with this is that you can't actually configure the
allowcomment flag of any access rights, in the web interface it
appears as just a overall view setting.
I think either the for loop needs to cover the objectionable access
type which doesn't show up anywhere in the access
5 matches
Mail list logo
