- 27 Nov, 2014 2 commits
-
-
Fix field AssessmentPart.criterion to point to Criterion table.
Usman Khalid committed -
TNL-72 & TNL-62 & TNL-811
Muhammad Ammar committed
-
- 26 Nov, 2014 1 commit
-
-
muhammad-ammar committed
-
- 25 Nov, 2014 4 commits
-
-
More accurate validation for date & time in studio editor.
Muzaffar yousaf committed -
TNL-58
muzaffaryousaf committed -
TNL-58
muzaffaryousaf committed -
TNL-58
muzaffaryousaf committed
-
- 24 Nov, 2014 2 commits
-
-
muzaffaryousaf committed
-
TNL-58
muzaffaryousaf committed
-
- 19 Nov, 2014 2 commits
-
-
Catch and log DatabaseErrors in assessment.api.self.create_assessment.
Usman Khalid committed -
TNL-812
Usman Khalid committed
-
- 18 Nov, 2014 2 commits
-
-
TNL-812
Usman Khalid committed -
Migration 0020 incorrectly altered the field to point to the CriterionOption table. TNL-826
Usman Khalid committed
-
- 13 Nov, 2014 2 commits
-
-
Fixed criterion name with label which is displayed to the user.
Waheed Ahmed committed -
TNL-768
Waheed Ahmed committed
-
- 12 Nov, 2014 5 commits
-
-
Usman Khalid committed
-
Added vagrant setup.
Usman Khalid committed -
Usman Khalid committed
-
Usman Khalid committed
-
Usman Khalid committed
-
- 11 Nov, 2014 1 commit
-
-
Usman Khalid committed
-
- 24 Oct, 2014 1 commit
-
-
Verify submission_uuid when creating assessments
Adam committed
-
- 23 Oct, 2014 1 commit
-
-
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
stv committed
-
- 18 Sep, 2014 1 commit
-
-
Update lxml and scipy
David Baumgold committed
-
- 16 Sep, 2014 2 commits
-
-
Don't pin the version too strictly.
Dave St.Germain committed -
Dave St.Germain committed
-
- 15 Sep, 2014 2 commits
-
-
David Baumgold committed
-
David Baumgold committed
-
- 12 Sep, 2014 1 commit
-
-
Update Transifex translations
Andy Armstrong committed
-
- 11 Sep, 2014 1 commit
-
-
Andy Armstrong committed
-
- 04 Sep, 2014 2 commits
-
-
Don't use published_date to figure out if xblock is published
Don Mitchell committed -
ask the modulestore if it's published LMS-11184
Don Mitchell committed
-
- 27 Aug, 2014 6 commits
-
-
Fix typo
srpearce committed -
Sylvia Pearce committed
-
Add updates about image responses, including screen shots
srpearce committed -
Sylvia Pearce committed
-
MathJax Integration
Stephen Sanchez committed -
Stephen Sanchez committed
-
- 22 Aug, 2014 2 commits
-
-
Se Won Jang committed
-
Currently, Latex rendering is only supported for question prompts in ORA2. This commit introduces Latex rendering in ORA2 student response, peer assessment view, self assessment view, grade view, and staff-info view. The reason that this Latex rendering code is inserted directly into ORA2 is that edx-platform, does not know when to start Latex rendering for ORA2 views that come in via AJAX. This commit introduces "Preview in Latex" feature which allows students to see their response rendered in MathJax before submission. Conflicts: openassessment/xblock/static/js/openassessment-lms.min.js openassessment/xblock/static/js/openassessment-studio.min.js
Se Won Jang committed
-
