Fix `created_on` in `UserSettingsModel`
See original GitHub issueThe created_on
field contains a lot of invalid values because there was a bug in a way how we saved the UserSettingModel
s (this was fixed in #9252).
We need to fix the created_on
via one-off job. The job will look through other fields in UserSettingModel
and through other models from the same user and compares them in order to find the lower date. This date is then set as the new created_on
.
The fields to look through are:
last_agreed_to_terms
last_started_state_editor_tutorial
last_started_state_translation_tutorial
last_logged_in
last_edited_an_exploration
last_created_an_exploration
Other models to look through are mostly from https://github.com/oppia/oppia/blob/develop/core/storage/user/gae_models.py
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (7 by maintainers)
Top Results From Across the Web
Releases · openfarmcc/OpenFarm
Mostly security upgrades and build system fixes. ... Change terminology to "Member"; Add user settings model; Add images to stage actions ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@sajalasati Yes, you can, I have assigned you.
@itsmayank0 Hi, this issue is not recommended for new contributors. Please pick one of these https://github.com/oppia/oppia/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3A"good+first+issue" issues to take up as a new contributor.