| 2009-03-02 14:39:43 |
Paul Everitt |
bug |
|
|
added bug |
| 2009-03-02 14:40:54 |
Paul Everitt |
karl3: importance |
Undecided |
Medium |
|
| 2009-03-02 14:40:54 |
Paul Everitt |
karl3: assignee |
|
chrism-plope |
|
| 2009-03-02 14:40:54 |
Paul Everitt |
karl3: statusexplanation |
|
I checked and the form handling is "right", meaning the code gets the right value from the form and follows the branching correctly. This one is probably more important than other bugs (though I didn't mark High) because it impacts a broad range of evaluation. |
|
| 2009-03-02 14:40:54 |
Paul Everitt |
karl3: milestone |
|
m4 |
|
| 2009-03-02 17:58:42 |
Paul Everitt |
description |
Choosing "Private" on the add-community or edit-community view |
Choosing "Private" on the add-community or edit-community view should result in the community being made private. Instead, here is what happens:
1) Click Add Community.
2) Choose Private and save.
3) Click Overview, then Edit to get to edit-community.
4) The "Public" radio button is selected.
5) Additionally, a different staff user is still able to get to the community, thus it isn't private. |
|
| 2009-03-02 19:53:14 |
Chris McDonough |
karl3: status |
New |
Fix Committed |
|
| 2009-03-02 19:53:14 |
Chris McDonough |
karl3: statusexplanation |
I checked and the form handling is "right", meaning the code gets the right value from the form and follows the branching correctly. This one is probably more important than other bugs (though I didn't mark High) because it impacts a broad range of evaluation. |
Jiggling the "private/public" toggle on the edit form now changes security.
I can't replicate the "other staff can see private community" claim. |
|
| 2009-06-08 22:37:30 |
Paul Everitt |
karl3: status |
Fix Committed |
Fix Released |
|
