Change course settings to require explicit save.
Rather than asynchronously saving when a setting is updated, we now prompt the user to confirm their changes and only persist the data if they hit the save button. Lettuce tests are updated to expect this behavior and some new ones are added.
Showing
- CHANGELOG.rst 2 additions, 0 deletionsCHANGELOG.rst
- cms/djangoapps/contentstore/features/common.py 6 additions, 0 deletionscms/djangoapps/contentstore/features/common.py
- cms/djangoapps/contentstore/features/course-settings.feature 11 additions, 0 deletionscms/djangoapps/contentstore/features/course-settings.feature
- cms/djangoapps/contentstore/features/course-settings.py 14 additions, 13 deletionscms/djangoapps/contentstore/features/course-settings.py
- cms/djangoapps/contentstore/features/grading.feature 10 additions, 0 deletionscms/djangoapps/contentstore/features/grading.feature
- cms/djangoapps/contentstore/features/grading.py 13 additions, 0 deletionscms/djangoapps/contentstore/features/grading.py
- cms/static/js/models/settings/course_details.js 3 additions, 3 deletionscms/static/js/models/settings/course_details.js
- cms/static/js/views/settings/main_settings_view.js 22 additions, 25 deletionscms/static/js/views/settings/main_settings_view.js
- cms/static/js/views/settings/settings_grading_view.js 22 additions, 9 deletionscms/static/js/views/settings/settings_grading_view.js
- cms/static/js/views/validating_view.js 25 additions, 9 deletionscms/static/js/views/validating_view.js
Please register or sign in to comment