-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Accept modified terms #23
Comments
The terms are as of now hardcoded in a controller in the backend. When we change the terms we also change the 'date_of_update'. Whenever the user logs in the API checks if the terms has been accepted after last 'date_of_update'. The API has a method to check if the user has accepted already. |
@bjornhjelle what's the best way to reset the fact that an user has accepted the terms? I remember this was broken over at biocaching.com and could need to do that for debugging purposes... |
Logg into server as yourself, and: |
Great thanks!
2017-03-04 22:14 GMT+01:00 Bjørn Hjelle <[email protected]>:
… Logg into server as yourself, and:
$ sudo su - bc
$ cd speciesdb
$ rails db
Password: *****
MariaDB [speciesdb_production]> select id from users where email = '
***@***.***';
MariaDB [speciesdb_production]> update users set accepted_terms_at =
curdate() - interval 1 year where id = ();
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#23 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ACgoJ-nvLLQEUWlAMe8Ppr4EwGiixn8eks5ridRAgaJpZM4L_vd9>
.
|
Currently, users only need to accept terms once.
But when terms are updated, the user should accept them again.
This should be done in two locations:
If declining the terms, the user should be logged out.
The text was updated successfully, but these errors were encountered: