Move cert date signals to avoid race conditions
COURSE_CERT_DATE_CHANGE was being called before saving the new data in the course overview. The listeners were expecting to pull the data out of the course overview, and thus were only right about half the time. This moves the signal to trigger after the course publish signals are handled.
Showing
- openedx/core/djangoapps/content/course_overviews/signals.py 7 additions, 0 deletionsopenedx/core/djangoapps/content/course_overviews/signals.py
- openedx/core/djangoapps/content/course_overviews/tests/test_signals.py 4 additions, 0 deletions...djangoapps/content/course_overviews/tests/test_signals.py
- openedx/core/djangoapps/courseware_api/views.py 0 additions, 1 deletionopenedx/core/djangoapps/courseware_api/views.py
- openedx/core/djangoapps/models/course_details.py 0 additions, 5 deletionsopenedx/core/djangoapps/models/course_details.py
- openedx/core/djangoapps/programs/signals.py 8 additions, 3 deletionsopenedx/core/djangoapps/programs/signals.py
- openedx/core/djangoapps/programs/tasks.py 4 additions, 1 deletionopenedx/core/djangoapps/programs/tasks.py
- openedx/core/djangoapps/programs/tests/test_signals.py 7 additions, 3 deletionsopenedx/core/djangoapps/programs/tests/test_signals.py
Please register or sign in to comment