bugSavane - Bugs: bug #4794, comment posting restriction does...

 
 
Show feedback again

You are not allowed to post comments on this tracker with your current authentification level.

bug #4794: comment posting restriction does not work if set to 'same as new'

Submitted by:  Yves Perrin <ype>
Submitted on:  Thu 24 Nov 2005 10:54:33 AM UTC  
 
Category: Web Frontend: TrackersStatus: Fixed
Severity: 3 - NormalPriority: C - Normal
Assigned to: NoneOpen/Closed: Closed
Release: 1.2Planned Release: 1.3
Reproducibility: NonePrivacy: Public

Thu 24 Nov 2005 06:23:12 PM UTC, comment #3:

> or when this option is selected, the restriction should not use the group type

> default but the group posting restriction (which in their case was set to
> 'logged-in user')

Indeed, that was supposed to work that way.

Mathieu Roy <yeupou>
Project Administrator
Thu 24 Nov 2005 06:14:29 PM UTC, comment #2:

The group type default posting restriction was 'anonymous' which according to your comment would explain why non-logged-in users could post comments.
However either the restriction select box item currently labelled
'Same as for new items' should be renamed 'Same as group default posting restriction'
or when this option is selected, the restriction should not use the group type default but the group posting restriction (which in their case was set to 'logged-in user')

Yves Perrin <ype>
Project Administrator
Thu 24 Nov 2005 06:03:06 PM UTC, comment #1:

Looking at it, it seems that the functionality actually work, but it takes the group type setting, instead of the group one, as reference.

What is the default for the given group type on the given tracker?

Mathieu Roy <yeupou>
Project Administrator
Thu 24 Nov 2005 10:54:33 AM UTC, original submission:

1] If posting restriction for posting new items is 'logged-in users' and posting restriction for comments is 'same as for new', it is still possible to post comments as anonymous. But setting the comment posting restrictions explicitly to 'logged-in users' does work fine.
2] Why is it so that the 'status' field is mandatory at submission of new items while none of the pre-defined values make sense at the time of the original submission? (status configuration setting error?) ... so I set status to 'confirmed' just to get the bug posted.

Yves Perrin <ype>
Project Administrator

 

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by yeupou (Updated the item)
  • -unavailable- added by ype (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follow 5 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Thu 24 Nov 2005 06:22:17 PM UTCyeupouStatusConfirmed=>Fixed
      Open/Closed-Automatic update due to transitions settings-=>Closed
    Thu 24 Nov 2005 06:03:06 PM UTCyeupouPriorityA - Later=>C - Normal
      Release=>1.2
      Planned Release=>1.3
    Show feedback again

    Back to the top


    Powered by Savane 3.1-cleanup