Open
Description
- How do permissions wind up getting created in the permissions table?
- What do the first and last part of a dotted permission name like
reviews.can_manage_tutorials
refer to in the Django database? - Why could we not find a permission that we could grant the Tutorials chair that would make the view
review_section()
insymposion/reviews/views.py
show the accept / reject dropdown choices when the chair viewed the URLhttps://us.pycon.org/2016/reviews/section/tutorials/
?
We need documentation for:
- Exactly the permission that will give a Tutorials Chair the ability to visit
https://us.pycon.org/2016/reviews/section/tutorials/
and see the accept / reject buttons. - Exactly the permission that will let the Tutorials Chair visit
https://us.pycon.org/2016/reviews/section/tutorials/
and see the "Result Notification" link over in the red-and-pink navigation bar that already says "Reviews" and "Voting status". - Exactly the permission that will let the Tutorials Chair visit
https://us.pycon.org/2016/reviews/section/tutorials/notification/accepted/
and see the accepted and rejected tutorials that are eligible to be emailed.
The problem could be a spelling error in the permissions checks in views.py
, or the problem could be that the permissions are not being correctly created in the first place, or the problem could be stale data in a fixture that was not updated when the code was updated.
Metadata
Assignees
Labels
No labels
Activity