| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| assessment | ||
| fileupload | ||
| locale | ||
| management | ||
| templates/openassessmentblock | ||
| tests | ||
| workflow | ||
| xblock | ||
| __init__.py | ||
| data.py | ||
| test_utils.py |
This corrects an issue where assessments were sometimes incorrectly associated with the wrong response. The behavior was caused because the POST request to the `peer_assess` handler only contained the feedback text/options and did _not_ include mention of which original response was being assessed. If the current workflow item is updated on the server _after_ the page first loads but _before_ the page is submitted, this submission will be incorrectly associated with the following response. Steps to reproduce: - Submit a response (User A). - Wait for peers to submit responses (User B and User C). - Load page with first peer response to be assessed (not not submit). - Open the same page again in a new tab. - In 1st tab, assess and submit assessment for User B. - In 2nd tab, assess and submit assessment for User B. - Notice that your assessment for User B's response is also applied to User C's response. This changeset does _not_ restore data retroactively. Fix TNL-680
| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| assessment | Loading commit data... | |
| fileupload | Loading commit data... | |
| locale | Loading commit data... | |
| management | Loading commit data... | |
| templates/openassessmentblock | Loading commit data... | |
| tests | Loading commit data... | |
| workflow | Loading commit data... | |
| xblock | Loading commit data... | |
| __init__.py | Loading commit data... | |
| data.py | Loading commit data... | |
| test_utils.py | Loading commit data... |