Closed laurentdavid closed 3 years ago
Hi @sampaccoud! I am going to work with @laurentdavid to move this PR forward. Assuming we address all your concerns above, can you confirm that this is the right general approach?
@regisb Yes we are ok with the idea of adding a cohort as a result of a payment. The problem was the way it is implemented.
Closed at the benefit of PR https://github.com/openfun/fun-apps/pull/705
When user completes payment make sure that he/she is added to a cohort named DEFAULT_VERIFIED_COHORT_NAME ("certificat"). The user will be added to all matching cohorts in the course he/she is paying for.
Background information
The addition is made when edX is called back after the payment (so here from paybox). In this case we used to send a confirmation email and now we also add the user to matching cohorts. The name of the cohort to look for is "certificat" but can be changed in the django settings (the name of the variable is DEFAULT_VERIFIED_COHORT_NAME) However, if for some reason the routines stops before the callback, the user will never be added to the cohort and will need to be via the UI. edX has since resolved this issue by creating cohorts that will automatically get users that are on a specific enrolment track (verified for example). So this is a temporary solution until we get to an upgraded version of the edX platform.
Other changes