Closed
Bug 1065442
Opened 10 years ago
Closed 9 years ago
Audit views that use PrivacyPolicyRequiredMixin as it may no longer be required in some situations
Categories
(Mozilla QA Graveyard :: One and Done, defect, P3)
Tracking
(Not tracked)
VERIFIED
FIXED
Future
People
(Reporter: bsilverberg, Unassigned)
Details
Attachments
(1 obsolete file)
There is a mixin that forces users to the profile screen in order to sign the privacy policy if they have not already done so. This is set up to fire on a few views, but it is likely no longer needed as users are also forced to sign the privacy policy upon logging in if they haven't already done so. Therefore it would be impossible for a user to access one of these views without already having been forced to sign the privacy policy after logging in. This logic was put in place initially to deal with users who hadn't signed the privacy policy but who were still logged in, but I wouldn't think we'd have any of those anymore.
Reporter | ||
Comment 1•10 years ago
|
||
Comment on attachment 8487255 [details] [review] Link to Github pull-request: https://github.com/mozilla/oneanddone/pull/175 Oops, didn't mean to include this. It came over with a clone.
Attachment #8487255 -
Attachment is obsolete: true
Reporter | ||
Comment 3•10 years ago
|
||
Thanks Tessy, you are more than welcome to work on this! Could you please assign it to yourself in Bugzilla, so that others do not think it is available to work on?
Reporter | ||
Comment 5•9 years ago
|
||
Commit pushed to master at https://github.com/mozilla/oneanddone https://github.com/mozilla/oneanddone/commit/c2519f889371d8ee30c8def51514687f51387579 Fix Bug 1065442 - Audit views that use PrivacyPolicyRequiredMixin as it may no longer be required in some situations
Reporter | ||
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Comment 6•9 years ago
|
||
Verified login on dev as an admin, regular user, and a new user.
Updated•6 years ago
|
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•