gitlab-org--gitlab-foss/app/views/users/terms/index.html.haml

- content_for :page_specific_javascripts do
  = render "layouts/google_tag_manager_head"
  = render "layouts/one_trust"
  = render "layouts/bizible"
= render "layouts/google_tag_manager_body"

#js-terms-of-service{ data: { terms_data: terms_data(@term, @redirect) } }
Add latest changes from gitlab-org/gitlab@master 2021-12-02 16:10:16 -05:00			`- content_for :page_specific_javascripts do`
			`= render "layouts/google_tag_manager_head"`
			`= render "layouts/one_trust"`
Add latest changes from gitlab-org/gitlab@master 2022-02-17 04:15:27 -05:00			`= render "layouts/bizible"`
Add latest changes from gitlab-org/gitlab@master 2021-12-02 16:10:16 -05:00			`= render "layouts/google_tag_manager_body"`
Enforces terms in the web application 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. 2018-04-27 10:50:33 -04:00
Add latest changes from gitlab-org/gitlab@master 2021-12-16 07:15:41 -05:00			`#js-terms-of-service{ data: { terms_data: terms_data(@term, @redirect) } }`