summaryrefslogtreecommitdiff
path: root/app/controllers/users
Commit message (Collapse)AuthorAgeFilesLines
* Enable even more frozen string in app/controllersgfyoung2018-09-251-0/+2
| | | | | | | | | | | | Enables frozen string for some vestigial files as well as the following: * app/controllers/projects/**/*.rb * app/controllers/sherlock/**/*.rb * app/controllers/snippets/**/*.rb * app/controllers/users/**/*.rb Partially addresses #47424.
* Users can accept terms during registrationBob Van Landuyt2018-06-081-1/+2
| | | | | | | | | | When a user checks the `accept` checkbox, we will track that acceptance as usual. That way they don't need to accept again after they complete the registration. When an unauthenticated user visits the `/-/users/terms` page, there is no button to accept, decline or continue. The 'current-user menu' is also hidden from the top bar.
* Messaging on terms page when user already accepted46585-gdpr-terms-acceptancetauriedavis2018-06-041-0/+4
| | | | | We show a blue flash banner if the user already accepted, and show a button allowing them to continue to the application.
* Enforce terms acceptance before other requirementsBob Van Landuyt2018-05-111-0/+4
| | | | | | | This prevents a redirect loop when a user has to enable 2FA and accept the terms. Now they will need to accept the terms, then enable 2FA, or any other requirements.
* Enforces terms in the web applicationBob Van Landuyt2018-05-041-4/+14
| | | | | | | | | | | | | | | | | | | | This enforces the terms in the web application. These cases are specced: - Logging in: When terms are enforced, and a user logs in that has not accepted the terms, they are presented with the screen. They get directed to their customized root path afterwards. - Signing up: After signing up, the first screen the user is presented with the screen to accept the terms. After they accept they are directed to the dashboard. - While a session is active: - For a GET: The user will be directed to the terms page first, after they accept the terms, they will be directed to the page they were going to - For any other request: They are directed to the terms, after they accept the terms, they are directed back to the page they came from to retry the request. Any information entered would be persisted in localstorage and available on the page.
* Allow a user to accept/decline termsBob Van Landuyt2018-05-041-3/+40
| | | | | When a user accepts, we store this in the agreements to keep track of which terms they accepted. We also update the flag on the user.
* Display terms to a userBob Van Landuyt2018-05-041-0/+19
When terms are present, they can be viewed on `/-/users/terms`.
View Lorry Controller Status