beat.web issueshttps://gitlab.idiap.ch/beat/beat.web/-/issues2020-09-28T13:36:45Zhttps://gitlab.idiap.ch/beat/beat.web/-/issues/570Fix url prefix usage in yearly account revalidation command2020-09-28T13:36:45ZFlavio TARSETTIFix url prefix usage in yearly account revalidation commandThe command and message needs to be updated to fix the url prefix usage.The command and message needs to be updated to fix the url prefix usage.Django 3 migrationFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/569Deletion of migration patch for current users to the supervision system2020-09-28T13:36:52ZFlavio TARSETTIDeletion of migration patch for current users to the supervision systemThe migration patch ecosystem that was used to warn current users of the new supervision system needs to be removed as it unused and it no longer makes sense to keep it in the repository.
The following migrations need to be adjusted to ...The migration patch ecosystem that was used to warn current users of the new supervision system needs to be removed as it unused and it no longer makes sense to keep it in the repository.
The following migrations need to be adjusted to accommodate with this.
The email generated for this need to be removed too.Django 3 migrationFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/568Crash on new supervisor sign-up2020-09-28T13:36:52ZFlavio TARSETTICrash on new supervisor sign-upThe application crashes with a `django.contrib.auth.models.User.DoesNotExist: User matching query does not exist.` when signing-up as a new supervisor.
This issue has shown up after the shift to Django 3The application crashes with a `django.contrib.auth.models.User.DoesNotExist: User matching query does not exist.` when signing-up as a new supervisor.
This issue has shown up after the shift to Django 3Django 3 migrationFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/564Crash in some admin pages2020-09-11T15:56:04ZSamuel GAISTCrash in some admin pagesWhen trying to go to an admin page that shows a beat asset, the site crashes because of a missing parameter.When trying to go to an admin page that shows a beat asset, the site crashes because of a missing parameter.Django 3 migrationSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/561Update dependencies to Django 32020-09-28T13:36:49ZSamuel GAISTUpdate dependencies to Django 3The version of Django currently used by the platform is outdated.
This issue tracks the update of the Django as well as its dependencies to a current and maintained version.The version of Django currently used by the platform is outdated.
This issue tracks the update of the Django as well as its dependencies to a current and maintained version.Django 3 migrationSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/560E-mail confirmations not containing the URL prefix and User links on the website2020-09-28T13:37:32ZFlavio TARSETTIE-mail confirmations not containing the URL prefix and User links on the websiteIssues with e-mail confirmations need to be checked as they don't contain the URL prefix and User links on the website.
On a local instance of beat.web this works, but it fails on the production platform. This seems to be a Django rel...Issues with e-mail confirmations need to be checked as they don't contain the URL prefix and User links on the website.
On a local instance of beat.web this works, but it fails on the production platform. This seems to be a Django related issue as a first guess.
A similar problem also seem to happen with "experiments".
Might be related to #558 and #561 Django 3 migrationFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/559Python 2 Code removal2020-09-28T13:36:53ZSamuel GAISTPython 2 Code removalCurrently beat/beat.web> code is still compatible with Python 2.
The infrastructure has been running Python 3 for several years and moving to Django 3 implies that Python 2 is now out of question.
This issue tracks the work of removing...Currently beat/beat.web> code is still compatible with Python 2.
The infrastructure has been running Python 3 for several years and moving to Django 3 implies that Python 2 is now out of question.
This issue tracks the work of removing all the compatibility code that has not been used for years and that will not be used anymore.Django 3 migrationSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/558Fix usage of URL_PREFIX2020-09-28T13:38:15ZSamuel GAISTFix usage of URL_PREFIXCurrently the URL_PREFIX settings variable is used like a fully qualified URL in many parts of the website which is wrong. As the name suggests, this prefix shall essentially "move" all the URLs of the site behind it.
If a fully qualifi...Currently the URL_PREFIX settings variable is used like a fully qualified URL in many parts of the website which is wrong. As the name suggests, this prefix shall essentially "move" all the URLs of the site behind it.
If a fully qualified address is needed it should be generated either using the request object associated with the method call or using Django's Sites framework.
This issue tracks the cleanup of the following:
- [x] Email generation
- [x] Template rendering
- [x] Other usagesDjango 3 migrationFlavio TARSETTIFlavio TARSETTI