Issue 260: All pod reports broken by new permission check
Status:  Fixed
Owner:
Closed:  Dec 2011
Project Member Reported by dmbs...@gmail.com, Dec 15, 2011
By https://code.google.com/p/student-worker-relational-database/source/detail?r=94b0a31518b13788cab5db7acb8149f55874f937

@user_passes_test(lambda u: u.has_perm('schedule.grade_reports'))

request must be passed which in this case ins't. So this breaks all reporting

Hacked production to avoid the checking.
Dec 15, 2011
Project Member #1 ca...@burkesoftware.com
thanks. I thought I had removed that and moved it to views. It's still in
views. I'll play with it today and make sure people who shouldn't pull
reports don't have access without that there.

On Thu, Dec 15, 2011 at 9:59 AM, <
student-worker-relational-database@googlecode.com> wrote:
Dec 15, 2011
Project Member #2 ca...@burkesoftware.com
Should be fine. Tried it with a couple of different perm levels, seemed to work appropriately.
Status: Needs_Verified
Dec 15, 2011
Project Member #3 dmbs...@gmail.com
Works but we must merge the different sis and schedule permissions together
Status: Patch_Needs_Improvement
Dec 16, 2011
Project Member #4 ca...@burkesoftware.com
(No comment was entered for this change.)
Status: Fixed
Cc: -da...@burkesoftware.com